https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6573

           Summary: Report for IPv6 IP hitting DNS BL/WL is broken
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: spamassassin
        AssignedTo: [email protected]
        ReportedBy: [email protected]


For IPv6 IP 2001:470:f329:1::1 in zone iprep.chaosreigns.com, it's reporting:

-0.1 RCVD_IN_IPREPDNS_100   RBL: Sender listed at
                            http://www.chaosreigns.com/iprep/, 100% ham
[0.0.0.1 listed in
0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.9.2.3.f.0.7.4.0.1.0.0.2.iprep.chaosreigns.com]

When it should be reporting:


-0.1 RCVD_IN_IPREPDNS_100   RBL: Sender listed at
                            http://www.chaosreigns.com/iprep/, 100% ham
                            [2001:470:f329:1::1 listed in
iprep.chaosreigns.com]


The IP was 2001:470:f329:1::1.  In long form, that's
2001:0470:f329:0001:0000:0000:0000:0001.  So the PTR record is all the
integers, in reverse order, with dots in between all of them: 
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.9.2.3.f.0.7.4.0.1.0.0.2.ip6.arpa. 
Which makes the DNS BL/WL record in zone iprep.chaosreigns.com:
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.9.2.3.f.0.7.4.0.1.0.0.2.iprep.chaosreigns.com.

So it looks like the report is just splitting that at the 4th dot, and
considering the first part the IP (reversed), and the second part the zone,
which is reasonable enough for IPv4, but wrong for IPv6.

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to