http://bugzilla.spamassassin.org/show_bug.cgi?id=2975
------- Additional Comments From [EMAIL PROTECTED] 2004-04-13 11:40 ------- Subject: Re: bayes_seen database uncontrolled growth On Tue, Apr 13, 2004 at 11:29:45AM -0700, [EMAIL PROTECTED] wrote: > Does the Bayes framework allow for an expiration to occur? Could it be rolled > in with the token auto expiration code? No it doesn't. It would take a slight re-design and probably more thought. I see the following possible attributes of things we might want to support in the future: 1) Straight date based expiry. Note Date/Time when msgid was first learned and after N days expire all msgids > N days old. We can then run this at the same time as expiration or some other process could handle this. 2) Similar to 1 but update the timestamp if we try to re-learn the msgid. The thinking here is that for some reason this msgid was re-examined so lets keep it around a little bit longer to avoid re-learning. 3) Keep no record of learned msgids and allow exhaustive learning or explicitly disable learning in this case. This would help folks who learn on one box and copy the bayes_toks file to a production box and have auto_learn turned off. It would also allow for multiple learns on the same message (ie exhaustive learning, see http://garyrob.blogs.com/garys_longer_rants/2004/02/instructions_fo.html via jmason). 4) Log how many times a message has been learned, again see exhaustive learning stuffs. 5) Tie which tokens were learned from a particular msgid and then expire by msgid instead of by token atime. 6) All the various combinations of all of the above. Anything else? Michael ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
