You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2015/09/07 18:48:30 UTC

[Bug 7242] URIBL_SBL and URIBL_SBL_A doing each other's lookups

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7242

Kevin A. McGrail <km...@pccc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kmcgrail@pccc.com

--- Comment #1 from Kevin A. McGrail <km...@pccc.com> ---
Adding more information about the issue:

$ printf "\n\nhttp://www.alfordmedia.com/" | spamassassin -D uridnsbl  2>&1     
Sep  5 00:57:40.749 [88636] dbg: uridnsbl: considering
host=www.alfordmedia.com, domain=alfordmedia.com
Sep  5 00:57:40.759 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_RHS_DOB
DNSBL:alfordmedia.com:dob.sibl.support-intelligence.net
Sep  5 00:57:40.759 [88636] dbg: uridnsbl: complete_ns_lookup
NS:alfordmedia.com
Sep  5 00:57:40.760 [88636] dbg: uridnsbl: got(1) NS for alfordmedia.com:
alfordmedia.com. 172603 IN NS ns-1298.awsdns-34.org.
Sep  5 00:57:40.760 [88636] dbg: uridnsbl: got(2) NS for alfordmedia.com:
alfordmedia.com. 172603 IN NS ns-1925.awsdns-48.co.uk.
Sep  5 00:57:40.761 [88636] dbg: uridnsbl: got(3) NS for alfordmedia.com:
alfordmedia.com. 172603 IN NS ns-62.awsdns-07.com.
Sep  5 00:57:40.761 [88636] dbg: uridnsbl: got(4) NS for alfordmedia.com:
alfordmedia.com. 172603 IN NS ns-696.awsdns-23.net.
Sep  5 00:57:40.762 [88636] dbg: uridnsbl: complete_a_lookup
A:www.alfordmedia.com
Sep  5 00:57:40.762 [88636] dbg: uridnsbl: complete_a_lookup got(1) A for
www.alfordmedia.com: www.alfordmedia.com. 103 IN A 209.124.71.2
Sep  5 00:57:40.764 [88636] dbg: uridnsbl: complete_a_lookup
A:ns-1298.awsdns-34.org
Sep  5 00:57:40.764 [88636] dbg: uridnsbl: complete_a_lookup got(1) A for
ns-1298.awsdns-34.org: ns-1298.awsdns-34.org. 170801 IN A 205.251.197.18
Sep  5 00:57:40.765 [88636] dbg: uridnsbl: complete_a_lookup
A:ns-1925.awsdns-48.co.uk
Sep  5 00:57:40.765 [88636] dbg: uridnsbl: complete_a_lookup got(1) A for
ns-1925.awsdns-48.co.uk: ns-1925.awsdns-48.co.uk. 170801 IN A 205.251.199.133
Sep  5 00:57:40.766 [88636] dbg: uridnsbl: complete_a_lookup
A:ns-62.awsdns-07.com
Sep  5 00:57:40.766 [88636] dbg: uridnsbl: complete_a_lookup got(1) A for
ns-62.awsdns-07.com: ns-62.awsdns-07.com. 170801 IN A 205.251.192.62
Sep  5 00:57:40.767 [88636] dbg: uridnsbl: complete_a_lookup
A:ns-696.awsdns-23.net
Sep  5 00:57:40.767 [88636] dbg: uridnsbl: complete_a_lookup got(1) A for
ns-696.awsdns-23.net: ns-696.awsdns-23.net. 170801 IN A 205.251.194.184
...
Sep  5 00:57:40.863 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL_A
DNSBL:2.71.124.209:sbl.spamhaus.org
Sep  5 00:57:40.864 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL
DNSBL:2.71.124.209:zen.spamhaus.org      <--- A
Sep  5 00:57:40.864 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL_A
DNSBL:18.197.251.205:sbl.spamhaus.org  <--- B
Sep  5 00:57:40.864 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL_A
DNSBL:62.192.251.205:sbl.spamhaus.org  <--- B
Sep  5 00:57:40.864 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL_A
DNSBL:133.199.251.205:sbl.spamhaus.org <--- B 
Sep  5 00:57:40.865 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL
DNSBL:184.194.251.205:zen.spamhaus.org
Sep  5 00:57:40.979 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL
DNSBL:18.197.251.205:zen.spamhaus.org
...
Sep  5 00:57:43.032 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL
DNSBL:62.192.251.205:zen.spamhaus.org
Sep  5 00:57:43.033 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL
DNSBL:133.199.251.205:zen.spamhaus.org
Sep  5 00:57:43.033 [88636] dbg: uridnsbl: complete_dnsbl_lookup URIBL_SBL_A
DNSBL:184.194.251.205:sbl.spamhaus.org <--- B

In the line marked A it looks like URIBL_SBL did look-up SBL (via zen)
for the host's IP. Also in the lines marked B it looks  URIBL_SBL_A is 
doing an SBL look-up on the nameserver IPs as well as the hosts. In
other words it looks like both rules are doing the full set of look-ups

-- 
You are receiving this mail because:
You are the assignee for the bug.