https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5926
--- Comment #1 from Sidney Markowitz <[EMAIL PROTECTED]> 2008-06-19 19:25:51
PST ---
I believe that what's going on is that the server at ax7.axolotl.com is not
properly putting the rdns information in the Received header. The __RDNS_NONE
rule parses the Received header, and does not do a rdns lookup itself. Compare
this header
Received: from e33.co.us.ibm.com ([32.97.110.151])
by ax7.axolotl.com (Lotus Domino Release 7.0.3)
with this one:
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
[9.17.195.106])
by e33.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id
m5IIHrwJ004657
The server that created the second Received header placed the rdns information
inside the parentheses, before the ip address.
Note that if you fix the 32.97.110.151 Received header, the RDNS_NONE rule is
still triggered by
Received: from ax7.axolotl.com ([63.241.71.50])
by AX1.axolotl.com (Lotus Domino Release 7.0.3)
because ax1.axolotl.com has the same problem. SpamAssassin seems to stop
checking for RDNS_NONE after the first one that it notices.
I think that this bug can be closed as WORKSFORME and you need to look at the
server configuration at axolotl.com, but I'm a bit outside my area of expertise
so I will leave this open to give someone a chance to jump in to tell me if
I've made a mistake in my analysis.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
