https://bugs.exim.org/show_bug.cgi?id=2034
Bjoern Jacke <bjoern@j3e.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
Version|4.87 |4.92
CC| |bjoern@j3e.de
--- Comment #3 from Bjoern Jacke <bjoern@j3e.de> ---
I've seen this kind of errors since a while and could analyze this further:
*.outlook.com servers and maybe some others shut down the connection right
after sending the SMTP QUIT without waiting for a reply. The relevant exim
debug output looks like this:
671 SMTP<< QUIT
671 SMTP>> 221 mail.example.com closing connection
671 tls_write(0x55b2c9c37b00, 38)
671 gnutls_record_send(SSL, 0x55b2c9c37b00, 38)
671 GnuTLS<2>: WRITE: -1 returned from 0x4, errno: 104
671 GnuTLS<3>: ASSERT: ../../lib/buffers.c[_gnutls_io_write_flush]:722
671 GnuTLS<3>: ASSERT: ../../lib/record.c[_gnutls_send_tlen_int]:574
671 outbytes=-110
671 tls_write: gnutls_record_send err
671 LOG: MAIN
671 TLS error on connection from
mail-oln040092073050.outbound.protection.outlook.com
(EUR04-HE1-obe.outbound.protection.outlook.com) [40.92.73.50]:22566
I=[<my-ip>]:25 (send): The TLS connection was non-properly terminated.
Exim doesn't notice the connectionn shutdown and still sends the SMTP closing
notice the to server which already gave up the connection though. Accordingly
the tls_write fails and results in the 104 gnutls error, which exim show in the
log as "The TLS connection was non-properly terminated".
--
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/ ##
Bjoern Jacke <bjoern@j3e.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
Version|4.87 |4.92
CC| |bjoern@j3e.de
--- Comment #3 from Bjoern Jacke <bjoern@j3e.de> ---
I've seen this kind of errors since a while and could analyze this further:
*.outlook.com servers and maybe some others shut down the connection right
after sending the SMTP QUIT without waiting for a reply. The relevant exim
debug output looks like this:
671 SMTP<< QUIT
671 SMTP>> 221 mail.example.com closing connection
671 tls_write(0x55b2c9c37b00, 38)
671 gnutls_record_send(SSL, 0x55b2c9c37b00, 38)
671 GnuTLS<2>: WRITE: -1 returned from 0x4, errno: 104
671 GnuTLS<3>: ASSERT: ../../lib/buffers.c[_gnutls_io_write_flush]:722
671 GnuTLS<3>: ASSERT: ../../lib/record.c[_gnutls_send_tlen_int]:574
671 outbytes=-110
671 tls_write: gnutls_record_send err
671 LOG: MAIN
671 TLS error on connection from
mail-oln040092073050.outbound.protection.outlook.com
(EUR04-HE1-obe.outbound.protection.outlook.com) [40.92.73.50]:22566
I=[<my-ip>]:25 (send): The TLS connection was non-properly terminated.
Exim doesn't notice the connectionn shutdown and still sends the SMTP closing
notice the to server which already gave up the connection though. Accordingly
the tls_write fails and results in the 104 gnutls error, which exim show in the
log as "The TLS connection was non-properly terminated".
--
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/ ##