Johann Spies wrote to [EMAIL PROTECTED]: > [...] > It might be both auto-whitelisting and bayesian corruption. > > I can not afford unreliable software to do this important job. > Am I the only one who experience this type of behaviour?
No. See, at least, the thread that I started, beginning with "Bayes went nuts". Aside from a couple of "me too" responses, I'm not aware of any resolution yet. The workaround was to replace the DB, as you discovered. On a system like yours, you might want to tune the expiry settings. Or, if you want control, don't auto-expire. Manually expire periodically, but back up the database first, manually expire on the backup (use --dbpath), compare sa-learn --magic, and then swap the databases if everything looks OK. If things *do* go wrong, you'll have a recent backup, *and* an excellent way to diagnose expiry-related problems. If you want to be part of the solution, let us know which version of SA you're running, what your expire settings were when this happened, and what sa-learn --magic tells you. It seemed to me that your post was more of a frustrated rant than a potential problem report. :-) > How can I prevent this? I can not watch spamassassin 24 hours per day > to jump in when something goes wrong. If it's that important, you can't afford *not* to watch SpamAssassin 24 hours per day to jump in when something goes wrong. Problems can occur with *any* system. Automate the monitoring of it, or hire someone who can. Cheers, - Ryan -- Ryan Thompson <[EMAIL PROTECTED]> SaskNow Technologies - http://www.sasknow.com 901-1st Avenue North - Saskatoon, SK - S7K 1Y4 Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America
