https://bugs.exim.org/show_bug.cgi?id=2034
Jeremy Harris <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|2017-02-10 07:53:58 [16952] |TLS error on connection |TLS error on connection |from ... |from (143.202.36.84) |(gnutls_handshake): The TLS |[143.202.36.72]:34536 |connection was non-properly |I=[189.184.64.125]:25 |terminated. |(gnutls_handshake): The TLS | |connection was non-properly | |terminated. | --- Comment #4 from Jeremy Harris <[email protected]> --- We could maybe deal with that behaviour more neatly, though the message as is currently is accurate - the Outlook end really did not bother to close down the TLS connection, it just dumped the TCP connection. We would have to investigate the layers of error and decide, given the context of having received a QUIT command, to not report anything. I'm unsure whether or not it is worth it. It's not clear that the original issue is the same though; that was during the initial handshake call. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
