On 20/04/14 14:20, Andreas Metzler wrote:
> On the outgoing connection $tls_cipher expands to the same content as
> $tls_out_cipher which is expected and wanted. However there is also an
> unwanted change: tls_in_cipher is suddenly *nonempty*, it has gone
> ^^
> persistant, recording the tls-information as of message receipt:
> I am not doing callouts or something like this, so afaiui
> tls_in_cipher should be empty in X-TLS-info-out.
Ah, no. That's what it's for; recording what the TLS information
was during acceptance of the mail item in question (now being
sent onwards). There's no particular reason to make that
information *un*-available now that the conflict in use
of the legacy "tls_cipher" variable is resolved.
--
Cheers,
Jeremy
