H-Sphere Reseller Guide

Spam Assassin Configuration Manager

2.4.1 and higher

 

To configure Spam Assassin from your admin control panel:

  1. Select Spam Assassin Manager in the Third Party Products menu.
  2. On the page that shows select mail server from the drop-down box and click Go.
  3. Configure parameters for the chosen mail server:
    • Rules Du Jour turn it on and check custom SpamAssassin rule sets whose newer versions you'd like to be automatically downloaded and updated.
    • Spamcheck minimal file size (Kb)
      Set the minimal file size of messages to be checked on spam. For instance, when you set 10Kb, the files that are 10Kb or more will subject to spam check. If the file size is less than 10Kb, the message will not be checked.
    • required_score
      Set the score required before a mail is considered spam. n.nn can be an integer or a real number. 5.0 is the default setting, and is quite aggressive; it would be suitable for a single-user setup, but if you're an ISP installing SpamAssassin, you should probably set the default to be more conservative, like 8.0 or 10.0. It is not recommended to automatically delete or discard messages marked as spam, as your users will complain, but if you choose to do so, only delete messages with an exceptionally high score such as 15.0 or higher. End users can choose their own spam check level to override the default one set. The larger the number of hist, the less aggresive spam check level: very_aggressive=2(hits),aggessive=4,normal=7,relaxed=10,permissive=14
    • rewrite_header Subject
      Text added to the "Subject:" line of mails that are considered spam. Note that you should only use the _REQD_ and _SCORE_ tags when rewriting the Subject header unless "report_safe" is 0. Otherwise, you may not be able to remove the SpamAssassin markup via the normal methods.
    • report_safe
      If this option is set to 1, an incoming message is tagged as spam, instead of modifying the original message, SpamAssassin will create a new report message and attach the original message as a message/rfc822 MIME part (ensuring the original message is completely preserved, not easily opened, and easier to recover). If this option is set to 2, then original messages will be attached with a content type of text/plain instead of message/rfc822. This setting may be required for safety reasons on certain broken mail clients that automatically load attachments without any action by the user. This setting may also make it somewhat more difficult to extract orview the original message.If this option is set to 0, incoming spam is only modified by adding some "X-Spam-" headers and no changes will be made to the body. In addition, a header named X-Spam-Report will be added to spam.
    • clear_headers
      Clear the list of headers to be added to messages. You may use this before any add_header options to prevent the default headers from being added to the message. Note that X-Spam-Checker-Version is not removable because the version information is needed by mail administrators and developers to debug problems. Without at least one header, it might not even be possible to determine that SpamAssassin is running.
    • use_bayes
      Whether to use the naive-Bayesian-style classifier built into SpamAssassin. This is a master on/off switch for all Bayes-related operations.
  4. Click Set.

 

Custom SpamAssassin Rule Sets

  • ANTIDRUG intended to detect common "pill spam" however, it is not appropriate for all environments. It may not be appropriate for a medical or pharmaceutical environment.
  • BIGEVIL looks for known spammer URLs in the spam.
  • BLACKLIST a blacklist of spammers.
  • BLACKLIST_URI looks for these domains inside URL's in the message.
  • BOGUSVIRUS lists bogus virus warnings and similar.
  • EVILNUMBERS addresses and phone numbers harvested from spam.
  • EVILNUMBERS1 addresses and phone numbers harvested from spam.
  • EVILNUMBERS2 addresses and phone numbers harvested from spam.
  • RANDOMVAL list of tags spammers sometimes forget to convert in spam.
  • SARE_ADULT designed to catch spam with "Adult" material.
  • SARE_BAYES_POISON_NXM using lists of words with equal length.
  • SARE_BML designed to catch "business, marketing and educational" spam.
  • SARE_BML_PRE25X designed to catch "business, marketing and educational" spam.
  • SARE_CODING contain HTML coding rules that detect various spammer tricks applied through HTML coding within messages.
  • SARE_FRAUD designed to catch "Nigerian 419", "International Lotto", etc. type scams.
  • SARE_FRAUD_PRE25X designed to catch "Nigerian 419", "International Lotto", etc. type scams.
  • SARE_HEADER contain Header rules that are not found in other SARE rule sets.
  • SARE_OEM tries to detect people selling OEM software to consumers.
  • SARE_RANDOM tries to detect common mis-fires on bulk mail software. Many signs are found like: %RND_NUMBER, etc.
  • SARE_SPECIFIC rule set which flags specific spam and/or spam from specific spammers.
  • SARE_SPOOF tries to detect common spoofing attempts by spammers. Many use a Message-ID of one provider but the message was never passed through the suggested system.
  • TRIPWIRE searches for 3 characters that shouldn't be together. This is based on the English language.
  •  



© Copyright 1998-2006. Positive Software Corporation.
All rights reserved.