Stefan Jakobs wrote:
I'm using SA 3.1.2 with amavis-new and postfix on a mailrelay.
I turned on bayes autolearning with the standard options, but my bayes_seen db
grows and grows, now it is by 1.1 GB.
Why reduce SA the size not automatically?
Probably because its automatic expiry runs are getting interrupted by
amavis-new. Check back in the list archives; quite a few people have
had this problem.
For *any* file-based sitewide Bayes setup, IMO, you should set the SA
options so it doesn't run automatic expiry, and set up a cron job to
manually run the expiry process on a regular basis (daily is probably
good for most sites; *really* high-traffic sites can probably go every
few hours but they should be using SQL-based Bayes anyway IMO <g>).
What can I do, to reduce the size of the db?
Right away, you can manually expire tokens by running sa-learn
--force-expire.
What are your experience with the bayes db?
One legacy system still running 2.64 has had a stable Bayes db around
40M for close to four years now. (Possibly 5 years. I don't recall
when I upgraded to 2.5x on that box.) Fairly early on, I disabled
automatic expiry and set up a daily cron job to run the expiry process
manually. I've *never* had trouble with the database inflating out of
control.
If you do set up a cron'ed expiry on your system, make sure it runs as
the same user amavis-new is running as. Otherwise you'll end up with
file permission issues.
Check the man pages for your local SA install for the exact Bayes
options you need to tweak.
-kgd
