https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6453
Summary: RDNS_NONE rule should handle RFC 2317 PTR resolution
Product: Spamassassin
Version: 3.3.1
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: enhancement
Priority: P2
Component: Rules
AssignedTo: [email protected]
ReportedBy: [email protected]
Since I upgraded to 3.3.1, all of our incoming messages are bumped by a
whopping 1.3 due to our own mail servers' IP addresses.
Incoming messages are all hit with RDNS_NONE, which used to be a minor hit but
now is fairly large. Reverse DNS is delegated to us by Savvis via RFC 2317
resolution (CNAME to PTR).
So. for:
Received: from [74.125.83.172] (helo=mail-pv0-f172.google.com)
by i29.s0.msiops.com with esmtp (Exim 4.71)
The offender is i29.20.msiops.com, which resolves to 64.79.173.124
digging -x that address:
;; ANSWER SECTION:
124.173.79.64.in-addr.arpa. 1971 IN CNAME
124.96-27.173.79.64.in-addr.arpa.
124.96-27.173.79.64.in-addr.arpa. 86400 IN PTR i28.s0.msiops.com.
And I think that because only a CNAME record is available, I get hit with the
RDNS_NONE.
I realize that not accounting for RFC 2317 may be a conscious decision but I
cannot find any reference to such and thus humbly request this enhancement.
-=greg
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
