ESET North America Server NOD32 사용자 설명서
Chapter 5. NOD32LMS basic configuration
5.2.2.5. Setting MTA Exim version 4
An MTA Exim version 4 stores its configuration in the file /etc/exim4/exim4.conf. The proce-
dure described here will therefore be done only with this one file and of course with the main
NOD32LMS configuration file (/etc/nod32/nod32.cfg) .
Please, note that the configuration described here is MDA independent by means it can be used
in cooperation with any MDA already working with Postfix MTA. First before any further steps,
please make a back-up of the original main Exim configuration file (for instance with the name
/etc/exim4/exim4.conf.orig). Now let’s look inside the content of the exim configuration file. It
is typicaly compound from the TRANSPORTERS and ROUTERS sections. Usually there should
be always ROUTER section responsible for messages local delivery (usually it is called ’loa-
caluser’). In order to configure exim to use NOD32LMS one has to define special ROUTER sec-
tion
dure described here will therefore be done only with this one file and of course with the main
NOD32LMS configuration file (/etc/nod32/nod32.cfg) .
Please, note that the configuration described here is MDA independent by means it can be used
in cooperation with any MDA already working with Postfix MTA. First before any further steps,
please make a back-up of the original main Exim configuration file (for instance with the name
/etc/exim4/exim4.conf.orig). Now let’s look inside the content of the exim configuration file. It
is typicaly compound from the TRANSPORTERS and ROUTERS sections. Usually there should
be always ROUTER section responsible for messages local delivery (usually it is called ’loa-
caluser’). In order to configure exim to use NOD32LMS one has to define special ROUTER sec-
tion
# ROUTER CONFIGURATION
nod32:
driver = accept
domains = +local_domains
condition = "${if and { {!eq {$received_protocol}{virus-scanned}} } {1}{0}}"
transport = nod32
and place this section before ROUTER section responsible for the local delivery.
One has also define appropriate TRANSPORTER section responsible to deliver e-mail messages
to nod32mda agent.
One has also define appropriate TRANSPORTER section responsible to deliver e-mail messages
to nod32mda agent.
# TRANSPORTS CONFIGURATION
nod32:
driver = pipe
command = /usr/bin/nod32mda $local_part@$domain
return_path_add
delivery_date_add
envelope_to_add
check_string = "From "
escape_string = ">From "
user = mailnull
group = mail
With the above setting we have ensured that all the e-mail messages sent to user belonging to
local domain will now be primarily sent to module nod32mda. Still there remains the second
part of the modification to provide that all messages processed by nod32mda will be sent to
the appropriate MAILBOX. In order to do so, we have to modify the parameter ’mda_path’
within the section [mda] of the main NOD32LMS configuration file (/etc/nod32/nod32.cfg) in
a following way.
local domain will now be primarily sent to module nod32mda. Still there remains the second
part of the modification to provide that all messages processed by nod32mda will be sent to
the appropriate MAILBOX. In order to do so, we have to modify the parameter ’mda_path’
within the section [mda] of the main NOD32LMS configuration file (/etc/nod32/nod32.cfg) in
a following way.
mda_path = "/usr/local/sbin/exim-deliver"
Now it is necessary to create the script file ’/usr/local/sbin/exim-deliver’ with the following
content.
content.
24