User Guide
Chapter 6 87
ClientFilteringSizeLimit 500
ClientDefaultDomain localhost
In addition to the settings described earlier in the appendix A.2.2, for the kas-
milter module you can set the SendMailAddress parameter in the filter.conf file,
which defines the socket for interaction with Sendmail.
To set up Sendmail for interaction with kas-milter, add the following lines to the
sendmail.cf configuration file:
Xkasfilter,S=local:/var/run/kas-milter.socket, T=C:10s,S:20s,
R:30s
O InputMailFilters=kasfilter
The detailed information on configuring sendmail.cf filters is available in the
Sendmail documentation.
Generally, when operating system is loading, Sendmail starts before
Kaspersky Anti-Spam. Because of this, Sendmail cannot find the
interaction socket and writes the following warning message to the
system log:
WARNING: Xkas: local socket name <socket_file>
missing
This warning does not indicate a failure because the missing socket file
is created by the kas-milter module after execution of Kaspersky Anti-
Spam.
The specifics of using kas-milter module with the Sendmail mail server:
• kas-milter does not create copies of messages during processing; which
means that if the message is sent to a number of recipients belonging to
different groups with different processing rules, then the message is
processed according to the settings defined in all groups. Example:
A message is sent to the alice@mycompany.com and
bob@mycompany.com e-mail addresses. These e-mail addresses belong
to the sales and managers groups respectively. According to the filtering
results, the message received the Spam status for the sales group and
Not detected for the managers group. According to the rules defined for
the sales group, the subject line of each message recognized as spam
(having the Spam status assigned) is modified with the tag [!! SPAM],
and the rules defined for the managers group state that all messages
with Not Detected status should be accepted. As a result, the mail
message with [!! SPAM] tag in the subject line is delivered to the both
recipients. The message contains the following headers:
X-Spamtest-Status-Extended: SPAM
X-Spamtest-Status-Extended: Not detected










