https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7211
Andy Smith <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andy-apache.org@strugglers. | |net --- Comment #6 from Andy Smith <[email protected]> --- Having read the documentation, unless I am missing something I cannot see how this plugin can work when email is received from both IPv4 and IPv6 hosts. The only way to specify a zone is "asn_lookup". If you do: asn_lookup origin.asn.cymru.com _ASN_ _ASNCIDR_ this will work fine for mails that come in from IPv4 addresses, but when you get one from an IPv6 address that happens to match, it will erroneously bring back a match for an IPv4 address like 2.0.0.0/16. If instead you do: asn_lookup origin6.asn.cymru.com _ASN_ _ASNCIDR_ then no IPv4 query will ever match, but it will work for IPv6 queries. That won't be very useful for most people since most mail comes in from IPv4 addresses. If you try adding both then all queries will go to both zones, so the erroneous answers will still be returned. Doesn't this plugin need to separate out zones that accept v4 queries and zones that accept v6 queries, so that one could for example do: asn_lookup origin.asn.cymru.com _ASN_ _ASNCIDR_ asn_lookup_v6 origin6.asn.cymru.com _ASN_ _ASNCIDR_ and then have the plugin send only v4 queries to the asn_lookup zones and only v6 queries to the asn_lookup_v6 zones? -- You are receiving this mail because: You are the assignee for the bug.
