SpamAssassin Tips

Tips for making SpamAssassin work better for you....

• Losing emails?
  • FalsePositives: Is your Ham being matched incorrectly as Spam?
  • AutoWhitelist: The SpamAssassin AWL - historical score-averaging for each sender
• Spam getting through?
  • UsingNetworkTests: Turning on the network rules to improve accuracy
  • BayesInSpamAssassin: Training the Bayesian learner
  • WritingRules: How to write and test new rules
  • Third party "drop-in" CustomRulesets and CustomPlugins
  • TrustPath: Fixing the "ALL_TRUSTED" problem.
  • RuleUpdates: Using sa-update to publish and/or receive rule updates.
• General info:
  • UpgradingVersion: Upgrading is quick and easy
  • FrequentlyAskedQuestions: General questions, not errors (see FixingErrors for that)
  • FixingErrors: Things that can go wrong and how to fix them
• Performance Tips:
  • FasterPerformance: DNS resolution, Using Spamd, Other good tips.
  • ChooseYourRules: Everyone's Spam is different
• ThankTheTeam

Here are some of the ways SpamAssassin can be used:

• UsedViaProcmail: run from the traditional UNIX .procmailrc file
• UsingSiteWide: using SpamAssassin site-wide
• IntegratedInMta: built into the whole mail-delivery process in the Mail Transfer Agent (sendmail, Exim, Postfix etc.)
• MailProxy: as a proxy server
• Run against a RemoteImapFolder
• UsingOnOsx
• UsingOnWindows
• CommercialProducts: commercial products that use SpamAssassin internally
  
• Really needed docs - someone please add this, "What if Spam Assasin is installed already on your ISP's mailserver and it doesn;t do anything. Where are docs for seting filter rules?" Or is this just not how it works and is this not something for people who are not Unix administrators to consider?