------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=512 ------- Comment #6 from [EMAIL PROTECTED] 2007-06-15 19:49 ------- (In reply to comment #5) > (In reply to comment #4) > > > I've just traced through and seen that indeed, $tls_cipher is set. The > > documentation needs updating if this is to be kept. > > OK, I now understand the problem you are trying to solve. I think the answer > to > tls_cipher is to document it. I'll work on the patch, probably next week. I'm probably just missing it (again), but where is $tls_cipher _unset_ before being set if TLS is available? It's copied from the spool, delivery is started; now, if the delivery avoids TLS because it wasn't advertised (Man-in-the-Middle removing the expected STARTTLS) then how can I test in the client whether the value of $tls_cipher is that previously established or a new value? Thanks, -- Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email -- ## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
