18
condition=“${ifeq{$received_protocol}{virus-scanned}{0}{1}}“
transport = nod32_transport
verify = false
Note that above entry has to be placed as a rst of the DIRECTORS CONFIGURATION section. You also have to dene
an appropriate TRANSPORTERS CONFIGURATION entry responsible for e-mail messages delivery to nod32mda agent.
Content of the entry is as follows:
#TRANSPORTSCONFIGURATION
nod32_transport:
driver = pipe
command=/usr/bin/nod32mda-oMrvirus-scanned$local_part@$domain
user=mail
group=mail
Note that in RedHat Ready and/or Novell (SuSE) Ready variation of NOD32 for Linux Mail Server the absolute path to
nod32mda module is dierent, so the denition of TRANSPORTS CONFIGURATION entry in this case is as follows:
#TRANSPORTSCONFIGURATION
nod32_transport:
driver = pipe
command=/opt/eset/nod32/bin/nod32mda-oMrvirus-scanned$local_part@$domain
user=mail
group=mail
Be 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 undened or set to your fully qualied 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 conguration le. 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 conguration, enter the following command:
/etc/init.d/nod32d reload
To accomplish the whole procedure, one has to restart the MTA Exim.
Note that NOD32LMS/NOD32BMS provides you with the option to dene NOD32 scanning engine 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‘ specied by the ‘mda_path‘ parameter. Thus for
instance to pass command line option --user to nod32mda agent, the parameter ‘command‘ dened in TRANSPORTS
CONFIGURATION entry must by as follows:
command=/usr/bin/nod32mda-oMrvirus-scanned$local_part@$domain\
----user$local_part
resp. in case of RedHat Ready and Novell (SuSE) Ready variation of NOD32 for Linux Mail Server used, the ’command’
NOD32 for Linux/BSD Mail Server