User Guide

Appendix A 105
127.0.0.1:9026 inet n n n - 20 spawn
user=mailflt argv=/usr/local/ap-mailfilter/bin/kas-pipe
-c /usr/local/ap-mailfilter/etc/kas-pipe-postfix.conf
127.0.0.1:9025 inet n - n - 25 smtpd
-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
For Postfix 2.1 and above kasp-pipe may be used as a proxy filter
(smtpd_proxy_filter) rather then the content filter (content_filter). This results in
faster processing of mail messages as the unnecessary waiting in the queue will
be avoided.
smtp inet n - n - - smtpd
-o smtpd_proxy_filter=127.0.0.1:9026
A.3.3.4. Configuring Exim when using
kas-pipe
Provided below is an example of the configuration of the kasp-pipe program and
Postfix mail system that work together as follows:
• Exim starts at port 25 with special configuration file
/usr/local/etc/exim/exim.listen;
• all mail messages received by Exim transferred to kas-pipe via LMTP
protocol;
• kas-pipe transfers the processed messages further. In order to do this,
/usr/local/sbin/exim -bs is started.
The /usr/local/ap-mailfilter/etc/kas-pipe.conf configuration file contains the
following information:
InProtocolLMTP Yes
OutgoingAddr exec:/usr/local/sbin/exim -bs