« Return to Thread: spamassassin management by file deletion

Re: spamassassin management by file deletion

by newby 23 :: Rate this Message:

Reply to Author | View in Thread

> Hmm.  Do you have shell access?  It's not necessary, but it'll make
> things easier if you do.

No, I don't have shell access.  I can access the file space by FTP, though.

> How big are each of those files?

auto-whitelist = 0.7MB
bayes_journal = 70kB
bayes_seen = 0.3MB
bayes_toks = 5.3MB
users_prefs = 1.5kB

> You'll probably want to disable the AWL and delete auto-whitelist;

How do I disable AWL?

> You'll probably also want to fiddle with the Bayes directive that
> controls how large the Bayes data files get;  while it works on number
> of tokens rather than disk size it can be give a rough estimate of disk
> use.  The default bayes_expiry_max_db_size of 150,000 tokens may be too
> large, but it looks like you can't make it much smaller.

My users_prefs file does not currently have a bayes_expiry_max_db_size option in it.  Do I simply add one, setting a smaller value?  If so, how do I get a sense of what a good value is?

> Over the longer term, you can delete bayes_journal and bayes_seen;
> those are not critical to proper operation of the Bayes subsystem.
> However, if you remove bayes_seen, you'll end up re-learning messages
> over and over again if regularly re-learn a folder that you don't empty.

Got it.  They don't seem to be a big problem right now.

There's nothing that I can do with bayes_toks?

Thank you for the above, Kris: it helps a good deal.

Best,

Colin

 « Return to Thread: spamassassin management by file deletion