>> > Another question. Am I right in thinking that the Amavis test can't >> >>> add any headers to the email ? IIRC I read somewhere that this is a >>> limitation of the Postfix policy protocol. >>> >> Postfix policy protocol can prepend a header, some people have >> suggested you can add more by using \r\n to separate, although i've >> not personally tested this. >> > > > > >> As for the amavis policy bank, i don't personally use it in policyd >> so Nigel is in a better position to answer, but i believe it doesn't >> make any changes. >> > > That's a shame. I'm looking at Policyd for several reasons, one is to > support "up front" scanning so I can reject spam. I refuse to bounce > anything unless I REALLY have to because of the problem that causes > with backscatter. For this reason, and also to avoid the complication > of "per domain" or "per user" settings, I have the settings very > relaxed on my current "store, check, forward" setup and add spam tags > so users can add their own filters and set their own drop threshhold. > I don't really want to lose the tagging/header from scanned mails. > > Policyd does not run Amavisd-new in any way.
1. Postfix calls policyd to check RCPT and whatever else, Policyd saves what policy it matched. 2. Postfix sends the mail to Amavisd-new using content-filter 3. Amavisd policyd plugin pushes itself in, looks at the send/recipient, finds the policy it matched, overrides the amavisd-new policy bank with your settings and amavisd-new continues. As easy as that. Regards Nigel
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
