Hello, On Wed, 2007-11-14 at 00:43 -0800, [EMAIL PROTECTED] wrote: > http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5652 [...] > So in the interim could I suggest an FAQ that acknowledges the problem and > gives > some sort of workaround/fudge, even if that is as simple (even if suboptimal) > as > removing "bayes_seen". (Can this be safely done without needing to restart > SA, > MailScanner, etc?) Or perhaps an automatically installed cron job that > removes > it if it exceeds a certain size. > > (Obviously a proper solution in the next release would be ideal. But if that > is > not possible, then some sort of FAQ/known-issue and/or fudge/workaround.) [...]
So what would be the proper procedure at the moment? I also have several servers with bayes_seen table growing to infinite (a few GB), and would like to add a cron-based cleanup job like I did for awl / tokens. The systems are set up to work automatically (no manual sa-learn operation, so no risk to load twice the same messages). So if I understand correctly (spent an hour browsing archives & faqs), I could simply truncate the bayes_seen table every week or so, or add a timestamp field and remove entries older than 1 week|month|... and the system would still work 100% fine? Thanks for a short confirmation & thanks for your great work, regards from Switzerland, Olivier
