Purging bayes_seen file.

[Francis Stevens <Fr...@bristow.co.uk>]

The bayes_seen file on my server has grown quite large (42MB), the man 
page for sa-learn documents what the file contains, records of 
message-ids that have been learned (in my case autolearned), but gives 
no clues of how to purge it or if this is a bad idea. Is there are 
method for shrinking this file (I'm already doing a regular sa-learn 
--force-expire --sync)? I've tried Google and the wiki but not found 
anything.  My first idea was to shutdown amavisd-new and remove the file 
altogether and then restart amavisd-new which will create a new, empty, 
file. Is this a "bad idea"?

FAS

Re: Purging bayes_seen file.

[Michael Parker <pa...@pobox.com>]

On Tue, May 03, 2005 at 01:25:10PM -0400, Matt Kettler wrote:
> 
> Unfortunately, the developers seem to keep pushing back the release for
> a fix for this, perhaps due to it being classified as p5 for some
> unknown reason. It's currently targeting 3.2.0.
> 
> I'd have considered it a blocker for the release of 3.0.0 myself (this
> bug was reported more than 8 months before 3.0.0 was released in
> November 2004.)
> 
> http://bugzilla.spamassassin.org/show_bug.cgi?id=2975
> 


Patches welcome.

Michael

Re: Purging bayes_seen file.

[Matt Kettler <mk...@evi-inc.com>]

Francis Stevens wrote:

> The bayes_seen file on my server has grown quite large (42MB), the man
> page for sa-learn documents what the file contains, records of
> message-ids that have been learned (in my case autolearned), but gives
> no clues of how to purge it or if this is a bad idea. Is there are
> method for shrinking this file (I'm already doing a regular sa-learn
> --force-expire --sync)? I've tried Google and the wiki but not found
> anything.  My first idea was to shutdown amavisd-new and remove the
> file altogether and then restart amavisd-new which will create a new,
> empty, file. Is this a "bad idea"?
>
> FAS
>
According to bugzilla there's no way to deal with this problem at the
present.  There's no expiry process (yet), and manually deleting the
file is reported as causing problems. That said, I've managed to delete
the file on my 2.64 setup without problems.

Unfortunately, the developers seem to keep pushing back the release for
a fix for this, perhaps due to it being classified as p5 for some
unknown reason. It's currently targeting 3.2.0.

I'd have considered it a blocker for the release of 3.0.0 myself (this
bug was reported more than 8 months before 3.0.0 was released in
November 2004.)

http://bugzilla.spamassassin.org/show_bug.cgi?id=2975