diff options
author | Peter Palfrader <peter@palfrader.org> | 2006-05-20 23:59:10 +0000 |
---|---|---|
committer | weasel <weasel@bc3d92e2-beff-0310-a7cd-cc87d7ac0ede> | 2006-05-20 23:59:10 +0000 |
commit | c0bd75bdc2b2bd90b89aef113b19f89db72aff20 (patch) | |
tree | b3db4327085849a803628a12cc622b309f571769 /spamassassin/sa-bogofilter/README | |
parent | ace70e8ecd004e36201531f73d6bdf07849d117d (diff) |
Add original sa-bogofilter
git-svn-id: svn+ssh://asteria.noreply.org/svn/weaselutils/trunk@95 bc3d92e2-beff-0310-a7cd-cc87d7ac0ede
Diffstat (limited to 'spamassassin/sa-bogofilter/README')
-rw-r--r-- | spamassassin/sa-bogofilter/README | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/spamassassin/sa-bogofilter/README b/spamassassin/sa-bogofilter/README new file mode 100644 index 0000000..bcf77f4 --- /dev/null +++ b/spamassassin/sa-bogofilter/README @@ -0,0 +1,16 @@ +SA-Bogofilter 0.01 + +This is a beta release of SA-Bogofilter. I actually use it in production, things have been fine so far. Your milage may vary. + +Things to be aware of: + + Each user gets their own directory under /var/lib/bogofilter/. SpamAssassin has NO WAY to know if these are valid users. so you may find yourself dealing with a bunch of folders that don't correspond to any users. If this is the case, either have your MTA do address verification BEFORE the mail hits SA, OR have cron remove all directories in the tree older than 2 weeks or 3 months or whatever you think is a sane value for your site. + + Just because bogofilter is enabled doesn't mean you have to disable the built in SpamAssassin bayes. + +TODO: + + It would be handy to provide an option for a GLOBAL bogofilter at the same time a per-user filter is in place. I haven't tried that configuration yet, but maybe it will happen. + +If you have any bugs, etc. feel free to contact me at josh@statewidesoftware.com. I'll try and help you out with any problems you have. I'd especially appreciate any patches. + |