X-Git-Url: https://git.exim.org/exim.git/blobdiff_plain/431b736177e2cdfd0b4da4c8545d8b732286abe1..8f2401034e2ce4007b1f270cd389381753c814eb:/doc/doc-txt/NewStuff diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 960f93ce8..f6cbf54c3 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.127 2007/01/17 11:17:58 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.151 2007/06/20 14:13:39 ph10 Exp $ New Features in Exim -------------------- @@ -8,103 +8,145 @@ 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.68 +------------ + + 1. The body_linecount and body_zerocount C variables are now exported in the + local_scan API. + + 2. When a dnslists lookup succeeds, the key that was looked up is now placed + in $dnslist_matched. When the key is an IP address, it is not reversed in + this variable (though it is, of course, in the actual lookup). In simple + cases, for example: + + deny dnslists = spamhaus.example + + the key is also available in another variable (in this case, + $sender_host_address). In more complicated cases, however, this is not + true. For example, using a data lookup might generate a dnslists lookup + like this: + + deny dnslists = spamhaus.example/<|192.168.1.2|192.168.6.7|... + + If this condition succeeds, the value in $dnslist_matched might be + 192.168.6.7 (for example). + + 3. Authenticators now have a client_condition option. When Exim is running as + a client, it skips an authenticator whose client_condition expansion yields + "0", "no", or "false". This can be used, for example, to skip plain text + authenticators when the connection is not encrypted by a setting such as: + + client_condition = ${if !eq{$tls_cipher}{}} + + Note that the 4.67 documentation states that $tls_cipher contains the + cipher used for incoming messages. In fact, during SMTP delivery, it + contains the cipher used for the delivery. The same is true for + $tls_peerdn. + + 4. There is now a -Mvc option, which outputs a copy of the + message to the standard output, in RFC 2822 format. The option can be used + only by an admin user. + + 5. There is now a /noupdate option for the ratelimit ACL condition. It + computes the rate and checks the limit as normal, but it does not update + the saved data. This means that, in relevant ACLs, it is possible to lookup + the existence of a specified (or auto-generated) ratelimit key without + incrementing the ratelimit counter for that key. + + In order for this to be useful, another ACL entry must set the rate + for the same key somewhere (otherwise it will always be zero). + + Example: + + acl_check_connect: + # Read the rate; if it doesn't exist or is below the maximum + # we update it below + deny ratelimit = 100 / 5m / strict / noupdate + log_message = RATE: $sender_rate / $sender_rate_period \ + (max $sender_rate_limit) + + [... some other logic and tests...] + + warn ratelimit = 100 / 5m / strict / per_cmd + log_message = RATE UPDATE: $sender_rate / $sender_rate_period \ + (max $sender_rate_limit) + condition = ${if le{$sender_rate}{$sender_rate_limit}} + + accept + + Version 4.67 ------------ 1. There is a new log selector called smtp_no_mail, which is not included in the default setting. When it is set, a line is written to the main log whenever an accepted SMTP connection terminates without having issued a - MAIL command. This includes both the case when the connection is dropped, - and the case when QUIT is used. Note that it does not include cases where - the connection is rejected right at the start (by an ACL, or because there - are too many connections, or whatever). These cases already have their own - log lines. - - The log line that is written contains the identity of the client in the - usual way, followed by D= and a time, which records the duration of the - connection. If the connection was authenticated, this fact is logged - exactly as it is for an incoming message, with an A= item. If the - connection was encrypted, CV=, DN=, and X= items may appear as they do for - an incoming message, controlled by the same logging options. - - Finally, if any SMTP commands were issued during the connection, a C= item - is added to the line, listing the commands that were used. For example, - - C=EHLO,QUIT - - shows that the client issued QUIT straight after EHLO. If there were fewer - than 20 commands, they are all listed. If there were more than 20 commands, - the last 20 are listed, preceded by "...". However, with the default - setting of 10 for smtp_accep_max_nonmail, the connection will in any case - be aborted before 20 non-mail commands are processed. + MAIL command. 2. When an item in a dnslists list is followed by = and & and a list of IP - addresses, in order to restrict the match to specific results from the DNS - lookup, the behaviour was not clear when the lookup returned more than one - IP address. For example, consider the condition - - dnslists = a.b.c=127.0.0.1 - - What happens if the DNS lookup for the incoming IP address yields both - 127.0.0.1 and 127.0.0.2 by means of two separate DNS records? Is the - condition true because at least one given value was found, or is it false - because at least one of the found values was not listed? And how does this - affect negated conditions? - - The behaviour of = and & has not been changed; however, the text below - documents it more clearly. In addition, two new additional conditions (== - and =&) have been added, to permit the "other" behaviour to be configured. - - A DNS lookup may yield more than one record. Thus, the result of the lookup - for a dnslists check may yield more than one IP address. The question then - arises as to whether all the looked up addresses must be listed, or whether - just one is good enough. Both possibilities are provided for: + addresses, the behaviour was not clear when the lookup returned more than + one IP address. This has been solved by the addition of == and =& for "all" + rather than the default "any" matching. - . If = or & is used, the condition is true if any one of the looked up - IP addresses matches one of the listed addresses. Consider: + 3. Up till now, the only control over which cipher suites GnuTLS uses has been + for the cipher algorithms. New options have been added to allow some of the + other parameters to be varied. - dnslists = a.b.c=127.0.0.1 + 4. There is a new compile-time option called ENABLE_DISABLE_FSYNC. When it is + set, Exim compiles a runtime option called disable_fsync. - If the DNS lookup yields both 127.0.0.1 and 127.0.0.2, the condition is - true because 127.0.0.1 matches. + 5. There is a new variable called $smtp_count_at_connection_start. - . If == or =& is used, the condition is true only if every one of the - looked up IP addresses matches one of the listed addresses. Consider: + 6. There's a new control called no_pipelining. - dnslists = a.b.c==127.0.0.1 + 7. There are two new variables called $sending_ip_address and $sending_port. + These are set whenever an SMTP connection to another host has been set up. - If the DNS lookup yields both 127.0.0.1 and 127.0.0.2, the condition is - false because 127.0.0.2 is not listed. You would need to have + 8. The expansion of the helo_data option in the smtp transport now happens + after the connection to the server has been made. - dnslists = a.b.c==127.0.0.1,127.0.0.2 + 9. There is a new expansion operator ${rfc2047d: that decodes strings that + are encoded as per RFC 2047. - for the condition to be true. +10. There is a new log selector called "pid", which causes the current process + id to be added to every log line, in square brackets, immediately after the + time and date. - When ! is used to negate IP address matching, it inverts the result, giving - the precise opposite of the behaviour above. Thus: +11. Exim has been modified so that it flushes SMTP output before implementing + a delay in an ACL. It also flushes the output before performing a callout, + as this can take a substantial time. These behaviours can be disabled by + obeying control = no_delay_flush or control = no_callout_flush, + respectively, at some earlier stage of the connection. - . If != or !& is used, the condition is true if none of the looked up IP - addresses matches one of the listed addresses. Consider: +12. There are two new expansion conditions that iterate over a list. They are + called forany and forall. - dnslists = a.b.c!&0.0.0.1 +13. There's a new global option called dsn_from that can be used to vary the + contents of From: lines in bounces and other automatically generated + messages ("delivery status notifications" - hence the name of the option). - If the DNS lookup yields both 127.0.0.1 and 127.0.0.2, the condition is - false because 127.0.0.1 matches. +14. The smtp transport has a new option called hosts_avoid_pipelining. - . If !== or !=& is used, the condition is true there is at least one looked - up IP address that does not match. Consider: +15. By default, exigrep does case-insensitive matches. There is now a -I option + that makes it case-sensitive. - dnslists = a.b.c!=&0.0.0.1 +16. A number of new features ("addresses", "map", "filter", and "reduce") have + been added to string expansions to make it easier to process lists of + items, typically addresses. - If the DNS lookup yields both 127.0.0.1 and 127.0.0.2, the condition is - true, because 127.0.0.2 does not match. You would need to have +17. There's a new ACL modifier called "continue". It does nothing of itself, + and processing of the ACL always continues with the next condition or + modifier. It is provided so that the side effects of expanding its argument + can be used. - dnslists = a.b.c!=&0.0.0.1,0.0.0.2 +18. It is now possible to use newline and other control characters (those with + values less than 32, plus DEL) as separators in lists. - for the condition to be false. +19. The exigrep utility now has a -v option, which inverts the matching + condition. - When the DNS lookup yields only a single IP address, there is no difference - between = and == and between & and =&. +20. The host_find_failed option in the manualroute router can now be set to + "ignore". Version 4.66