At 11:10 AM 8/17/2004, Rogers, Zo� A. wrote:
I have reduced the size in local.cf - bayes_expiry_max_db_size 80000, however this has no effect because token expiry never takes place and the database just grows and grows, this is what check_bayes_db looks like. Note that no tokens have expired even though the last expiry ran today and there are over 4 million tokens in the db.

what does the output of sa-learn --force-expire -D look like?


Emails now take nearly 30 seconds to process through spamassassin, see the maillog below. I agree that the timestamps on the tokens are corrupt. What are my options? Are there any tools available for fixing an SA 2.60 database or should I get rid of the database completely and start over again?

Are you really running 2.60? Any SA older than 2.64 is subject to a DoS attack from malformed mime segments.. I'd suggest an upgrade.




Reply via email to