Chapter 2. Typical Patterns Of Product Deployment; Internal Architecture Of Kaspersky Anti-Virus - KAPERSKY ANTI-VIRUS 5.0 - FOR LINUX FREEBSD-OPENBSD MAIL SERVER Administrator's Manual

CHAPTER 2. TYPICAL
PATTERNS OF PRODUCT
DEPLOYMENT
Depending on the initial architecture of the mail server, we offer several variants
of deployment of Kaspersky Anti-Virus
On a single mail server with mail system. This variant is used when the
server has an installed and adjusted mail system sendmail, qmail, Postfix
or Exim (see section 2.2 on page 14).
On a dedicated server as a secondary filter: This method is
recommended when the primary mail server is running an unsupported
operating and mail system (see section 2.4 on page 17).
On a single server with mail system as a secondary filter: This variant of
deployment is recommended in the event that a mail filter, such as
Kaspersky Anti-Spam, is installed on the mail server (see section 2.3 on
page 16).
As a filter for external mailboxes. This method of deployment is useful in
the event that mail server users have their mailboxes on external servers
and it is necessary to provide antiviral protection of downloaded mail
messages (see section 2.5 on page 19).
In all the cases mentioned above, besides filtering mail traffic, Kaspersky Anti-
®
Virus can also scan all mounted file systems.
Prior to studying the above deployment patterns in detail, we shall review the

internal architecture of Kaspersky Anti-Virus

operation algorithm.
2.1. Internal architecture of
Kaspersky Anti-Virus
When using Kaspersky Anti-Virus
algorithm.
In this section, we shall review the product's internal architecture, especially as
applied to mail traffic scanning , since the process of scanning server file
systems is quite simple and does not require a special in-depth study.
®
for Unix Mail Servers:
®
in order to fully understand its
®
, it is important to understand the operation
®