Installation manual

45
3.3.2.1.7 Score
Turn on score history - Enables tracking of historical scores for repeat senders.
Stop analysis when SPAM score threshold has been reached - This option allows you to tell the antispam engine
to stop analyzing the message once a score has been reached. This can reduce the number of rules and other checks
that are performed, thus improving throughput.
Use accelerated analysis before threshold score for a clean message has been reached - This option allows you
to tell the antispam engine to skip slow rule checks if the message is likely to be ham.
Message categorization
Score value from which a message is regarded as SPAM: - Antispam engine assigns scanned message a score
from 0 to 100. Setting the score value borders affects what messages are considered as SPAM and what
messages aren't. If you set incorrect values, it may decrease quality of the antispam engine's detection results.
Score value which sets a border when a message is regarded as probable SPAM or probably clean: -
Antispam engine assigns scanned message a score from 0 to 100. Setting the score value borders affects what
messages are considered as SPAM and what messages aren't. If you set incorrect values, it may decrease quality
of the antispam engine's detection results.
Score value up to which a message is regarded as certainly clean: - Antispam engine assigns scanned
message a score from 0 to 100. Setting the score value borders affects what messages are considered as SPAM
and what messages aren't. If you set incorrect values, it may decrease quality of the antispam engine's detection
results.
3.3.2.1.8 Spambait
Spam addresses: - If the RCPT TO: address from SMTP envelope matches an email address in this list, then the
statistics file will record tokens in email message as being sent to a spambait address. Addresses must match
exactly ignoring case, wildcard entries are not supported.
Addresses regarded as nonexistent: - If the RCPT TO: address from SMTP envelope matches an email address in
this list, then the statistics file will record tokens in email message as being sent to a nonexistent address.
Addresses must match exactly ignoring case, wildcard entries are not supported.
3.3.2.1.8.1 Spambait addresses
You can set email addresses which will only receive SPAM. To add an email address, type it in a standard format and
press Add button. To modify existing email address, use Edit button. To delete, press Remove button.
3.3.2.1.8.2 Addresses regarded as nonexistent
You can set email addresses which will appear as nonexistent to the outside. To add an email address, type it in a
standard format and press Add button. To modify existing email address, use Edit button. To delete, press Remove
button.
3.3.2.1.9 Communication
Single SpamLabs request duration (in seconds): - Limit how long single request to the Antispam protection
SpamLabs can take. The value is specified in units of integral seconds. The value of "0" disables this feature and no
limit will be placed.
Use v.4x protocol: - Communicate with the Antispam protection SpamLabs to determine scoring via old slower v4.
x protocol. When you set this option to Automatically, it allows Antispam engine to automatically use the
netcheck feature as a fallback to LiveFeed queries.
Range of v4.x protocol usage: - Since networks can introduce latency and a decrease in performance, this
option allows running network checks conditionally based on the score. Network is only queried if score is at or
between the "low" and "high" range specified via this option.
LiveFeed server address: - Specifies which server to query for LiveFeed requests.
LiveFeed request lifetime (in seconds): - This option allows setting a minimum TTL for entries in the antispam