Installation manual

14
6. Important ESET Mail Security mechanisms
6.1 Handle Object Policy
The Handle Object Policy (see figure 6-1) mechanism provides filtering of scanned objects based on their status. This
functionality is based on the following configuration options:
action_av
action_av_infected
action_av_notscanned
action_av_deleted
For detailed information on these options, please refer to the esets.cfg (5 ) man page.
Figure 6-1. Scheme of Handle Object Policy mechanism.
Every object processed is first handled according to the configuration of the ‘a ction_a v‘ option. If this option is set to ‘a ccept’
(or ‘d efer’ , ‘d isca rd’ , ‘reject’ ) the object is accepted (or deferred, discarded, rejected). If the option is set to ‘sca n’ the object is
scanned for virus infiltrations, and if the ‘a v_clea n_m o d e ’ option is set to ‘yes ’, the object is also cleaned. In addition, the
configuration options ‘a ction_a v_in fected ’, ‘a ction_a v_no tsca n ned ’ and ‘a ction_a v_deleted ’ are taken into account to further
evaluate handling of the object. If an ‘a ccept’ action has been taken as a result of these three action options, the object is
accepted. Otherwise, the object is blocked.
6.2 User Specific Configuration
The purpose of the User Specific Configuration mechanism is to provide a higher degree of customization and functionality. It
allows the sytem administrator to define ESETS antivirus scanner parameters based on the user who is accessing file system
objects.
A detailed description of this functionality can be found in the esets.cfg (5 ) man page; in this section we will provide only a
short example of a user-specific configuration.