> I'd suggest even keeping 1 machine as the "master" bayes DB, do sa-learns
> there by hand, and copy out DBs onto the "slave" servers which do
> the scanning. Each "slave" has a copy of the bayes DB on their
> local disk, which is overwritten periodically by the master.
Which brings up an interesting thought.
Does Bayes have a "learn to log" option where it can spool all the messages
an auto-learn has decided to learn?
If it did, each system could "autolearn" to a local log, and a cron script
could suck them up every so often, cat them together, and do a dedicated
update of the Bayes db, then redeploy the updated version.
I'd think with that the only place you will take a hit will be doing the
actual db update, which probably will shut down Bayes for a few moments
during the file switch.
You could do the entire learn process on a dedicated small machine that
wasn't even part of the actual mail filtering system, but was just a db
updater and redeployer.
Loren
