ESET NOD32 ANTIVIRUS - FOR LINUX-BSD MAIL SERVER Installation Manual page 24

and place it as a first in the DIRECTORS CONFIGURATION section and you have to define special ROUTERS
CONFIGURATION entry:
# ROUTERS CONFIGURATION
nod32_router:
driver = domainlist
route_list = "* localhost byname"
condition = "${if eq {$received_protocol}{virus-scanned} {0}{1}}"
transport = nod32_transport
verify = false
and place it as a first in the ROUTERS CONFIGURATION section. You have also define an appropriate TRANSPORTERS
CONFIGURATION entry responsible for e-mail messages delivery to nod32mda agent. Content of the entry is as follows:
# TRANSPORTS CONFIGURATION
nod32_transport:
driver = pipe
command = /usr/bin/nod32mda -oMr virus-scanned $local_part@$domain
user = mail
group = mail
Note that in RedHat Ready and/or Novell (SuSE) Ready variation of this anti-virus product the absolute path to
nod32mda module is different, so the definition of TRANSPORTS CONFIGURATION entry in this case is as follows:
# TRANSPORTS CONFIGURATION
nod32_transport:
driver = pipe
command = /opt/eset/nod32/bin/nod32mda -oMr virus-scanned $local_part@$domain
user = mail
group = mail
Make sure that the 'user' (usually 'mail') used in the above settings is listed in a 'trusted_users' list for this parameter.
Also be sure that the option 'qualify_domain' is undefined or set to your fully qualified domain name.
With the above settings you have ensured that all the e-mail messages originally sent to local domain user will
be primarily catched by nod32mda module. Yet there remains to provide that all messages processed by nod32mda
will be sent to the appropriate mailbox. To do so just modify parameter 'mda_path' within section [mda] of main
NOD32 configuration file. In case the absolute path to the exim is '/usr/sbin/exim' the parameter 'mda_path' will be
as follows.
mda_path = "/usr/sbin/exim"
To reread the newly created NOD32 configuration, enter the following command.
/etc/init.d/nod32d reload
To accomplish the whole procedure, one has to resatrt the MTA Exim.
Note that our product provides you with the option to define NOD32 scanner parameters individually for recipient
users (resp. recipient domains). In this case it is necessary to pass the information about the recipient user to nod32mda
module using its command line interface. Note that in case you would like to pass any command line parameter to the
whole nod32mda agent it is necessary to prepend the parameter by sentence '--' , otherwise the parameter will be
assumed to be passed to 'exim' specified by the 'mda_path' parameter. Thus for instance to pass command line option --

NOD32 for Linux/BSD Mail Server