Re: Postfix policy servers

Hi Andreas

Andreas Metzler <[email protected]> wrote:
> Hello,
> I've played a little bit with postgrey. You can *almost* use it in
> exim's acls with a
> condition = $magic_stringcomparison{$readsocket{...}}
>
> There is just a single problem, the postfix policy servers will not
> close the connection after replying to a request, but exim's
> $readsocket expects the server to close the connection. Therefore
> you'll get connection-timed-out-errors from exim.

Could be strung together with an intermediate daemon, then? I wouldn't
discount that type of solution.

> So you either have to modify the policy servers or ask Phil to enhance
> $readsocket to add an option forcing it to close the connection. I do
> not think this should go into exiscan, but into exim proper.

Interesting - I'm not sure I agree, though. Exiscan has developed into a way
of hiding the complexity of communicating with various third-party policy
engines, providing a consistent high-level interface to the Exim config file
with no complex socket handling needed from Exim. I'd say this fits very
well with that paradigm.

Maybe advanced users might want to call a Postfix policy server directly
from their Exim config code, and it would be useful for the core product to
support that. But for the general-purpose drop-in user, Exiscan does the job
better IMHO. Look at how easy it is to drop in AV scanning with ClamAV or
Sophie.. nothing to tweak except high-level config items such as
host/port/socket etc.

Peter