----- Original Message ----- From: "Ulysses Cruz" <[EMAIL PROTECTED]> To: <users@spamassassin.apache.org> Sent: Thursday, September 23, 2004 1:21 PM Subject: Re: ***SPAM*** Problems with URIDNSBL Under Spamassassin 3.0?
> On Thu, Sep 23, 2004 at 01:10:40PM -0500, Sandy S whispered: > > Ulysses - > > Thanks for your advice. I'm pretty sure we have all the needed perl > > modules, since 99% of the time the URIBL rules are working just as they're > > supposed to. It's only on those one or two .info domains that they don't > > fire. > > > > Any other ideas? > > > > Thanks, > > Sandy > > OK, last guess here, you said that you're running SA from procmail, have you > checked to see if the URIBL rules are failing for the same user each time, or > are they failing for random users? It's possible one of your users has the > wrong configuration, or possibly lacks permissions to connect to the URIBLs or > run a particular perl module. > > Ulysses > > -- > Ulysses S. Cruz [EMAIL PROTECTED] > "If it wasn't for the voices in my head, I'd go insane from loneliness" > -Me, Myself and I > Ulysses - Thanks for another good idea. Just to make absolutely sure there were no permissions issues, I went in as root and manually ran the email in question through spamassassin -D, but I got the same results. I did find these lines in the debug output: debug: URIDNSBL: domains to query: tvuu.wneiis-MUNGEDplanet.info dkcw.wneiis-MUNGEDplanet.info ----and---- debug: URIDNSBL: queries completed: 0 started: 0 debug: URIDNSBL: queries active: DNSBL=2 NS=2 at Thu Sep 23 13:36:08 2004 debug: done waiting for URIDNSBL lookups to complete Apparently the lookups timed out. I assume that's something to do with the fact that it's checking for tvuu.wneiis-MUNGEDplanet.info instead of just wneiis-MUNGEDplanet.info, but I don't know enough about how the URI RBLs work to be sure. I'm stumped at this point, but fortunately a) it works most of the time and b) other checks like Razor and DCC seem to be kicking in to push these messages over the Spam threshhold anyway. So I guess it's not a major issue - I was just wondering if anyone else had run into it and if it was something I should report as a bug. Thanks for all your help and ideas! Sandy
