Benny Pedersen wrote:
On Thu, June 26, 2008 02:54, Matt Kettler wrote:
It's a fine distinction, but one that does matter to some folks who are
set up this way. In most cases the two are equal, but that doesn't
excuse me from confusing the two. I should know better. :)
then stop cc me
I'll attempt to do so. Didn't realize you disliked it.
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
tests=FM_FAKE_HELO_VERIZON,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of [EMAIL PROTECTED]
designates 206.46.173.3 as permitted sender)
Received: from [206.46.173.3] (HELO vms173003pub.verizon.net) (206.46.173.3)
by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jun 2008 00:56:44 +0000
fake helo ???
I'm SA interpreted the Received header as meaning that athena.apache.org
found no reverse-lookup the host, and that 206.46.173.3 is a host with
no reverse DNS claiming to be vms173003pub.verizon.net. At least, that's
how I'd read that header.. the FM_FAKE_HELO_VERIZON is likely an early
rule trying to detect hosts using verizon helo's that aren't really
verizon hosts.
