Installation manual

18
directory.
Regular updates of the anti-spam database can be administered using tasks in Scheduler. Anti-spam functionality can also be
configured using the following configuration file:
@ETCDIR@/anti-spam/spamcatcher.conf
Note: SpamCatcher is a tool for spam detection. It tracks all email communication on its own server and monitors messages
rejected by users. It evaluates this and various other data to determine which email is likely to contain spam and sends users a
probability score for every message they receive. It allows you to create your own rules for identifying and blacklisting spam.
Hundreds of rules can be used to evaluate spam score and block the incoming spam.
The @ETCDIR@/anti-spam/ directory contains a number of different configurations stored in files, that can be used to
customize the anti-spam engine. If you wish to start using a particular configuration, replace the default anti-spam
configuration stored in ‘spamcatcher.conf’ with any of the available configuration files and then reload the ESETS daemon.
spamcatcher.conf
Is a default configuration file, that contains optimal configuration recommended for typical server environment.
To display differences between any of the files in the anti-spam directory, use the diff command. For example, if you wish to
compare the spamcatcher.conf and the spamcatcher.conf.accurate files use the following command:
diff spamcatcher.conf spamcatcher.conf.accurate
spamcatcher.conf.accurate
Bayesian Word Token analysis (i.e. spam filtering using Bayesian Analysis) is enabled. It improves accuracy, but uses more
memory and can therefore take slightly more time to finish than other methods.
The limit of the number of domains queried against the DNS Block List server (DNSBL) is increased (the ‘dnsbl_max_domains’
option). DNSBLs are most often used to publish addresses of computers or networks linked to spamming.
Sender Policy Framework (SDK) with live DNS queries will be performed.
The value of the ‘spam_threshold’ parameter is increased. Messages with spam scores equal to or higher than this value will
be rejected.
The SpamCompiler version 4 is enabled.
spamcatcher.conf.fast
The number of domains queried against the DNS Block List server is reduced.
The option ‘target_throughput’ allowing you to specify throughput in messages per second is enabled.
Cpu usage during rule file updates is reduced by increasing the size of on-disk cache files.
TTL's (Time to live) for internal DNS and LiveFeed caches are enabled.
spamcatcher.conf.no_livefeed
The ‘livefeed’ option specifies which server is queried for LiveFeed requests. This option is disabled in this configuration file.
The internal cache for DNS requests is disabled.
7.4.1 SpamCatcher settings
The spamcatcher.conf configuration file allows you to modify several additional settings that are not available in the ESETS
confugration file. The settings in spamcatcher.conf are transparently structured and described:
Name – parameter name
Arguments – values the parameter can be assigned and their syntax
Default – default parameter value
Description – detailed parameter description
Blank lines and lines beginning with # are omitted.
A list of the most important settings in spamcatcher.conf
Parameter name
Details
approved_ip_list
List of approved IP addresses. You can specify IPs that should be approved, i.e., if the first non-ignored
IP in Received headers matches any address in this list, the message scores 0 and no other checks are
made.
blocked_ip_list
List of blocked IP addresses. You can specify IPs that should be blocked, i.e., if any non-ignored IP in
Received headers matches the address in this list, the message scores 100 and no other checks are
made.