> Likely some time this year, but it is not entirely trivial, because
> the spec requires a first successful delivery to "activate" the policy,
> and expedited policy cache refresh on delivery failure.  Therefore,
> there would need to be some sort of new feedback mechanism at delivery
> completion.
>
> Also the new "tlsrpt" draft solicits aggregated delivery failure stats,
> which might also require similar feedback.
>
> Cycles to work on this are not immediately available.  With so few
> early adopters, and even Gmail in "testing", you might just build
> manual policy that gets you secure transport to Gmail, Yahoo and
> the other "free" email providers.
>

As always, the answers I get in this list is always straight forward and
informative.
Thank you very much!

-- 
Jonathan


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to