Content Filtering In Mta Exim 4 - ESET NOD32 ANTIVIRUS - FOR LINUX-BSD MAIL SERVER Installation Manual

user to nod32mda agent, the parameter 'command' defined in TRANSPORTS CONFIGURATION entry must by as follows:
command = /usr/bin/nod32mda -oMr virus-scanned $local_part@$domain \
-- --user $local_part
resp. in case of RedHat Ready and Novell (SuSE) Ready variation of this anti-virus product used, the ' c ommand'
parameter has to be defined as follows:
command = /opt/eset/nod32/bin/nod32mda -oMr virus-scanned $local_part@$domain \
-- --user $local_part

4.3.4. Content filtering in MTA Exim 4

Let's look inside the exim configuration file '/etc/exim4/exim4.conf' to become familiar with its content. It is typically
compound from TRANSPORTS CONFIGURATION section and ROUTERS CONFIGURATION section. In order to configure exim
to use our anti-virus as a content filter you have to define special ROUTERS CONFIGURATION entry in a following way:
# ROUTER CONFIGURATION
nod32_router:
driver = accept
condition = "${if eq {$received_protocol}{virus-scanned} {0}{1}}"
transport = nod32_transport
verify = false
Note that above entry has to be placed 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 = mailnull
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 = mailnull
group = mail
Make sure that the 'user' (usually 'mailnull') is the value of ' e xim_user' or pick a name fromthe list 'trusted_users' for
this parameter. Also be sure that the option ' q ualify_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. Still 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
chapter 4 / Integration with E-mail Messaging System
5