Installation manual

17
[smtp]
agent_enabled = yes
listen_addr = "localhost"
listen_port = 2526
server_addr = "localhost"
server_port = 2525
action_av = "scan"
To provide individual parameter settings, define a ‘user_config’ parameter with the path to the special configuration file where
the individual setting will be stored. In the example below, we create a reference to the special configuration file
‘esets_smtp_spec.cfg’, which is located in the ESETS configuration directory. See below:
[smtp]
agent_enabled = yes
listen_addr = "localhost"
listen_port = 2526
server_addr = "localhost"
server_port = 2525
action_av = "scan"
user_config = "esets_smtp_spec.cfg"
Once the special configuration file is referenced from within the [smtp] section, create the ‘esets_smtp_spec.cfg’ file in the ESETS
configuration directory and add the appropriate individual settings. The ‘esets_smtp_spec.cfg’ file should look like this:
[[e-mail]]
action_av = "reject"
Note that the section header identifies the recipient for which the individual settings have been created, and the section body
contains individual parameters for this recipient. This configuration will allow all other users attempting to access the file-
system to be processed normally. All file system objects accessed by other users will be scanned for infiltrations, except for the
user [e-mail], whose access will be rejected (blocked).
7.3 Blacklist and Whitelist
In the following example we demonstrate blacklist and whitelist creation for the esets_smtp content filter for MTA Postfix
configuration. Note that the configuration described in the previous section is used for this purpose.
To create a blacklist used by esets_smtp, create the following group section within the special configuration file
‘esets_smtp_spec.cfg’, introduced in the previous section. See below:
[black-list]
action_av = "reject"
Next, add the SMTP server to the ‘black-list’ group. To do this, the following special section must be created:
[|[e-mail]]
parent_id = "black-list"
In the example above, ‘[e-mail]’ is the email address of the sender added to the ‘black-list’. All email
messages sent from this address will now be rejected. When creating the ‘white-list’ used by esets_smtp, it is necessary to create
the following group section in the special configuration file ‘esets_smtp_spec.cfg’. See below:
[white-list]
action_av = "accept"
action_as = "accept"
Adding the sender’s email address to the list is self-explanatory.
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 recipient 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.
7.4 Anti-Spam control
The anti-spam system filters spam messages, using dynamic evaluation of the data flow of the email delivery process.
To eliminate spam, ESET Mail Security uses the anti-spam control mechanism. This mechanism can be 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
only be used for email objects. Due to this, this functionality is relevant only for the following modules: esets_imap, esets_mda,
esets_pipe, esets_pop3, esets_smtp, esets_smfi and esets_cgp.
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