On Wed, Sep 13, 2023 at 09:33:36AM +0100, Jeremy Harris via Exim-users wrote:
> "non-properly terminated" means the far end didn't do a proper TLS close
> sequence. It's unfortunately common. However, combined with the 30s stall,
> worth checking on. Get a delivery run with debug; look for the "SMTP"
> lines - these are the SMTP commands and responses - and you'll be able
> to tell where it is in the protocol conversation.
So long as the delivery completed, the lost "close_notify" and TCP FIN
are harmless, though do delay local end process cleanup. Since Exim is
the client, it could skip waiting for the QUIT response, just send
QUIT<CRLF>, perform an SSL_shutdown(), and close the socket without
waiting for a response. Postfix has taken this approach successfully
for almost 20 years:
http://www.postfix.org/postconf.5.html#smtp_skip_quit_response
--
Viktor.
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## [email protected]
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
