X-Git-Url: https://git.exim.org/users/jgh/exim.git/blobdiff_plain/7e66e54dcf419ff995a49250902ae71a73228373..9675b3847f805018897fc71dcc5c98b78defd510:/doc/doc-txt/NewStuff diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 604e59a9a..6dfb76ea8 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.78 2005/12/06 10:25:59 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.82 2006/02/10 14:25:43 ph10 Exp $ New Features in Exim -------------------- @@ -13,13 +13,33 @@ Version 4.61 PH/01 There is a new global option called disable_ipv6, which does exactly what its name implies. If set true, even if the Exim binary has IPv6 support, - no IPv6 activities take place. AAAA records are never looked up as a for - host names given in manual routing data or elsewhere. AAAA records that - are received from the DNS as additional data for MX records are ignored. - Any IPv6 addresses that are listed in local_interfaces, manualroute route + no IPv6 activities take place. AAAA records are never looked up for host + names given in manual routing data or elsewhere. AAAA records that are + received from the DNS as additional data for MX records are ignored. Any + IPv6 addresses that are listed in local_interfaces, manualroute route data, etc. are also ignored. If IP literals are enabled, the ipliteral router declines to handle IPv6 literal addresses. +PH/02 There are now 20 of each type of ACL variable by default (instead of 10). + It is also possible to change the numbers by setting ACL_CVARS and/or + ACL_MVARS in Local/Makefile. Backward compatibility is maintained if you + upgrade to this release with existing messages containing ACL variable + settings on the queue. However, going in the other direction + (downgrading) will not be compatible; the values of ACL variables will be + lost. + +PH/03 If quota_warn_message contains a From: header, Exim now refrains from + adding the default one. Similarly, if it contains a Reply-To: header, the + errors_reply_to option, if set, is not used. + +PH/04 The variables $auth1, $auth2, $auth3 are now available in authenticators, + containing the same values as $1, $2, $3. The new variables are provided + because the numerical variables can be reset during string expansions + (for example, during a "match" operation) and so may lose the + authentication data. The preferred variables are now the new ones, with + the use of the numerical ones being deprecated, though the support will + not be removed, at least, not for a long time. + Version 4.60 ------------