Hi Wietse, On Tue, Mar 22, 2016 at 10:28:48 -0400, Wietse Venema wrote: > In order to protect the stability of the Postfix SMTP client, I > propose a new feature that builds on smtp_tls_policy_maps that > allows experimentation with STS and other features.
Great! I am looking forward to it. > Q1: What point in time is the call made? Maybe after the TLS-protected HELO? > Q2: What attributes to send? E.g., nexthop, recipient, SMTP_SESSION, > SMTP_ITERATOR, what else? Probably also information about the TLS connection, so that a policy daemon can do the verification that it needs. Possibly the CA CN and certificate CN plus the information if it's considered trusted or not? I guess you could also send the certificate over the wire? > 3) The reply is exactly the same as with smtp_tls_policy_maps. The > rationale for this is to simplify implementation, user interface, and > documentation (less code to write and fewer new things to learn). I would have thought something more in line with access restrictions. I mean: I probably want to tell Postfix if it needs to keep the mail in the queue (with a defer reason), or possibly bounce it, in case I am not happy with what the next hop gives me. How to do that with a reply like in smtp_tls_policy_maps? Cheers David
