Hi,
These are all the log lines for one of the affected messages:
2026-02-02 10:48:41.283 [822946] 1XXXXX-XXXXXXXXXX-3rpC Completed
QT=3.361s
2026-02-02 10:48:41.283 [822946] 1XXXXX-XXXXXXXXXX-3rpC
2026-02-02 10:48:41.280 [822948] 1XXXXX-XXXXXXXXXX-3rpC peer close after
all rcpt responses; converting i/o-error to no-error
2026-02-02 10:48:41.280 [822948] 1XXXXX-XXXXXXXXXX-3rpC SSL_write: (from
forwarder.mydomain [1.2.3.4]:30548) syscall: Connection reset by peer
2026-02-02 10:48:38.384 [822936] 1XXXXX-XXXXXXXXXX-3rpC <= user@mydomain
H=forwarder.mydomain [1.2.3.4]:30548 I=[4.3.2.1]:25 Ci=822936 P=esmtps
L. X=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no S=20367368 RT=0.303s
id=XXXXXX@mydomain T="Some subject" from <user@mydomain> for
recipient@otherdomain
I also have tried to further debug the problem. Here is a snippet from
the debug log:
SMTP|> MAIL FROM: ***
SMTP|> RCPT TO:***
SMTP>> DATA
cmd buf flush 474 bytes
tls_write(0x55649bdd92e0, 474)
SSL_write(0x55649bd05d80, 0x55649bdd92e0, 474)
outbytes=474 error=0
sync_responses expect mail
Calling SSL_read(0x55649bd05d80, 0x55649bdd82e0, 4096)
read response data: size=287
SMTP<< 250 2.1.0 Sender ok
sync_responses expect rcpt for ***
SMTP<< 250 2.1.5 Recipient ok
sync_responses expect data
SMTP<< 354 Enter mail, end with "." on a line by itself
SMTP>> (writing message)
[ ... SNIP ... ]
flushing headers buffer
writing data block fd=6 size=8189 timeout=300
tls_write(0x55649bd1ecc8, 8189)
SSL_write(0x55649bd05d80, 0x55649bd1ecc8, 8189)
outbytes=-1 error=1
LOG: MAIN
TLS error (SSL_write): error:100C0102:BIO routines::passed a null
parameter
writing error 104: Connection reset by peer
LOG: MAIN
peer close after all rcpt responses; converting i/o-error to no-error
ok=1 send_quit=0 send_rset=1 continue_more=0 yield=0 first_address is
NULL
Calling SSL_read(0x55649bd05d80, 0x55649bdd82e0, 4096)
read response data: size=33
SMTP<< 421 4.4.2 Connection read error
Calling SSL_read(0x55649bd05d80, 0x55649bdd82e0, 4096)
tls_close(): shutting down TLS (with response-wait)
tls_write((nil), 0)
SSL_shutdown: error:0A000126:SSL routines::unexpected eof while reading
SMTP(close)>>
Thank you + best regards,
Stefan
On 2026-02-08 11:45, Jeremy Harris via Exim-users wrote:
On 2026/02/08 10:23 AM, Stefan Langeder via Exim-users wrote:
Hi,
Presumably Exim thinks the message was dealt with. What does the log
say?
that brings me back to my initial question that I started this thread
with. The logs do not say much, they say
"peer close after all rcpt responses; converting i/o-error to
no-error"
and then
"completed".
Please give all log lines relevant to the message. Do not summarise;
incomplete
information makes it hard to draw accurate conclusions.
For example, there must have been an acceptance line ("<=") for the
message.
My initial question was if "converting i/o-error to no-error" may be
the reason that Exim does not retry - or in other words, makes it
think that the message was dealt with. If so, I am looking for a way
to tell Exim that the transmission is not successful in such cases and
that a retry is required.
On 04/02/2026 11:03, Jeremy Harris via Exim-users wrote: On 2026/02/04
9:14 AM, Stefan Langeder via Exim-users wrote: > No.
^^^^^
--
Cheers,
Jeremy
--
## 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 https://www.exim.org/
## Please use the Wiki with this list - https://code.exim.org/exim/wiki/wiki
