Appendix A
91
user=mailflt3 argv=/usr/local/ap-mailfilter3/bin/
kas-pipe
127.0.0.1:9025 inet n - n - 25 smtpd
-o smtpd_authorized_xforward_hosts=127.0.0.0/8
-o local_recipient_maps=
-o relay_recipient_maps=
-o smtpd_restriction_classes=
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=
permit_mynetworks,reject
-o mynetworks=127.0.0.0/8
-o strict_rfc821_envelopes=no
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
-o receive_override_options=
no_address_mappings
kas3scan unix - - n - 10 smtp
-o smtp_send_xforward_command=yes
### KASPERSKY ANTI-SPAM END ###
For Postfix version 2.1 and higher, you can configure
kas-pipe
to act as a
proxy filter (
smtpd_proxy_filter
). In this case, the
reject
action is used during
SMTP sessions, which speeds up message processing. However, such a
configuration is recommended only when a mail server is not heavily loaded.
To configure kas-pipe to act as a proxy filter, replace the first two lines in the
example above with the following:
smtp inet
n
-
n - - smtpd
-o smtpd_proxy_filter=127.0.0.1:9026
A.2.4.2. Configuring
Exim to work with kas-pipe
You can integrate kas-pipe into the Exim mail server by adding a new router at
the beginning of the router list in the Exim configuration file and adding the
transport for this router that will be used to start kas-pipe. This router is of a
conditional type because it will not be used to process main sent locally using the
ESMTP protocol.
