162018-05-06 17:53:13ClintonEbadiremove some old cruft about shared-folder (create-user will create them now, and mire migration finished a decade ago). still needs work.152013-01-14 09:13:53ClintonEbadicat142013-01-08 20:31:43ClintonEbadicopy the example exim filter in line132008-07-07 04:27:49localhostconverted to 1.6 markup122007-12-18 01:09:27AdamChlipalaBad link112007-12-15 17:30:11AdamChlipalamembers2 -> members102007-12-09 01:17:18MichaelOlsonAdd section for removing old spam training data92007-12-02 20:25:38FrankBynum82007-11-27 16:15:23pod1-4.cs.purdue.eduMention proper contents of shared-folders file --mwolson72007-11-09 06:14:22RyanMikulovskynevermind about request for clarification.62007-11-09 06:09:11RyanMikulovskyadd request for clarification of SpamAssassin shared folders52007-11-04 22:59:50AdamChlipala42007-11-01 21:47:37MichaelOlsonMove ntk's example to EximFilter page32007-11-01 21:32:12MichaelOlsonFix logfile path22007-11-01 20:52:14MichaelOlson12007-11-01 20:49:29MichaelOlsonInitial contentsThis page describes how to use SpamAssassin to keep junk email under control.

You will probably want to set up SpamAssassin to detect junk e-mail for you. SpamAssassin is a program for categorizing e-mail as spam based on a wide range of criteria. It indicates its decisions by adding special headers to messages. Please note that we will never reject any spam email before it hits your filtering rules. It is up to you to decide how to classify the email that hits your inbox.

We use a custom tool called setsa to determine whether your email should be run through SpamAssassin. To enable SpamAssassin for mail to your UNIX account, run To later disable it, run To check whether you've enabled it or not, run You can similarly enable or disable SpamAssassin for a virtual mailbox address by adding it as the first argument to setsa; for example, setsa user@domain.com on enables SpamAssassin for user@domain.com if you have DomTool permissions for domain.com. Please don't enable this if you can't commit to following the training procedure below when SpamAssassin makes an incorrect classification! SpamAssassin makes small mistakes over time, and this can interact poorly with its automatic learning of which message properties signify spam. If you don't correct its small misclassifications, then these increase the chance of misclassifying future messages, which itself leads to more faulty learning, vicious cycle style.

The above procedure only asks SpamAssassin to examine your mail and add extra headers indicating its verdict, spam or legit. To use these headers to move junk mail to a folder called Spam in your IMAP mailbox, copy the following template to ~/.public/.forward. This is an Exim filter that looks for SpamAssassin headers that indicate spamhood. You need to create a Spam folder manually to use this. You can modify this template to save spam to other places, if you don't use IMAP or prefer another scheme. (If you already have a ~/.public/.forward file because you forward all of your mail to another account elsewhere, then you can ignore this section. You should use that e-mail provider's spam filtering services.) SpamAssassin flags spam with a spamminess level of 5.0 or higher. You can use the X-Spam-Level: header to customize your own filter to your own liking, however. As an example, you can see NathanKennedy's .forward file on the MemberManual/Email/EximFilter page.

One way that SpamAssassin spots spam is by using statistical (Bayesian) analysis. This requires lots of training data to work properly. Sometimes this analysis will make mistakes, and you'll want to perform the electronic equivalent of slapping it with a newspaper. The way to do that is to deposit misclassified mail in special system-wide IMAP folders, one called SiteSpam for spam that SpamAssassin missed and one called SiteHam for good messages that were erroneously marked as spam. If you ever run into this situation, here's how you can feed our system-wide trainer: First, this is only going to work if you are using IMAP (our webmail is using IMAP, so that can be used). If you're not, or if you have other sources of spam or ham that you'd like handled specially, place a support request on the portal. Use your IMAP client's "subscribe" feature to subscribe to SiteSpam and/or SiteHam, which should appear in the SpamAssassin mailbox inside the shared tree. If you don't see the shared tree, then file a support request. When you want a message to be used as an example of spam or ham, place a copy of it in the appropriate folder. Every five minutes, our faithful spamhound will sniff these folders, update its data, and clear their contents. If you would like to automate this process somewhat, check out FeedingSpamAssassin. For the curious and the sysadmins out there, SpamAssassinAdmin gives more details on how we set this up. CategoryMemberManual CategoryNeedsWork