Introduction | Installation | Status Window | General Preferences
Virus Preferences | Spam Preferences | Logging | Winnow
Training Addresses | Whitelists/SpamTraps

Documentation - Spam Preferences

Spam Thresholds
Spam Score determines at what score an email is deemed to be spam. The default is 5.0.
Can Spam determines at what score email is not delivered. This score can be equal to or greater than the Spam Score. It can also be set to Never in which case all email is delivered.

You can choose to bounce spam that has exceeded the 'Can Spam' score by checking the box. However, be warned - if you use this option, you WILL be bouncing mail to forged addresses which can result in your server being blacklisted. Use this option with caution. You can customize the bounce message by editing the file located here: 'Counteragent 2:Counteragent Files:Templates:spam_bounce.txt'.

Scoring Options
These options allow you to turn on/off the automatic learning features of SpamAssassin.

• Use Bayes Database: This option toggles the SpamAssassin Bayes database on and off. With this off, the Bayes database will not be used to enhance spam scores. The default is on.
• Bayes Auto Learn: This option toggles auto learning of mail on and off. When this is off, mail can still be manually trained using the training addresses.
• Use Auto Whitelist: This option toggles the SpamAssassin Auto Whitelist on and off.

Reporting Options
The first three options determine how spam messages are handled.

• Deliver (Spam Headers Added): Adds the SpamAssassin headers showing the message is spam. In the end user's email client, they can filter their email on the X-Spam-Status or X-Spam-Score headers.
• Mark and Deliver (Subject Rewritten): In addition to the SpamAssassin headers, this option prepends the Subject with "****SPAM****". The end user can then filter the email based upon the Subject, the X-Spam-Status header, or the X-Spam-Score header.
• Deliver as Attachment w/Report: SpamAssassin creates a new email that lists the tests that caused the email to score as spam. It then attaches the original message to the report email. This allows the original unaltered message to be easily retrieved. End uses can still filter on the SpamAssassin headers.

** Note: If you have set the Can Spam threshold to the same as your Spam Threshold, then the above options are moot because no spam email will be delivered to the end user. This is a perfectly legitimate thing to do, but you should keep it in mind.

• Send Spam Report to Admin: This is useful for verifying that SpamAssassin is properly tagging email. An Admin Spam Report is sent to the admin email address with the spam message as an attachment. This attachment maintains its Mac resource forks and can be delivered by dropping the attached message file into 'EIMS Folder:Mail Folder:Incoming Mail'.
• Report Canned Spam to Databases: This reports canned spam to spam databases. This at least includes SpamCop and can include other databases if you install the appropriate SpamAssassin plugins like DCC, Razor, or Pyzor.
• Report Spamtraps to Database: Similar to the above, it reports email received at your SpamTrap addresses to the spam databases.

Introduction | Installation | Status Window | General Preferences
Virus Preferences | Spam Preferences | Logging | Winnow
Training Addresses | Whitelists/SpamTraps