On Apr 18, 2006, at 3:09 PM, Daryl C. W. O'Shea wrote:
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.
It might be good to try running some tests with -L and some tests
without -L, to see if the same test is fast without the network check.
That would help isolate the problem to "is SpamAssassin slow" or "is
SpamAssassin spending a lot of time waiting for DNS results". It
probably IS the latter, but it's always good to isolate symptoms, IMO.
Also, are you doing any other network stuff? razor, pyzor, etc.?
