diff options
| author | Tony Finch <dot@dot.at> | 2005-09-22 12:03:36 +0000 |
|---|---|---|
| committer | Tony Finch <dot@dot.at> | 2005-09-22 12:03:36 +0000 |
| commit | 9ec05e5e69d25b2c6a971ceb6381156f886272fa (patch) | |
| tree | 7de7f9cd9525d32d5ddf2d04452001f6cffdab91 /doc | |
| parent | 0154e85a4031b840fc35109a84ff32f55c802d97 (diff) | |
Explain in the ratelimit docs how to work out the over-limit recovery time.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/doc-txt/NewStuff | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index 87e364df6..61abdfda7 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.73 2005/09/19 14:01:51 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.74 2005/09/22 12:03:36 fanf2 Exp $ New Features in Exim -------------------- @@ -353,7 +353,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 |