OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: Policy Server Protocol - Request for (small) Enhancement(s)

From: Ronald F. Guilmette (rfgtristatelogic.com)
Date: Sun May 18 2008 - 13:15:44 CDT


In message <482DF370.9050003megan.vbhcs.org>, you wrote:

>Ronald F. Guilmette wrote:
>>>> Second question: Regardless of the set of "stages" in which the "recipient
>"
>>>> parameter is only supplied to the policy server when it is the singular
>>>> allowed recipient, why is it that Postfix can't/doesn't supply the entire
>>>> list of all of the (multiple) allowed recipients? Is there some special
>>>> problem that I'm not aware of that prevents Postfix from handing the polic
>y
>>>> server the whole and entire list of permitted recipients? (I'm just tryin
>g
>>>> to understand things a bit better here.)
>
>I believe the major issue is that multiple recipients are
>simply not meaningful in this context. Once the client gets
>to DATA, individual recipients can no longer be
>rejected/accepted; you have to either accept or reject the
>whole message.

Thank you.

I didn't understand (or didn't remember) that the protocol causes a
separate transaction with the external policy server for each separate
RCPT TO. Now that I know/remember that, it all makes perfect sense.

>For now, in those cases where you want to see the entire
>recipient list you need to build that list with a policy
>server called from smtpd_recipient_restrictions that keeps state.

Yes.

The good news is that I don't actually need to do that.

I just needed to be sure that I _can_ get each on of the recipient
addresses in turn. And apparently I can. So that's perfect.

The only actual issue that still concerns me is the one regarding the
pre- versus post-rewritten recipient addresses. It's useful to have
the pre-rewritten ones, but for what I'm doing it would be more useful
to have access to the post-rewritten ones.

I suppose that my policy sever could, in theory, convert pre-rewritten
recipient addresses into post-rewritten ones _if_ it could get access,
selectively, to _just_ the address rewriting functionality of the
local(8) delivery agent, but I don't know how to do that.

Regards,
rfg