From dceb978c01ccd0cf02df96aa34ee9c7e151ca2fe Mon Sep 17 00:00:00 2001 From: Tony Finch Date: Wed, 27 Jul 2005 18:27:55 +0000 Subject: [PATCH] A ratelimit documentation clarification, 4.52/TF/04. --- doc/doc-txt/NewStuff | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff index bddf5b827..4df98e9de 100644 --- a/doc/doc-txt/NewStuff +++ b/doc/doc-txt/NewStuff @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/NewStuff,v 1.55 2005/07/23 20:59:16 tom Exp $ +$Cambridge: exim/doc/doc-txt/NewStuff,v 1.56 2005/07/27 18:27:55 fanf2 Exp $ New Features in Exim -------------------- @@ -164,6 +164,12 @@ TF/04 There is a new ratelimit ACL condition which can be used to measure example, you can limit the sending rate of each authenticated user, independent of the computer they are sending from, by setting the key to $authenticated_id. The default key is $sender_host_address. + Internally, Exim includes the smoothing constant p and the options in + the lookup key because they alter the meaning of the stored data. + This is not true for the limit m, so you can alter the configured + maximum rate and Exim will still remember clients' past behaviour, + but if you alter the other ratelimit parameters Exim will effectively + forget their past behaviour. Each ratelimit condition can have up to two options. The first option specifies what Exim measures the rate of, and the second specifies how -- 2.30.2