Am 19.07.2016 um 21:50 schrieb Ryan Coleman:
On Jul 19, 2016, at 2:20 AM, Matus UHLAR - fantomas <uh...@fantomas.sk> wrote: On 18.07.16 23:44, Ryan Coleman wrote:How do I get Spamassassin configured with Postfix to have the email checked there FIRST before running it through Postgrey?you can not - postgrey as a policy service is always run before spamassassin, no matter how it's used.Or how do I get it to dump back into the queue after the hold time and scan through SpamAssassin? I’m watching all my log files and emails that are clearing PostGrey are definitely not going to SpamAssassin next; and they never get there in the first place because of Postgrey.strange... how do you run spamassassin from postfix?In master.cf like everyone else…
"everyone else"?no - not everyone else pipes mail in master.cf to spamassassin - the majority is using "spamd" as exmaple with "smtpd_milters = unix:/run/spamass-milter/spamass-milter.sock" to save wasted ressources for repeated initialization
smtp inet n - - - - smtpd -o content_filter=spamassassin
comes *after* "check_policy_service" by definition master.cf:spf-policy unix - n n - 0 spawn user=nobody argv=/usr/bin/python /usr/libexec/postfix/policyd-spf /etc/python-policyd-spf/policyd-spf.conf
and in "mian.cf" you are supposed to have "check_policy_service unix:private/spf-policy" within "smtpd_recipient_restrictions"
so postgrey and contentfilters are completly independent, there is no hold at all, any greylisted client becomes a 4xx response long before SA is part of the game, comes back later and if it comes back *late enough* it makes it to contentfilters
signature.asc
Description: OpenPGP digital signature
