[sf-lug] iris.well.com is unknown

[Michael Paoli]

Or ... you could put it on the list, avoiding multiple person's
more-or-less going around, checking, doing same on and/or off-list,
or going "Huh?" after looking it over again.

In any case, thanks for noting and pointing
it out, saves me bothering to check and provide the evidence in
yet more incontrovertible form and with the relevant authoritative
references.

> From: "James Stockford" <jim at well.com>
> Subject: Re: [sf-lug] iris.well.com is unknown
> Date: Thu, 10 Jan 2019 13:40:16 -0800

>
> my apologies. I recall clearly changing
> the subject to iris.well.com is unknown.
>
> Having reviewed the thread, it is clear
> that you revised it.
>
> I'm replying directly rather than through
> the list to reduce non-technical burden.
>
>
> On 1/9/19 9:22 PM, Michael Paoli wrote:
>>> From: "James Stockford" <jim at well.com>
>>> Subject: Re: [sf-lug] Wi-Fi woes
>>> Date: Wed, 9 Jan 2019 12:27:04 -0800
>>
>>> I've discovered another post-disaster symptom
>>> that may relate:
>>
>> Update the Subject: header
>>
>>> I use Thunderbird to get my email from
>>> The Well's email server, iris.well.com
>>>
>>> Now I click to reply to an email, write
>>> my comment, then click the Send button.
>>> The system responds with a message that
>>> iris.well.com is unknown.
>>
>> Absolutely nothing about that inherently related to Wi-Fi.
>> If you were on a perfectly fine operating computer on hardwired LAN,
>> with find Internet access, etc., and got that message, would you presume
>> it was Wi-Fi?  No.
>> So, no reason to presume it's Wi-Fi.
>> So, how 'bout an updated to ye olde Subject: header,
>> maybe something like:
>> Subject: DNS: iris.well.com is unknown
>> Or if you don't now if it's a DNS issue or not, how 'bout:
>> Subject: iris.well.com is unknown
>>
>> So, my reply to:
>> Subject: Re: [sf-lug] Wi-Fi woes
>>> iris.well.com is unknown
>>
>> Not a Wi-Fi problem, please accurately state relevant facts.