User Guide

14 Kaspersky Anti-Spam 3.0
The distribution package of Kaspersky Anti-Spam includes client plug-ins for
Sendmail, Postfix, Exim, Qmail and Communigate Pro.
As a rule, a client plug-in must be installed as a filter providing for receipt of
messages to be analyzed from the mail server and for the subsequent return of
modified e-mail.
Client plug-in modules are started by their respective mail servers. The sole
exception is Sendmail, which does not launch a client plug-in. Mail server can
start several client plug-ins for parallel processing of several letters. Please refer
to Appendix A.2 on page 84 for details on client plug-in modules and the
methods of their integration.
Irrespectively of the individual peculiarities of client modules, each module
interacts with the filtration server via a network or a local socket using internal
data exchange protocol.
Anti-Spam Engine responds to the requests of clients accessing it, receives
from them messages for analysis and returns the results.
The standard installation procedure assumes that the mail server with an
integrated client plug-in and the filtration server are installed on the same
computer.
However, the anti-spam engine of Kaspersky Anti-Spam can also be installed to
a separate server. In that case client modules running on another computer
(server) will exchange data with the filtration server through local network using
TCP.
Anti-Spam Engine running on a dedicated computer can serve several mail
servers at once provided that the performance of the computer it uses is
sufficient to process all that e-mail traffic.
Anti-Spam Engine consists of the following components:
• filtration module that performs message analysis
• licensing module, which checks the availability of a valid license key file
and compliance with the limitations specified in the purchased license
• daemon processing SPF requests
• script, which performs automatic downloads of content filtration databases
and compiles them
• Control Center
• Auxiliary programs and scripts.
Filtration master process (ap-process-server) is the main component of the
filtering module; it performs the following tasks:
• monitoring of requests from client modules for connection to the filtering
process