You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2008/03/10 16:46:32 UTC

[Bug 5652] bayes_seen - auto expire

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5652


Olivier Mueller <om...@omx.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |om-lists-spamassassin@omx.ch




--- Comment #6 from Olivier Mueller <om...@omx.ch>  2008-03-10 08:46:32 PST ---
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


-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.