Date: 08 Jul 2003 09:42:49 +1000 From: Andrew Thomson <ajthomson@optushome.com.au> To: freebsd-questions@freebsd.org Subject: Re: spamassassin slow to process messages Message-ID: <1057621369.52026.35.camel@athomson.prv.au.itouchnet.net> In-Reply-To: <20030707232232.GA82782@catflap.home.slightlystrange.org> References: <1057619317.52026.28.camel@athomson.prv.au.itouchnet.net> <20030707232232.GA82782@catflap.home.slightlystrange.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. cheers, ajt.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1057621369.52026.35.camel>