X-Git-Url: https://git.exim.org/exim.git/blobdiff_plain/475fe28a6a039803d280266e29e755a603d1dfe7..d87df92cd9117c3bee1db7741090a974f3463848:/doc/doc-txt/NewStuff diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 4a2739188..dc03699f3 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.34 2005/04/06 14:03:53 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.101 2006/04/20 14:11:29 ph10 Exp $ New Features in Exim -------------------- @@ -8,143 +8,74 @@ but have not yet made it into the main manual (which is most conveniently updated when there is a relatively large batch of changes). The doc/ChangeLog file contains a listing of all changes, including bug fixes. - -Version 4.51 +Version 4.62 ------------ -PH/01 The format in which GnuTLS parameters are written to the gnutls-param - file in the spool directory has been changed. This change has been made - to alleviate problems that some people had with the generation of the - parameters by Exim when /dev/random was exhausted. In this situation, - Exim would hang until /dev/random acquired some more entropy. - - The new code exports and imports the DH and RSA parameters in PEM - format. This means that the parameters can be generated externally using - the certtool command that is part of GnuTLS. - - To replace the parameters with new ones, instead of deleting the file - and letting Exim re-create it, you can generate new parameters using - certtool and, when this has been done, replace Exim's cache file by - renaming. The relevant commands are something like this: - - # rm -f new.params - # touch new.params - # chown exim:exim new.params - # chmod 0400 new.params - # certtool --generate-privkey --bits 512 >new.params - # echo "" >>new.params - # certtool --generate-dh-params --bits 1024 >> new.params - # mv new.params params - - If Exim never has to generate the parameters itself, the possibility of - stalling is removed. - -PH/02 A new expansion item for dynamically loading and calling a locally- - written C function is now provided, if Exim is compiled with - - EXPAND_DLFUNC=yes +1. The ${readsocket expansion item now supports Internet domain sockets as well + as Unix domain sockets. If the first argument begins "inet:", it must be of + the form "inet:host:port". The port is mandatory; it may be a number or the + name of a TCP port in /etc/services. The host may be a name, or it may be an + IP address. An ip address may optionally be enclosed in square brackets. + This is best for IPv6 addresses. For example: - set in Local/Makefile. The facility is not included by default (a - suitable error is given if you try to use it when it is not there.) + ${readsocket{inet:[::1]:1234}{}... - If you enable EXPAND_DLFUNC, you should also be aware of the new redirect - router option forbid_filter_dlfunc. If you have unprivileged users on - your system who are permitted to create filter files, you might want to - set forbid_filter_dlfunc=true in the appropriate router, to stop them - using ${dlfunc to run code within Exim. + Only a single host name may be given, but if looking it up yield more than + one IP address, they are each tried in turn until a connection is made. Once + a connection has been made, the behaviour is as for ${readsocket with a Unix + domain socket. - You load and call an external function like this: +2. If a redirect router sets up file or pipe deliveries for more than one + incoming address, and the relevant transport has batch_max set greater than + one, a batch delivery now occurs. - ${dlfunc{/some/file}{function}{arg1}{arg2}...} - Once loaded, Exim remembers the dynamically loaded object so that it - doesn't reload the same object file in the same Exim process (but of - course Exim does start new processes frequently). - - There may be from zero to eight arguments to the function. When compiling - a local function that is to be called in this way, local_scan.h should be - included. The Exim variables and functions that are defined by that API - are also available for dynamically loaded functions. The function itself - must have the following type: - - int dlfunction(uschar **yield, int argc, uschar *argv[]) - - Where "uschar" is a typedef for "unsigned char" in local_scan.h. The - function should return one of the following values: - - OK Success. The string that is placed in "yield" is put into - the expanded string that is being built. +Version 4.61 +------------ - FAIL A non-forced expansion failure occurs, with the error - message taken from "yield", if it is set. +The documentation is up-to-date for the 4.61 release. Major new features since +the 4.60 release are: - FAIL_FORCED A forced expansion failure occurs, with the error message - taken from "yield" if it is set. +. An option called disable_ipv6, to disable the use of IPv6 completely. - ERROR Same as FAIL, except that a panic log entry is written. +. An increase in the number of ACL variables to 20 of each type. - When compiling a function that is to be used in this way with gcc, - you need to add -shared to the gcc command. Also, in the Exim build-time - configuration, you must add -export-dynamic to EXTRALIBS. +. A change to use $auth1, $auth2, and $auth3 in authenticators instead of $1, + $2, $3, (though those are still set) because the numeric variables get used + for other things in complicated expansions. -TF/01 $received_time is a new expansion variable containing the time and date - as a number of seconds since the start of the Unix epoch when the - current message was received. +. The default for rfc1413_query_timeout has been changed from 30s to 5s. -PH/03 There is a new value for RADIUS_LIB_TYPE that can be set in - Local/Makefile. It is RADIUSCLIENTNEW, and it requests that the new API, - in use from radiusclient 0.4.0 onwards, be used. It does not appear to be - possible to detect the different versions automatically. +. It is possible to use setclassresources() on some BSD OS to control the + resources used in pipe deliveries. -PH/04 There is a new option called acl_not_smtp_mime that allows you to scan - MIME parts in non-SMTP messages. It operates in exactly the same way as - acl_smtp_mime +. A new ACL modifier called add_header, which can be used with any verb. -PH/05 It is now possible to redefine a macro within the configuration file. - The macro must have been previously defined within the configuration (or - an included file). A definition on the command line using the -D option - causes all definitions and redefinitions within the file to be ignored. - In other words, -D overrides any values that are set in the file. - Redefinition is specified by using '==' instead of '='. For example: +. More errors are detectable in retry rules. - MAC1 = initial value - ... - MAC1 == updated value +There are a number of other additions too. - Redefinition does not alter the order in which the macros are applied to - the subsequent lines of the configuration file. It is still the same - order in which the macros were originally defined. All that changes is - the macro's value. Redefinition makes it possible to accumulate values. - For example: - MAC1 = initial value - ... - MAC1 == MAC1 and something added +Version 4.60 +------------ - This can be helpful in situations where the configuration file is built - from a number of other files. +The documentation is up-to-date for the 4.60 release. Major new features since +the 4.50 release are: -PH/06 Macros may now be defined or redefined between router, transport, - authenticator, or ACL definitions, as well as in the main part of the - configuration. They may not, however, be changed within an individual - driver or ACL, or in the local_scan, retry, or rewrite sections of the - configuration. +. Support for SQLite. -PH/07 $acl_verify_message is now set immediately after the failure of a - verification in an ACL, and so is available in subsequent modifiers. In - particular, the message can be preserved by coding like this: +. Support for IGNOREQUOTA in LMTP. - warn !verify = sender - set acl_m0 = $acl_verify_message +. Extensions to the "submission mode" features. - Previously, $acl_verify_message was set only while expanding "message" - and "log_message" when a very denied access. +. Support for Client SMTP Authorization (CSA). +. Support for ratelimiting hosts and users. +. New expansion items to help with the BATV "prvs" scheme. -Version 4.50 ------------- +. A "match_ip" condition, that matches an IP address against a list. -The documentation is up-to-date for the 4.50 release. +There are many more minor changes. ****