------- 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 #8 from Andreas Metzler <[email protected]> 2014-04-20 07:46:12 --- On 2014-04-15 Jeremy Harris <[email protected]> wrote: > ------- 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 #7 from Jeremy Harris <[email protected]> 2014-04-15 > 16:53:57 --- > Created an attachment (id=711) --> (http://bugs.exim.org/attachment.cgi?id=711) > --> (http://bugs.exim.org/attachment.cgi?id=711) > proposed fix > In the transport startup, repoint the legacy variables over to the new > outbound > ones Hello, I have just tested the proposed patch in my trivial setup (mail sent on to smarthost) by making the belowmentioned modifications to my configuration and comparing headers with and without patch. ------------------------------------------- add this to acl check mail: warn message = X-TLS-info-rcpt: [tls_out_cipher $tls_out_cipher ] \ [tls_in_cipher $tls_in_cipher ] \ [tls_cipher $tls_cipher ] add this to smarthost transport: headers_add = X-TLS-info-out: [tls_out_cipher $tls_out_cipher ] \ [tls_in_cipher $tls_in_cipher ] \ [tls_cipher $tls_cipher ] ------------------------------------------- On message reception (mail acl) the expected (=nothing) happens, tls_out_cipher stays empty, tls_cipher and tls_in_cipher have the same info. 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_out_cipher is suddenly *nonempty*, it has gone persistant, recording the tls-information as of message receipt. cu Andreas -- Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
