summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJeremy Harris <jgh146exb@wizmail.org>2018-04-18 23:27:15 +0100
committerJeremy Harris <jgh146exb@wizmail.org>2018-04-18 23:27:15 +0100
commit25ca84e25a47ccf8e1e0560ebd88794dabeb8db5 (patch)
treec41bc5f80b7026e6e7e6620e385f31c82de014bc /doc
parent4ae6e648660146fd44e7aa00669d00e49c17c31a (diff)
Docs: rewrite description of 'leaky' ratelimit. Bug 1298
Diffstat (limited to 'doc')
-rw-r--r--doc/doc-docbook/spec.xfpt14
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 63a78fc02..b1cc46862 100644
--- a/doc/doc-docbook/spec.xfpt
+++ b/doc/doc-docbook/spec.xfpt
@@ -30969,13 +30969,15 @@ rest of the ACL.
The &%leaky%& (default) 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
-client's average rate of successfully sent email, which cannot be greater than
-the maximum allowed. If the client is over the limit it may suffer some
-counter-measures (as specified in the ACL), but it will still be able to send
-email at the configured maximum rate, whatever the rate of its attempts. This
+client's average rate of successfully sent email,
+.new
+up to the given limit.
+This is appropriate if the countermeasure when the condition is true
+consists of refusing the message, and
is generally the better choice if you have clients that retry automatically.
-For example, it does not prevent a sender with an over-aggressive retry rate
-from getting any email through.
+If the action when true is anything more complex then this option is
+likely not what is wanted.
+.wen
The &%strict%& option means that the client's recorded rate is always
updated. The effect of this is that Exim measures the client's average rate