-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.116 2006/10/16 13:43:21 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/NewStuff,v 1.120 2006/11/06 15:50:12 ph10 Exp $
New Features in Exim
--------------------
values matches (or if no record is found), this is the only lookup that is
done. Only if there is a match is one of the more specific lists consulted.
+6. All authenticators now have a server_condition option. Previously, only
+ plaintext had this, and this has not changed: it must be set to the
+ authenticator as a server. For the others, if server_condition is set, it is
+ expanded if authentication is successful, and treated exactly as it is in
+ plaintext. This can serve as a means of adding authorization to an
+ authenticator.
+
+7. There is a new command-line option called -Mset. It is useful only in
+ conjunction with -be (that is, when testing string expansions). It must be
+ followed by a message id; Exim loads the given message from its spool before
+ doing the expansions, thus setting message-specific variables such as
+ $message_size and the header variables. The $recipients variable is
+ available. This feature is provided to make it easier to test expansions
+ that make use of these variables. However, Exim must be called by an admin
+ user when -Mset is used.
+
+8. Another similar new command-line option is called -bem. It operates like -be
+ except that it must be followed by the name of a file. For example:
+
+ exim -bem /tmp/testmessage
+
+ The file is read as a message (as if receiving a locally-submitted non-SMTP
+ message) before any of the test expansions are done. Thus, message-specific
+ variables such as $message_size and $h_from: are available. However, no
+ Received: header is added to the message. If the -t option is set,
+ recipients are read from the headers in the normal way, and are shown in the
+ $recipients variable. Note that recipients cannot be given on the command
+ line, because further arguments are taken as strings to expand (just like
+ -be).
+
+9. When an address is delayed because of a 4xx response to a RCPT command, it
+ is now the combination of sender and recipient that is delayed in subsequent
+ queue runs until its retry time is reached. You can revert to the previous
+ behavious, that is, delay the recipient independent of the sender, by
+ setting address_retry_include_sender=false in the smtp transport. However,
+ this can lead to problems with servers that regularly issue 4xx responses to
+ RCPT commands.
+
+
Version 4.63
------------
git://git.exim.org / exim.git / blobdiff