User Guide

46 Kaspersky
®
SMTP-Gateway 5.5 for Linux/Unix
If the auto archiving option is enabled, copies of the following messages will be
archived:
• All incoming messages, including infected objects, without additionally
notifying the administrator. Archiving of such messages is enabled when
the path to the archive directory is specified as the value of the
IncomingArchivePath parameter in the [smtpgw.path] section).
• Outgoing messages, including those delivered to recipients, blocked
because of a virus, and notifications generated by the application.
Archiving of such messages is enabled when the path to the archive
directory is specified as the value of the OutgoingArchivePath
parameter in section [smtpgw.path]).
Before you enable automatic archiving, make sure that there is enough
space in your server’s file system to accommodate the archive.
Do not forget to purge this directory from time to time to remove old
messages and compress necessary files (the frequency of that
procedure depends on the mail traffic intensity within your network).
4.3. Protection from hacker attacks
and spam
To provide the highest level of security for your mail system, we recommend that
you modify the Kaspersky SMTP-Gateway configuration file to extend the anti-
virus functionality of the application. To protect your server from hacker attacks
or, for example, to prevent spam being relayed through your server, configure
the following options:
• ConnectRule in the [smtpgw.access] section. The parameter defines
application behaviour during establishment of an SMTP session.
• HeloRule in the [smtpgw.access] section. The parameter defines
application response to HELO/EHLO command received from a client.
• MailfromRule in the [smtpgw.access] section. The parameter defines
application behaviour at an attempt to send a message from a source
(passed with MAIL FROM command) with a domain name, which does
not match the actual IP address or MX host corresponding to that domain.
• RelayRule in the [smtpgw.access] section. The parameter defines the
rules for client access to gateway. Correct settings of that option are
essential for prevention of application use as a publicly open mail relay.
A detailed discussion of the syntax of these parameters is provided in
the description of the configuration file (see A.2 on p. 82).