Matt Kettler wrote:
Derek Catanzaro wrote:
I have a ton of bayes_toks.expire files listed in
/root/.spamassassin. Is it safe to delete these files?
Yes, provided no expire process is currently running and using one.
I did wind up deleting all of the bayes_toks.expire files, there were hundreds.
1) run sa-learn --force-expire to fix the immediate problem.
After deleting the bayes_toks.expire files I ran sa-learn --force-expire and received the result below and it just stayed there for at least 20 minutes so I forced it to stop. Is this normal behavior? Was I too impatient with the process? My bayes_toks file is 321MB, not sure if that is part of the issue.

.spamassassin]# sa-learn --force-expire
bayes: synced databases from journal in 0 seconds: 1611 unique entries (2099 total entries)
2) prevent future problems by fixing your spamassassin timeout value in
MailScanner.cf

Anything under 600 seconds is bad news if you use bayes. In fact, I'd
set it to 3000 seconds. I use MailScanner myself, and have since the SA
2.31 days, and I've NEVER had MailScanner time out a SA process for any
valid reason. I've only had it time out because the timeout value was
too short.
Matt, After posting this to the list I did some more research online and found the following thread which you responded to. I have applied the settings listed in this thread to my MS/SA setup. Do these settings still apply in your opinion? The thread recommends a minimum of 60 seconds for the spamassassin timeout value, mine is set to 75. Based on what you are saying above I believe I need to increase the spamassassin timeout dramatically, can you confirm? Since I deleted the bayes_toks.expire files there has been 1 .expire file generated already, so I 'm assuming that should tell me my timeout is still too low?

http://mail-archives.apache.org/mod_mbox/spamassassin-users/200410.mbox/[EMAIL 
PROTECTED]

Thanks for all of the information you provided. I really appreciate the assistance.
Thanks,
Derek


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Reply via email to