Expand recipients_max, smtp-batch input

[exim.git] / doc / doc-txt / ChangeLog

diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 48cc629109c18a04d9ce1fbe117165490622373a..2dab6775a986ef9683f45f27bd7d1a3911f60239 100644 (file)
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -67,7 +67,7 @@ JH/13 Add an fdatasync call for the received message data file in spool, before
       loggging reception and sending the SMTP ack.  Previously we only flushed
       the stdio buffer so there was still the possibility of a disk error.
 
       loggging reception and sending the SMTP ack.  Previously we only flushed
       the stdio buffer so there was still the possibility of a disk error.
 

-JH/14 Bug 3061: Avoid a split log line when trtying to rewrite a malformed
+JH/14 Bug 3061: Avoid a split log line when trying to rewrite a malformed

       address.  Previously, for the last address in a header line (commonly
       there is only one) the terminating newline was part of the logged
       information.
       address.  Previously, for the last address in a header line (commonly
       there is only one) the terminating newline was part of the logged
       information.


@@ -102,6 +102,22 @@ JH/20 Bug 3047: A recent (somewhere between 10.34 and 10.42) version of the
       The same issue arises with the ACL regex condition, which is applied
       to every line of a received message.
 
       The same issue arises with the ACL regex condition, which is applied
       to every line of a received message.
 

+JH/21 Bug 3059: Fix crash in smtp transport. When running for a message for
+      which all recipients had been handled (itself an issue) a null-pointer
+      deref was done on trying to write a retry record. Fix that by counting
+      the outstanding recipients before trying to transmit the message.
+      The situation arose for a second MX try within a transport run, when the
+      first had perm-rejected a recipient (the only one for the connection, in
+      the case seen) during pipelining, and then closed the TCP connection.
+      The transport classified that as an I/O error, leaving the message
+      outstanding but having marked up the recipient as dealt-with. It then
+      tried another MX because of the I/O error. Fix this by converting the
+      message-level status to ok if there was a close but all recipients were
+      dealt with.  Thanks to Wolfgand Breyha for debug runs.
+
+JH/22 The ESMTP_LIMITS facility (RFC 9422) is promoted from experimental status
+      and is now controlled by the build-time option DISABLE_ESMTP_LIMITS..
+

 
 Exim version 4.97
 -----------------
 
 Exim version 4.97
 -----------------