On Wed, 9 May 2007, Justin Mason wrote:
Duane Hill writes:
I've been doing some testing with v3.2.0 on my local machine and am seeing
a test that is triggering. I'm going to share the IP it is triggering on
in hopes someone can point out what I'm missing.
[71849] dbg: received-header: parsed as [ ip=162.42.148.100 rdns=
helo=smtpgate.ndunet.com by=admin.mwci.net ident= envfrom= intl=0 id=119059853
auth= msa=0 ]
...
[71849] dbg: rules: ran header rule RDNS_NONE ======> got hit: "[ip=162.42.148.100
rdns= "
Doing a lookup of the IP from where I am sitting, I can get the reverse
DNS:
Non-authoritative answer:
100.148.42.162.in-addr.arpa name = smtpgate.ndunet.com.
sounds like the MTA in question is not performing rDNS lookups,
or else not recording them in a format SpamAssassin can read.
You are correct now that I look. The MTA is CommuniGate and the header is:
Received: from [162.42.148.100] (HELO smtpgate.ndunet.com)
by admin.mwci.net (CommuniGate Pro SMTP 4.1.8)
with ESMTP id 119059853 for [EMAIL PROTECTED];
Wed, 09 May 2007 14:11:59 +0000
I can resolve 162.42.148.100 from the CommuniGate server successfully.
And, as I reflect back, this has been brought up a very few times in the
past about the headers being incorrect with that MTA on this list.
