Jason Frisvold wrote: > > With respect to bayes_tok though, can that be trimmed at all with > minimal impact? 3GB is a tad large for the database, though I guess > that depends on the number of users. I can't think of any way to > limit that, though, and I wonder how even larger entities can deal > with databases that much be much larger. > Bayes_toks should trim itself automatically.
Have you done a sa-learn --dump magic? How long has it been since expiry ran on your system? How may tokens are in the DB? Try running sa-learn --force-expire. Does that run (probably for a long time) and then fix the problem? Do you call SA through MailScanner or amavis which might be interfering with expire runs by timing out and killing SA? (This only matters for tools that use the API.. Or technically a tool that uses the spamassassin command line script, but no decent integration tools that monitor execution time do that. Anything that calls spamc to access spamd won't be able to kill off the expire process by killing spamc.)
