-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.106 2006/07/17 09:18:09 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/NewStuff,v 1.111 2006/09/25 10:14:20 ph10 Exp $
New Features in Exim
--------------------
-This file contains descriptions of new features that have been added to Exim,
-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.
+This file contains descriptions of new features that have been added to Exim.
+Before a formal release, there may be quite a lot of detail so that people can
+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.64
+------------
+
+1. ACL variables can now be given arbitrary names, as long as they start with
+ "acl_c" or "acl_m" (for connection variables and message variables), are
+ at least six characters long, with the sixth character being either a digit
+ or an underscore. The rest of the name can contain alphanumeric characters
+ and underscores. This is a compatible change because the old set of
+ variables such as acl_m12 are a subset of the allowed names. There may now
+ be any number of ACL variables. For example:
+
+ set acl_c13 = value for original ACL variable
+ set acl_c13b = whatever
+ set acl_m_foo = something
+
+ What happens if a syntactically valid but undefined ACL variable is
+ referenced depends on the setting of the strict_acl_vars option. If it is
+ false (the default), an empty string is substituted; if it is true, an error
+ is generated. This affects all ACL variables, including the "old" ones such
+ as acl_c4. (Previously there wasn't the concept of an undefined ACL
+ variable.)
+
+ The implementation has been done in such a way that spool files containing
+ ACL variable settings written by previous releases of Exim are compatible
+ and can be read by the new release. If only the original numeric names are
+ used, spool files written by the new release can be read by earlier
+ releases.
+
+2. There is a new ACL modifier called log_reject_target. It makes it possible
+ to specify which logs are used for messages about ACL rejections. Its
+ argument is a list of words which can be "main", "reject", or "panic". The
+ default is "main:reject". The list may be empty, in which case a rejection
+ is not logged at all. For example, this ACL fragment writes no logging
+ information when access is denied:
+
+ deny <some conditions>
+ log_reject_target =
+
+ The modifier can be used in SMTP and non-SMTP ACLs. It applies to both
+ permanent and temporary rejections.
+
Version 4.63
------------
1. There is a new Boolean option called filter_prepend_home for the redirect
- router. It defaults true, for backward compatibility. If a "save" command in
- an Exim filter has a relative path for its argument, and $home is defined,
- it is automatically prepended to the relative path. This action can now be
- prevented by setting filter_prepend_home false.
+ router.
2. There is a new acl, set by acl_not_smtp_start, which is run right at the
start of receiving a non-SMTP message, before any of the message has been
- read. (This is the analogue of the acl_smtp_predata ACL for SMTP input.) The
- result of this ACL is ignored; it cannot be used to reject a message. If
- you really need to, you could set a value in an ACL variable here and reject
- based on that in the acl_not_smtp ACL. However, this ACL can be used to set
- controls, and in particular, it can be used to set control=suppress_local_
- fixups, which cannot be used in the acl_not_smtp ACL because by the time
- that ACL is run, it is too late. When the acl_not_smtp_start ACL is run, the
- sender and recipients are known, so the "senders" and "sender_domains"
- conditions and $sender_address and $recipients variables can be used.
- Variables such as $authenticated_ sender are also available. It is possible
- to specify added header lines in this ACL.
+ read.
3. When an SMTP error message is specified in a "message" modifier in an ACL,
or in a :fail: or :defer: message in a redirect router, Exim now checks the
- start of the message for an SMTP error code. This consists of three digits
- followed by a space, optionally followed by an extended code of the form
- n.n.n, also followed by a space. If this is the case and the very first
- digit is the same as the default error code, the code from the message is
- used instead. If the very first digit is incorrect, a panic error is logged,
- and the default code is used. This is an incompatible change, but it is not
- expected to affect many (if any) configurations. It is possible to suppress
- the use of the supplied code in a redirect router by setting the
- smtp_error_code option false. In this case, any SMTP code is quietly
- ignored.
+ start of the message for an SMTP error code.
4. There is a new parameter for LDAP lookups called "referrals", which takes
- one of the settings "follow" (the default) or "nofollow". The latter stops
- the LDAP library from trying to follow referrals issued by the LDAP server.
+ one of the settings "follow" (the default) or "nofollow".
+
+5. Version 20070721.2 of exipick now included, offering these new options:
+ --reverse
+ After all other sorting options have bee processed, reverse order
+ before displaying messages (-R is synonym).
+ --random
+ Randomize order of matching messages before displaying.
+ --size
+ Instead of displaying the matching messages, display the sum
+ of their sizes.
+ --sort <variable>[,<variable>...]
+ Before displaying matching messages, sort the messages according to
+ each messages value for each variable.
+ --not
+ Negate the value for every test (returns inverse output from the
+ same criteria without --not).
Version 4.62
git://git.exim.org / users / jgh / exim.git / blobdiff