Chapter 2. Typical Patterns Of Application Deployment; Internal Architecture Of Kaspersky Anti-Virus - KAPERSKY ANTI-VIRUS 5.5 - FOR LINUX-FREEBSD MAIL SERVERS Administrator's Manual

CHAPTER 2. TYPICAL
PATTERNS OF APPLICATION
DEPLOYMENT
Depending on the initial architecture of the mail server, there are several options
for deploying Kaspersky Anti-Virus for Linux and FreeBSD Mail Servers:
•
On the same server with the e-mail software. This option is used when
the server is hosting a Sendmail, Qmail, Postfix or Exim mail software
(see section 2.2 on page 13).
•
On a dedicated server as a secondary filter: This option is recommended
when the primary mail server is running an unsupported operating and/or
mail system (see section 2.3 on page 14).
•
As a filter for external mail services. This option is useful when mail server
users have their mailboxes on external servers, in order to provide antivi-
ral protection of downloaded mail messages (see section 6.5 on page 62).
In all these cases, Kaspersky Anti-Virus can both filter mail traffic and scan all
mounted file systems.
Prior to studying the above deployment patterns in detail, we shall review the
internal architecture of Kaspersky Anti-Virus in order to fully understand its
operational algorithm.
2.1. Internal architecture of
Kaspersky Anti-Virus
When using Kaspersky Anti-Virus, it is important to understand its operational
algorithm.
This section reviews the application's internal architecture, concentrating on mail
traffic scanning, since the process of scanning server file systems is
comparatively straightforward and does not require a special in-depth study.
It should be noted that Kaspersky Anti-Virus is only capable of scanning mail for
viruses, and does not constitute a mail agent capable of receiving and routing
mail traffic. This must be carried out by a mail system installed on the server,
with which the anti-virus program is integrated after installation.