| In the following sections we will show how JSpamFilter provides a variety of tests to determine whether an incoming connection or message
can be identified as coming from a sender of spam email and how JSpamFilter then offers several options for handling the mail after testing. |
|
JSpamFilter utilizes two basic types of tests:
- Source Tests: Tests Based on Who Is Sending the Message
- Content Tests: Tests Based on Message Content and Attachments
|
JSpamFilter then provides several treatment options based on the outcome of the tests:
- Refuse, Block, Tag, or Leave Untouched
|
| The result of the tests* is the construction of a score that is a measure of the likelihood of a message being spam.
This can be thought of as a relative, open-ended probability. The action that JSpamFilter takes is based on the value of the score relative to the thresholds established by the Administrator. |
| *The score can be over-ridden if a DNSBL is set to "REFUSE" as described in the later section on DNSBL action levels. |
|
| We're going to first discuss the treatment options (refuse, block, tag, leave untouched), as the tests are best understood in the light of how the message can be handled after the test. |
