Richard Collyer wrote:
Daryl C. W. O'Shea wrote:
Richard Collyer wrote:

I've changed it to a DNS server from my ISP, but so far its not making any difference.

 SA: finished scan in 13.719613 secs - hits=-1.0

BTW, if you watch the debug output of a message being scanned, you'll see exactly where it's slow.

spamassassin -D < non-local-test.msg

I'm guessing that these are the problems. SpamAssassin is launching a lot of rDNS queries looking for A records and such like. Better stil these are coming back false. Someone I was talking too mentioned i need a -H flag somewhere to stop these DNS lookups?

-H sets the home directory and has nothing to do with DNS lookups. -L disabled all net tests, which you don't really want either.


Ideas?
[EMAIL PROTECTED]:/home/richard] $ spamassassin -D < test-external.msg

<snip>

[42615] dbg: dns: success for 16 of 38 queries
[42615] dbg: dns: timeout for sorbs after 12 seconds

<etc>

A little weird that you're getting no NXDOMAIN responses from those lists. I'd look for a firewall issue blocking DNS responses.

Try querying for some of the records manually.

In any case, also read about rbl_timeout in the Mail::SpamAssassin::Conf perldoc.


Daryl

Reply via email to