On Tue, 2003-07-08 at 09:22, Daniel Bye wrote:
> Could be mx timeouts, DNS timeouts, rbl timeouts, dcc/razor/pyzor
> timeouts...
> In your global SpamAssassin config, try setting a value for timelog_path -
> this will cause spamd to log what it's doing, and where it spent most time
> doing it.  Check perldoc Mail::SpamAssassin::Conf.
> You might also try turning on debugging (modify /usr/local/etc/rc.d/spamd.sh
> so that spamd is called with the `-D' option, then restart spamd).  You will
> then get lots of debugging in /var/log/mail.

Thanks Dan.

Some great suggestions, appreciate it. Anyway you were onto it.. tracked
down the following..

0.000: Finished head tests (Delta: 0.000s)
0.000: Starting body tests
0.000: Razor2 -> Starting razor test (10 secs max)
10.000: Razor2 -> Finished razor test: not known spam (Delta: 10.000s)
10.000: Finished body tests (Delta: 10.000s)

Time to investigate that.



[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to