X-Git-Url: https://git.exim.org/users/heiko/exim.git/blobdiff_plain/2fe767453007d1b015f52313d16dc61635085621..5fa5f96fcfb9aa3c73e4ce9289a30be1e616e576:/doc/doc-txt/NewStuff?ds=sidebyside diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 46fd6c4d8..09e4dd283 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -9,6 +9,13 @@ test from the snapshots or the CVS before the documentation is updated. Once the documentation is updated, this file is reduced to a short list. +Version 4.76 +------------ + + 1. The global option "dns_use_edns0" may be set to coerce EDNS0 usage on + or off in the resolver library. + + Version 4.75 ------------ @@ -22,6 +29,16 @@ Version 4.75 false. When true, if the external delivery command exits on a signal then Exim will freeze the message in the queue, instead of generating a bounce. + 3. Log filenames may now use %M as an escape, instead of %D (still available). + The %M pattern expands to yyyymm, providing month-level resolution. + + 4. The $message_linecount variable is now updated for the maildir_tag option, + in the same way as $message_size, to reflect the real number of lines, + including any header additions or removals from transport. + + 5. When contacting a pool of SpamAssassin servers configured in spamd_address, + Exim now selects entries randomly, to better scale in a cluster setup. + Version 4.74 ------------ @@ -55,7 +72,7 @@ Version 4.73 2. A new pipe transport option, "permit_coredumps", may help with problem diagnosis in some scenarios. Note that Exim is typically installed as a setuid binary, which on most OSes will inhibit coredumps by default, - so that safety mechanism would have to be overriden for this option to + so that safety mechanism would have to be overridden for this option to be able to take effect. 3. ClamAV 0.95 is now required for ClamAV support in Exim, unless @@ -141,7 +158,7 @@ Version 4.73 forward, we recommend using TRUSTED_CONFIG_LIST with shim configs that include the main config. As a transition mechanism, we are temporarily providing a work-around: the new build option WHITELIST_D_MACROS provides - a colon-separated list of macro names which may be overriden by the Exim + a colon-separated list of macro names which may be overridden by the Exim run-time user. The values of these macros are constrained to the regex ^[A-Za-z0-9_/.-]*$ (which explicitly does allow for empty values).