----- Original Message -----
>>I have not experienced the huge hit to CPU, disk, or bandwidth. My
Postfix
>>configuration didn't change when Spamassassin was introduced. It still
runs
>>all of its own internal spam tests and header checks before handing off to
>>SA via the content-filter. The only messages that get handed off to SA by
>>Postfix are those messages it was going to deliver anyway.
>
>ok, I was pretty sure smtpd passed to content-filter after DATA command and
>queueing the msg. That's how it seems to work in the smtpd policy
READMEchecks?
Nope, that's why when you re-inject to postfix from the content-filter, you
send the message to a different port with all of the previous Postfix check
disabled, so that the original Postfix tests are not run again:
127.0.0.1:10026 inet n - y - - smtpd
-o content_filter=
-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 header_checks=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks=127.0.0.0/8
-o strict_rfc821_envelopes=yes
Bill
