[exim-dev] [Bug 1455] tls_out_cipher or tls_cipher is empty

Top Page
Delete this message
Reply to this message
Author: Andreas Metzler
Date:  
To: exim-dev
Old-Topics: [exim-dev] [Bug 1455] New: tls_out_cipher is empty
Subject: [exim-dev] [Bug 1455] tls_out_cipher or tls_cipher is empty
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=1455




--- Comment #10 from Andreas Metzler <eximusers@???> 2014-04-20 15:01:36 ---
On 2014-04-20 Jeremy Harris <jgh@???> wrote:
> 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.


Hello,

Thanks, I see.

Just to be triple clear: 4.82 does not do that, this is a new
enhancement cause by the patch.

cu Andreas


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email