Joel Uckelman on 8 Aug 2002 18:18:04 -0000 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
[hosers-announce] how not to ENLARGE YOUR PENIS and REFINANCE BEFORE IT'S TOO LATE!!!! |
Ahem. All incoming mail is now being filtered by SpamAssassin. You can see what it's doing if you look for various X-spam-* headers. Each incoming mail is tested against a host of heuristics, and given a score based on the results. E.g., HAVING AN ENTIRE LINE OF YELLING SHOULD GET THIS MESSAGE A FEW POINTS which you'll be able to see in on of the X-spam-* headers. By default, any message that scores 5.0 or higher is given the following header: X-spam-flag: YES It's easy to use procmail and the X-spam-flag header to sort the spam from real mail. Assuming that you use MH locally and you want your spam to be filed into an MH folder named 'spam', this can be accomplished by creating a ~/.procmailrc with the following contents: :0: * ^X-Spam-Status: Yes | /usr/lib/nmh/rcvstore +spam If you already have one, then chances are you already know how to integrate this recipe into your existing .procmailrc. If you use fetchmail to read you mail somewhere else, (e.g., Tom?), just make a .procmailrc there with the same contents. If you use some other mail reader (does anyone here *not* use MH?), or you want some other behavior, we'll figure something out. Nearly everything is configurable; if you want to adjust some of the tests, or whatever, you can do that in your ~/.spamassassin/user_prefs. The system-wide config file is /etc/mail/spamassassin/local.cf, the system-wide defaults are listed in the man page for Mail::SpamAssassin::Conf, and the tests are defined in the files in /usr/share/spamassassin/. Hopefully, this is enough information for everyone to get started. If you have any questions about how this works, or what you should do, please ask. -- J. _______________________________________________ hosers-announce mailing list hosers-announce@xxxxxxxxxxx http://lists.ellipsis.cx/mailman/listinfo/hosers-announce