Anti-Spam Control; Samples Submission System; Web Interface - ESET MAIL SECURITY - FOR LINUX BSD AND SOLARIS Installation Manual

The '|' character is placed in front of the header name of the special section for the sender address and is not placed
there for the recnano ipient address. For information regarding the special header name syntax, refer to the man page
of the appropriate ESETS agent module. For esets_smtp, refer to the esets_smtp(1) man page.

6.4 Anti-Spam Control

The anti-spam system filters all spam email messages, i.e., email messages that recipients do not want, from the
data flow of the email messaging delivery process.
To eliminate spam, ESET Mail Security uses the anti-spam control mechanism. This mechanism is enabled using the
'action_as' parameter. For a full description of the parameter refer to the esets.cfg(5) man page. Note that anti-spam
scanning can be used only for email objects. Thus, this functionality is relevant only for the following modules:
esets_imap, esets_mda, esets_pipe, esets_pop3, esets_smtp and esets_smfi.
Once anti-spam is enabled in any of the configuration sections, the anti-spam scanning engine initializes during the
main scanning daemon start-up. During this process, appropriate anti-spam support modules are loaded from the
anti-spam cache directory.
Anti-spam functionality can also be configured using the following configuration file:
@ETCDIR@/anti-spam/spamcatcher.conf
The number of files within this directory is equal to the number of different settings of the anti-spam engine. The
default configuration file corresponds to optimal configuration recommended for typical server environment. In order
to use any of the files, replace the default antispam configuration file 'spamcatcher.conf' with the chosen one and
reload the ESETS daemon.
To define the period (in minutes), after which ESETS will check for available antispam module updates, edit the entry
shown below in the ESETS configuration file. If you do not set this parameter, ESETS will not regularly update its
antispam database:
as_update_period = 60

6.5 Samples Submission System

The Samples submission system is an intelligent ThreatSense.Net technology that collects infected objects which
have been detected by advanced heuristics and delivers them to the samples submission system server. All virus
samples collected by the sample submission system will be processed by the ESET virus laboratory and if necessary,
added to the ESET virus signature database.
NOTE: According to our license agreement, by enabling sample submission system you are agreeing to allow the
computer and/or platform on which the esets_daemon is installed to collect data (which may include personal
information about you and/or the user of the computer) and samples of newly detected viruses or other threats and
send them to our virus lab. This feature is turned off by default. All information collected will be used only to analyze
new threats and will not be used for any other purpose.
In order to activate the Samples Submission System, the samples submission system cache must be initialized. This
can be achieved by enabling the 'samples_enabled' option in the [global] section of the ESETS configuration file. To
allow for the actual delivery of samples to the ESET virus laboratory servers, the parameter 'samples_send_period'
must also be specified in the same section.
In addition, users can choose to provide the ESET virus laboratory team with supplementary information using the
'samples_provider_mail' and/or 'samples_provider_country' configuration options. The information collected using
these options will assist in providing the ESET team with an overview about a given infiltration which may be
spreading over the Internet.
For more information on the Samples Submission System, refer to the esets_daemon(8) man page.

6.6 Web Interface

The Web Interface allows user-friendly configuration, administration and license management of ESET Security
systems. This module is a separate agent and must be explicitly enabled. To quickly configure the Web Interface, set the
following options in the ESETS configuration file and restart the ESETS daemon:
16