Hello rob On Thu, Feb 23, 2012, at 03:39 PM, /dev/rob0 wrote: > > Based on that, my current understanding of my config is that > > email is received by postscreen, > > No, postscreen receives no mail. It receives a connection, > identifies it as legitimate, and passes that connection on to smtpd. I've > only > ever done after-queue content filtering with postscreen, so I am not > sure how they interact. Looks like it goes to smtpd, filter, smtpd, > very much as after-queue content filtering works.
Connection vs mail. That's a distcintion I hadn't understood from reading. Nice short, clear explanation. Thanks. > See "Principles of operation" in SMTPD_PROXY_README.html which says: > > * The before-filter Postfix SMTP server accepts connections from > the Internet and does the usual relay access control, SASL > authentication, TLS negotiation, RBL lookups, rejecting > non-existent sender or recipient addresses, etc. > > It's the very last item before "etc" that you are missing. You are > not getting to the filter. Yes. I think Noel's comments and post are also addressing that. > > Will such a header be added for ALL recipients? or just for the > > matched address? > > A header is part of the message, the DATA part of SMTP. There is one > DATA for all RCPT TO addresses. So, yes. snip Great. That seems like it's a real option, then. I'll explore further. Thanks. > > Naively, I'd assume 'this' is best done @postscreen time. Iiuc, > > though, that's not currently possible, and/or would require > > 'additional development'. > > Not going to happen; postscreen does what it does, and that is > probably all it will ever do. Forget postscreen, irrelevant to this. Per your explanation above, Gotcha. Cheers, Roger
