15
not a full-blown MDA, it is rather a wrapper; the ‘mda_path‘ parameter in this case has the following format:
mda_path=“/usr/lib/sm.bin/sensible-mda“
To reread of newly created NOD32 conguration, enter the following command:
/etc/init.d/nod32d reload
To accomplish the whole procedure, one has to restart the MTA Sendmail.
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 original MDA specied by the ‘mda_path‘ parameter. Thus
for instance to pass command line option --user to nod32mda agent the above discussed parameter ‘A‘ of Sendmail
conguration le has to be dened in a following way:
A=nod32mda-t-Y-a$h-d$u----user$u
With this setting a special section [user], if dened in NOD32 conguration le, will be used by main NOD32 daemon
for scanning.
4.1.2.2. Setting NOD32MDA in Postx MTA
First one has to grab information on the MDA used by Postx. This can be found in Postx conguration le ’/etc/
postx/main.cf’. The Postx authors have written a helper utility ‘postconf‘ to work with the le, so we will use it in this
procedure. Thus by entering command
postconf mailbox_command
you can receive the following information on return:
mailbox_command=maildrop-d“$USER““$EXTENSION“
From the line above you can see that the MDA used by Postx is program called ’maildrop’. In order to replace the
original MDA by nod32mda module, enter the following command
postconf-e’mailbox_command=nod32mda-d“$USER““$EXTENSION“’
Keep in mind that the command line switches used in ’mailbox_command’ after the nod32mda component must
stay the same as in the original conguration le, otherwise the conguration may not work properly. The reason is that
the switches depend on the version of original MDA used by the Postx.
With the above modications you have ensured that all the e-mail messages originally sent to MDA will be catched
by nod32mda module rst. Still there remains to provide that all messages processed by nod32mda will be sent to the
original MDA for further delivery. To do so, just modify parameter ‘mda_path‘ within section [mda] of main NOD32
conguration le. In case of ’maildrop’ MDA the parameter ‘mda_path‘ will be as follows:
mda_path=“/usr/bin/maildrop“
For reread of newly created NOD32 conguration, enter the following command:
/etc/init.d/nod32d reload
To accomplish the whole procedure, one has to restart the MTA Postx.
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
chapter 4 / Integration with E-mail Messaging System