X-Git-Url: https://git.exim.org/users/jgh/exim.git/blobdiff_plain/1130bfb0c80bb04fa0873a075758a8abb84f607a..433a298016c18052dae7554c6770013578e40be8:/doc/doc-txt/NewStuff diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 85be6dc06..bbf27010d 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.68 2005/09/12 13:39:31 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.76 2005/10/03 13:25:32 ph10 Exp $ New Features in Exim -------------------- @@ -8,6 +8,16 @@ 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. +Exim version 4.54 +----------------- + +There was a problem with 4.52/TF/02 in that a "name=" option on control= +submission terminated at the next slash, thereby not allowing for slashes in +the name. This has been changed so that "name=" takes the rest of the string as +its data. It must therefore be the last option. + + + Exim version 4.53 ----------------- @@ -104,7 +114,7 @@ PH/06 It is now possible to specify a port number along with a host name or PH/07 $smtp_command_argument is now set for all SMTP commands, not just the non-message ones. This makes it possible to inspect the complete command - for RCPT commands, for example. + for RCPT commands, for example. But see also PH/45 below. PH/08 The ${eval expansion now supports % as a "remainder" operator. @@ -146,6 +156,28 @@ PH/11 There is a new log selector, "unknown_in_list", which provokes a log entry when the result of a list match is failure because a DNS lookup failed. +PH/12 There is a new variable called $smtp_command which contains the full SMTP + command (compare $smtp_command_argument - see PH/07 above). This makes it + possible to distinguish between HELO and EHLO, and also between things + like "MAIL FROM:<>" and "MAIL FROM: <>". + +TF/01 There's a new script in util/ratelimit.pl which extracts sending + rates from log files, to assist with choosing appropriate settings + when deploying the ratelimit ACL condition. + +PH/13 A new letter, "H", is available in retry parameter sets. It is similar + to "G" (geometric increasing time intervals), except that the interval + before the next retry is randomized. Each time, the previous interval is + multiplied by the factor in order to get a maximum for the next interval. + The mininum interval is the first argument of the parameter, and an + actual interval is chosen randomly between them. Such a rule has been + found to be helpful in cluster configurations when all the members of the + cluster restart at once, and may synchronize their queue processing + times. + +PH/14 The options never_users, trusted_users, admin_groups, and trusted_groups + are now expanded when the configuration file is read. + Exim version 4.52 ----------------- @@ -282,7 +314,7 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure rate limit. Conversely, if m and p are both small then messages must be sent at an even rate. - The key is used to look up the data used to calcluate the client's + The key is used to look up the data used to calculate the client's average sending rate. This data is stored in a database maintained by Exim in its spool directory alongside the retry database etc. For example, you can limit the sending rate of each authenticated user, @@ -297,7 +329,8 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure Each ratelimit condition can have up to two options. The first option specifies what Exim measures the rate of, and the second specifies how - Exim handles excessively fast clients. + Exim handles excessively fast clients. The options are separated by a + slash, like the other parameters. The per_mail option means that it measures the client's rate of sending messages. This is the default if none of the per_* options is specified. @@ -330,7 +363,12 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure updated. The effect of this is that Exim measures the client's average rate of attempts to send email, which can be much higher than the maximum. If the client is over the limit it will be subjected to - counter-measures until it slows down below the maximum rate. + counter-measures until it slows down below the maximum rate. The + smoothing period determines the time it takes for a high sending rate + to decay exponentially to 37% of its peak value, which means that you + can work out the time (the number of smoothing periods) that a client + is subjected to counter-measures after an over-limit burst with the + formula ln(peakrate/maxrate). The leaky option means that the client's recorded rate is not updated if it is above the limit. The effect of this is that Exim measures the @@ -353,13 +391,12 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure # Log all senders' rates warn ratelimit = 0 / 1h / strict - log_message = \ - Sender rate $sender_rate > $sender_rate_limit / $sender_rate_period + log_message = Sender rate $sender_rate / $sender_rate_period # Slow down fast senders warn ratelimit = 100 / 1h / per_rcpt / strict - delay = ${eval: 10 * ($sender_rate - $sender_rate_limit) } + delay = ${eval: $sender_rate - $sender_rate_limit }s # Keep authenticated users under control deny @@ -373,8 +410,8 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure # Restrict incoming rate from each host, with a default rate limit # set using a macro and special cases looked up in a table. defer - message = Sender rate $sender_rate exceeds \ - $sender_rate_limit messages per $sender_rate_period + message = Sender rate exceeds $sender_rate_limit \ + messages per $sender_rate_period ratelimit = ${lookup {$sender_host_address} \ cdb {DB/ratelimits.cdb} \ {$value} {RATELIMIT} }