X-Git-Url: https://git.exim.org/exim.git/blobdiff_plain/b4e7527561f1c68b821d5cf25efe29ae63d1d434..a1caa6da6f72e8c5b8b24678e32c4953a26a2b48:/doc/doc-txt/ChangeLog diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog index e258966d8..a6da95001 100644 --- 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. -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. @@ -80,8 +80,8 @@ JH/16 Two-phase queue runs are now reported in the daemon startup log line and in exiwhat output. JH/17 Bug 3064: Fix combination of "-q -R ". Introduction of - the multiple-queue-runners facility for 4.97 broking this, giving only - a one-time run of the queue. + the multiple-queue-runners facility for 4.97 broke this, giving only a + one-time run of the queue. JH/18 Bug 3068: Log a warning for use of deprecated syntax in query-style lookups. @@ -89,7 +89,7 @@ JH/18 Bug 3068: Log a warning for use of deprecated syntax in query-style JH/19 Fix TLS startup. When the last expansion done before the initiation of a TLS session resulted in a forced-fail, a misleading error was logged for the expansino of tls_certificates. This would affect the common case of - that option being set (main-section options) but not having any vriable + that option being set (main-section options) but not having any variable parts. It could also potentially affect tls_privatekeys. The underlyding coding errors go back to 4.90 but were only exposed in 4.97. @@ -99,6 +99,34 @@ JH/20 Bug 3047: A recent (somewhere between 10.34 and 10.42) version of the when a user had over 104207 messages stored and the appendfile maildir_quota_directory_regex option is in use. Release the allocated memory every thosand files to avoid this. + 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. + +JH/23 Bug 3066: Avoid leaking lookup database credentials to log. + +JH/24 Bug 3081: Fix a delivery process crash. When the router "errors_to" + option specified a fixed address, later rewriting on that address would + trip on the configuration data being readonly. Instead of modifying + in-place, copy data. Found and fixed by Peter Benie. + +JH/25 Bug 3079: Fix crash in dbmnz. When a key was present for zero-length + data a null pointer was followed. Find and testcase by Sebastian Bugge. Exim version 4.97 @@ -675,7 +703,7 @@ JH/44 Bug 2701: Fix list-expansion of dns_ipv4_lookup. Previously, it did mx_fail_domains. JH/45 Use a (new) separate store pool-pair for DKIM verify working data. - Previously the permanent pool was used, so the sore could not be freed. + Previously the permanent pool was used, so the store could not be freed. This meant a connection with many messages would use continually-growing memory.