Hi Douglas, Douglas Kirkland schrieb :
[...] > And the world could end. What happens if some user messes with > somebody elses stuff? That what logs are for and boot the user. You > are god of the servers. Oh sorry, back to the real world. Give them > guild line in the spamc line on how it will be setup. Do not let them > guess. and don't give them a chance to spoil someone elses auto_whitelist* or bayes*. ;) [...] > If you enable bayes filtering then the bayes is at this location: > > /var/spamassassin/$domain/$group/.spamassassin/ > > In my setup we will not be allowing bayes because we have three > different server spamd server and that can eat a lot of disk space. > Then there is maintaining the bayes stuff. mhh that is exacctly my problem now. So far I have only used the "default setup and run". bayes seems to be a very good part of identifying the spam. As far as I have read documentation bayes is far better on a per-user basis than on site-wide setting, which seems logical to me. I haven't been using any sa-learn yet but still spamassassin seems still to work with it an adopt it automatically. So didn't see a problem with "maintaining the bayes stuff" yet. [...] Thx and nice holidays, Hans ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
