X-Git-Url: https://git.exim.org/users/heiko/exim.git/blobdiff_plain/6af56900ac77d083b8c3abc76bd808e6718412ee..5a03bd24ee73e09f4bd086654d5ad1fa9b973996:/doc/doc-txt/NewStuff

diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index 4640547ae..bbf27010d 100644
--- a/doc/doc-txt/NewStuff
+++ b/doc/doc-txt/NewStuff
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.72 2005/09/19 11:56:11 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
 -----------------
 
@@ -165,6 +175,9 @@ PH/13 A new letter, "H", is available in retry parameter sets. It is similar
       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
 -----------------
@@ -350,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
@@ -373,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
@@ -393,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} }