JSpamFilter computes a "score" based on its analysis of an incoming email message. The score is determined
by the lookup settings (see Part 9 (DNSBL and SURBL Look-Up Configuration))
and the entries in the filter file. The score can be thought of as a relative "open-ended" probability: the bigger
score, the more likely the message is spam email.
The Block and Tag thresholds determine the values at which different "actions" occur:
- When setting the Block and Tag thresholds, set the Block threshold higher than the tag threshold.
- If the score exceeds the "block" threshold, the connection is Blocked.
- If the score exceeds the "tag" threshold, the message is Tagged.
If not overridden in the DNSBL entry (see JSpamFilter Manual Part 9
(DNSBL and SURBL Configuration)), this specifies the default
action to use for "hits" on a DNSBL. If set to "block", the
server will drop connections with a "550 service not available" error;
if "tag", a "[JSpamFilter]" tag will be prepended to the
Subject line of any message from a suspicious source. The default is Tag.
Mandatory when using tagging, even if not using a filter file.
This is the score at which JSpamFilter will tag the e-mail. Note:
If a message is on a "Tag" DNSBL list, the score starts
at this value; this makes it so that messages that are already suspect are
more likely to be blocked.
Optional. The score at which JSpamFilter will block
the e-mail. In JSpamFilter Enterprise, messages on "Block" DNSBLs
start at this score.