>> (in reverse order for clarity)
>> Message 1:
>> Received: from lucid.net.nz by lists.boingo.com with SMTP; Wed, 15
>> Nov 2000 13:44:12 -0800
>> Received: from [207.46.115.23] (helo=lists.boingo.com)
>> by tantalum.btinternet.com with smtp (Exim 3.03 #83)
>> id 13wAKU-0000gO-00; Wed, 15 Nov 2000 21:42:55 +0000
>>
>>
>> Message 2:
>> Received: from lucid.net.nz by lists.boingo.com with SMTP; Wed, 15
>> Nov 2000 13:44:12 -0800
>> Received: from [207.46.115.23] (helo=lists.boingo.com)
>> by praseodumium.btinternet.com with smtp (Exim 3.03 #83)
>> id 13wAOO-00001G-00; Wed, 15 Nov 2000 21:46:57 +0000
> At first glance, looks like a misconfiguration of
> btinternet.com to me --
>
> note, one message is received by tantalum.btinternet.com
> and the other by praseodumium.btinternet.com.
I have to partially disagree with this analysis.
Because, in this instance, the "being received at two separate locations"
behavior can only happen if boingo sends two separate messages.
The actual machine acting as the SMTP server for the domain btinternet.com
is allowed to change quite consistently. Some larger domains are configured
such that a pool of machines alternate being identified as *the* SMTP server
on a per domain name resolution. It's a somewhat primitive form of load
balancing (especially primitive for SMTP...it works much, much better for
things like www.foo.bar).
So, the second message going through another machine is not a priori
evidence of a problem at btinternet.com.
I can come up with some failure scenarios that would result in this
behavior; however, the vast majority of them end up pointing the fickle
finger of fate at the mail server on boingo.com.
At the moment, there's insufficient data to draw a conclusion with any
degree of confidence.
mikel
PS: *I'm* not seeing duplicate messages.
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
