X-Git-Url: https://git.exim.org/users/jgh/exim.git/blobdiff_plain/30dba1e609d941013dc8421de5104dad387ac5b1..e97957bc478f60d32649b329659d4b72748745c1:/doc/doc-txt/NewStuff?ds=sidebyside diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 04fedd633..f3e34e773 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.91 2006/02/28 11:25:40 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.96 2006/03/09 15:10:16 ph10 Exp $ New Features in Exim -------------------- @@ -98,6 +98,92 @@ PH/14 Messages created by the autoreply transport now contain a References: and then the final 11 are copied, before adding the message ID of the incoming message. +PH/15 The smtp transport has a new option called authenticated_sender_force. + When set true, it allows the authenticated_sender option's value to be + used, even if Exim has not authenticated as a client. + +PH/16 The expansion ${time_eval:} converts an Exim time string such as + 2d4h1m into a number of seconds. + +PH/17 The ACL modifier control=allow_auth_unadvertised can be used to permit a + client host to use the SMTP AUTH command even when it has not been + advertised in response to EHLO. Furthermore, because there are apparently + some really broken clients that do this, Exim will even accept AUTH after + HELO when this control is set. It should only be used if you really need + it, and you should limit its use to those broken hosts that do not work + without it. For example: + + warn hosts = 192.168.34.25 + control = allow_auth_unadvertised + + This control is permitted only in the connection and HELO ACLs. + +PH/18 There is a new ACL modifier called "add_header" which does what its name + implies. It specifies one of more header lines that are to be added to an + incoming message, assuming, of course, that the message is ultimately + accepted. + + This modifier is permitted in the MAIL, RCPT, PREDATA, DATA, MIME, and + non-SMTP ACLs (in other words, those that are concerned with accepting a + message). Added header lines are accumulated during the MAIL, RCPT, and + PREDATA ACLs, with any duplicates being discarded. They are then added to + the message before processing the DATA and MIME ACLs, during which + further added header lines are accumulated, again with duplicates + discarded. Thus, it is possible to add two identical header lines to an + SMTP message, but only if one is added before DATA and one after. + + In the case of non-SMTP messages, new headers are accumulated during the + non-SMTP ACL, and added to the message at the end. + + The add_header modifier is available for use with all ACL verbs. In the + case of the WARN verb, add_header supersedes the use of "message" for + this purpose; for the other verbs, it provides a new facility. If both + add_header and "message" are present on a WARN verb, both are processed + according to their specifications. + + The add_header modifier acts immediately it is encountered during the + processing of an ACL. This is different to the (now-deprecated) use of + "message" on a WARN verb, where the action is taken only if all the + conditions are true. Notice the difference between these two cases on a + RCPT ACL: + + deny add_header = ADDED: some text + + + deny + add_header = ADDED: some text + + In the first case, the header is always added, whether or not the current + recipient is rejected. In the second case, the header is added only if + the recipient is rejected. + + If add_header appears more than once on an ACL statement, multiple + headers are added, provided that they have different content. (In the + case of WARN with "message", only the last value of "message" is used.) + + The facility for specifying where the new header is to be inserted, as + described for WARN with "message" in section 39.19 of the 4.60 manual, is + supported. + +PH/19 The following errors can now be detected in retry rules: + + mail_4xx This is like rcpt_4xx, but applies to MAIL commands + + data_4xx This is like rcpt_4xx, but applies to DATA commands and the + response code after the end of the data + + lost_connection This error occurs when the server unexpectedly closes + the SMTP connection. There may, of course, legitmate reasons + for this (host died, network died), but if it repeats a lot + for the same host, it indicates something odd. + + tls_required The server was required to use TLS (hosts_require_tls), + but either did not offer it, or responded with 4xx to + STARTTLS, or there was a problem setting up the TLS connection + + Note that a 5xx response to STARTTLS is a permanent error. + + Version 4.60 ------------