From: Chris <[EMAIL PROTECTED]>
To: users@spamassassin.apache.org
Date: Friday, September 29, 2006, 3:59:03 PM
Subject: Non-blocklisted embedded URLs are getting hits on
URIBL_AB_SURBL and URIBL_PH_SURBL in SpamAssassin 3.1.5
===8<==============Original message text===============
On Thursday 28 September 2006 1:17 am, Donald Craig wrote:
And Theo Van Dinter pointed out:
You're not by chance using the opendns.{com,org} folks for DNS,
are you?
Of course. I'm an idiot. I switched to OpenDNS a couple of weeks
back.
Time to return from whence I came. Thank you,
Donald,
We handle DNSBLs but not URIBLs, at the moment. Passing along to
Noah to see what he can do. Sorry you had this happen to your
SpamAssassin scoring. (Time to check mine... :-) )
You can resolve this behavior by turning off typo correction in your
preferences page and it'll work again with us returning NXDOMAIN
(RCODE=3) instead of doing the typo correction service. Hopefully we
can get more granular with that in the future.
If you are on a dynamic IP, well, just sit tight for a couple more
weeks or email me to start beta testing some code this week to handle
dynamic IPs (and that offer is for anyone).
Thanks,
David Ulevitch (from OpenDNS)
Don Craig
--------------------------------------------------------------------
I'm getting matches whenever I have an embedded URL
on URIBL_AB_SURBL and URIBL_PH_SURBL -
unless the URL is actually in URIBL_SBL, in which case the
logic for all the flavors of URIBL_XX_SURBL seems
to work correctly. I have verified the
absence of the incorrectly matching URLs from SURBL
with lookups in http://www.rulesemporium.com/cgi-bin/uribl.cgi
This is SpamAssassin 3.1.5, all was fine in 3.1.2.
For now I have set both those tests to 0.00.
Don Craig
Yes, OpenDNS definitely caused problems for me also:
Sep 1 21:51:25 localhost spamd[10939]: uridnsbl: bogus rr for
domain=otwaloow.com, rule=URIBL_XS_SURBL, id=8880
rr=otwaloow.com.xs.surbl.org. 1 IN A 208.67.219.40
at /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/Plugin/
URIDNSBL.pm line
626.
Theo pointed out the errors of my ways:
The error is saying that it's looking for a 127/8 result, but it gets
208.67.219.40 (which resolves to a *.opendns.com name btw). So I
would
say that yes, the problems are related to changing your nameservers.
--
Chris
===8<===========End of original message text===========
