6.3. Black-list and white-list
In the next example we demonstrate the black-list and also white-list creation for the esets_
smtp congured as content lter for MTA Postx. Note that we use conguration described in the
previous section for this purpose.
Thus in order to create black-list used by esets_smtp we have to create the following group
section within the special conguration le‘esets_smtp_spec.cfg’ introduced in the previous
section.
[black-list]
action_av = ”reject”
The next step is to add some SMTP server into the ‘black-list’ group. For this purpose we have
to create special section
[|sndrname1@sndrdomain1.com]
parent_id = ”black-list”
where ‘sndrname1@sndrdomain1.com’ is an e-mail address of the sender added into the
‘black-list’. Note that with this setting all e-mail sent from this address will be rejected.
If we want to create the ‘white-list’ used by esets_smtp we have to create the following group
section within the special conguration le‘esets_smtp_spec.cfg’ introduced in the previous
section.
[white-list]
action_av = ”accept”
action_as = ”accept”
Adding of sender’s e-mail address into the list is self-explanatory.
Please, note the character ‘|’ placed in front of the header name of the special section in case
of sender address and not placed there in case of recipient address. To get description of the
special header name syntax, please refer to the appropriate ESETS agent module manual page.
For an esets_smtppleaserefertoesets_smtp(1)manualpage.
6.4. Anti-Spam Control
The goal of anti-spam system is to lter all spam e-mail messages, i.e. the e-mail messages
that the recipient users do not want, from data ow of the e-mail messages delivery process.
To get rid of spam, this product implements the anti-spam control mechanism. The anti-spam
functionalitycanbeenabledusingparameter‘as_enabled’(togetdescriptionoftheparameter
see esets.cfg(5) manual page). Note that anti-spam scanning can be used only for e-mail objects,
thus this functionality is relevant only for esets_imap, esets_mda, esets_pipe, esets_pop3,
esets_smtp and esets_sm modules.
Once anti-spam is enabled in any of the conguration sections the anti-spam scanning engine
is initialized during the main scanning daemon start-up. During this process an appropriate anti-
spam supporting modules are loaded from within the anti-spam cache directory.