ESET MAIL SECURITY, Installation Manual

Page: 24 / 42

24
ESET Mail Security
6.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:
[|sndrname1@sndrdomain1.com]
parent_id = ”black-list”
In the example above, ‘sndrname1@sndrdomain1.com’ 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.
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 ‘as_enabled’ 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: