I had the exact same problem with a mySQL setup. The problem was permissions, the mySQL user did not have delete permissions for the that table so it could not remove the rows. Once I did that, everything started working fine.
-----Original Message----- From: Dave Koontz [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 19, 2007 5:55 PM To: users@spamassassin.apache.org Subject: Re: bayes_seen = 256GB Theo and all. I know this topic comes up on occasion, but I am not sure I've ever seen an explanation as to why the bayes_seen file is not auto pruned along with the bayes db file. Since tokens expire in the main DB file, what is the purpose of having a seen file to unlearn tokens which may have long ago been purged? IMO, it would seem logical to also purge the seen file at some sort of cycle so it can't grow so excessively large. Theo Van Dinter wrote: > On Wed, Sep 19, 2007 at 03:23:50PM -0600, Mr. Gus wrote: > >>> The file bayes_seen has grown in size to 256GB! (274992939008) >>> How do I cap the size limit of this file? I want to have it not grow larger >>> then say 800mb at the most! >>> >> You need to expire old bayes tokens. The limit is set not as a size, but as >> > > Expiring bayes tokens does nothing to the bayes_seen file. There is no expiry > for bayes_seen. > > If the seen file is bigger than you'd like, I'd just rm the file. > >
