[snip]
>Earthlink has added a hop to all of its mail routes that is address
>127.0.0.1.
[snip]
>Received: from smtp.earthlink.net [209.86.93.204]
> by localhost with POP3 (fetchmail-6.2.5.5)
> for <> (single-drop); Wed, 25 Apr 2007 02:52:48 -0700 (PDT)
>Received: from noehlo.host ([127.0.0.1])
> by mx-various.atl.sa.earthlink.net (EarthLink SMTP Server) with
SMTP >id 1hGEaM2WL3Nl36J4; Wed, 25 Apr 2007 05:52:28 -0400 (EDT)
>Received: from friend ([84.22.20.109])
> by mx-various.atl.sa.earthlink.net (EarthLink SMTP Server) with
ESMTP
>id 1hGEaG1f93Nl36J0
> for <>; Wed, 25 Apr 2007 05:52:27 -0400 (EDT)
I think Chris was talking about the same behavior yesterday... his
message had the following headers in it...
Received: from [208.47.184.3] (HELO mailrelay.embarq.synacor.com)
(208.47.184.3)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Apr 2007 18:07:55
-0700
Received: from localhost (localhost.localdomain [127.0.0.1])
by mailrelay.embarq.synacor.com (Postfix) with ESMTP id
0EA8122B971
for <[EMAIL PROTECTED]>; Tue, 24 Apr 2007 21:07:35
-0400 (EDT)
Received: from mailrelay.embarq.synacor.com ([127.0.0.1])
by localhost (smtp01.embarq.synacor.com [127.0.0.1])
(amavisd-new, port 10024)
with ESMTP id Ffxe6ob1J0vm for <[EMAIL PROTECTED]>;
Tue, 24 Apr 2007 21:07:34 -0400 (EDT)
Received: from [192.168.2.2] (tx-71-48-168-13.dhcp.embarqhsd.net
[71.48.168.13])
by mailrelay.embarq.synacor.com (Postfix) with ESMTP id
9F9F222B966
for <[EMAIL PROTECTED]>; Tue, 24 Apr 2007 21:07:34
-0400 (EDT)
It looks like Embarq is even worse than Earthlink, as they route through
127.0.0.1 TWICE.
So, I think Earthlink may not be the only one with this "problem"...
If this isn't a special case for Earthlink, we'll need to think a little
more generically about how to work around it.
>From the looks of the headers, it may be an amavisd misconfiguration?
(I don't use amavisd, so I can't comment past this...)
Regards,
--Vince
