Skip to main content.
Techincal Support || Troubleshoot || Additional Software || System Bulletins


Internet Channel has been testing anti-spam technologies to help keep the often offensive unsolicited bulk e-mail out of the mailboxes of customers who do not want it.

We have chosen "SpamAssassin" to tag incoming e-mail as to its likelihood of being spam. "SpamAssassin" uses a points system to take many criteria into consideration when determining whether or not a message is spam. When these individual criteria (each is assigned a certain number of points) add up to more than a predetermined number (we default this number to 6) "SpamAssassin" calls the message spam.

"SpamAssassin" only marks the message to indicate its opinion as to whether or not the message is spam. We have configured this marking to be non-visible by default. It adds a few lines of text into the header of the message.

These lines are not normally displayed in most e-mail programs. However most e-mail programs are capable of filtering messages into special folders based on the information in these normally hidden headers. What you do with "SpamAssassin"'s judgment of the message is up to you. We merely provide the tool.

Here is an example of the headers added to a non-spam message:

X-Spam-Status: No, hits=0.6 required=6.0

Here is an example of the headers added to a spam message:

X-Spam-Status: Yes, hits=21.7 required=6.0
X-Spam-Flag: YES
X-Spam-Level: *********************
X-Spam-Checker-Version: SpamAssassin 2.43 (
X-Spam-Report:   21.70 hits, 6 required;
  *  2.2 -- Received contains a faked HELO hostname
  *  1.3 -- From: does not include a real name
  *  0.2 -- X-Mailer header indicates a non-spam MUA (Outlook Express)
  *  2.2 -- BODY: Tells you to 'take action now!'
  *  1.5 -- BODY: Talks about opting in
  *  1.3 -- BODY: Incorporates a tracking ID number
  *  0.7 -- BODY: List removal information   
  *  0.4 -- BODY: Says: "to be removed, reply via email" or similar
  *  0.4 -- BODY: Information on how to work at home (1)
  *  0.3 -- BODY: Act Now! Don't Hesitate!
  *  1.3 -- BODY: Spam phrases score is 13 to 21 (high)
            [score: 20]
  *  1.2 -- BODY: Includes a form which will send an email
  *  0.2 -- BODY: Includes a URL link to send an email
  *  0.7 -- URI: Includes a link to a likely spammer email address
  *  0.6 -- URI: Includes a URL link to send an email with the subject 'remove'
  *  0.4 -- URI: Includes a link to send a mail with a subject
  *  0.2 -- URI: Includes a 'remove' email address
  *  1.4 -- 'From' does not match 'Received' headers
  *  0.4 -- RBL: Received via a relay in
            [RBL check: found, type:]
  *  2.7 -- RBL: DNSBL: sender is Confirmed Spam Source
  *  1.3 -- message body is 25-50% uppercase
  *  0.4 -- HTML-only mail, with no text version

We have been running "SpamAssassin" for a few months now in testing and find it to be about 80-99% effective with a very low occurrence of false positives (incorrectly labeling a message as spam when it is actually a legitimate e-mail). Making personal changes to your SpamAssassin preferences can significantly increase the effectiveness and further reduce the possiblity of false positives. However, false positives are possible and you should not throw tagged messages away out of hand. You should first ask yourself how bad it would be for you to discard an important message.

We suggest filtering all tagged messages to a separate quarantine folder. You can either quickly scan the subject and sender of messages in that folder without being subjected to the content of those messages before deciding to view or delete the messages.

Some of the more likely candidates for false positives are:

You can configure your e-mail software to act on SpamAssassin's tagging of the messages using the instructions found on this web page.

We provide a mechanism whereby you can adjust the "SpamAssassin" settings for your personal e-mail to reduce the number of false positives and/or increase the effectiveness of "SpamAssassin" for your individual mix of e-mail. In the war against spam, there is no one configuration which will work for all users.

You can adjust your SpamAssassin preferences using this web site.

On the above site you can: