https://bugs.exim.org/show_bug.cgi?id=1298
Git Commit <g...@exim.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |g...@exim.org
--- Comment #2 from Git Commit <g...@exim.org> ---
Git commit:
https://git.exim.org/exim.git/commitdiff/25ca84e25a47ccf8e1e0560ebd88794dabeb8db5
commit 25ca84e25a47ccf8e1e0560ebd88794dabeb8db5
Author: Jeremy Harris <jgh146...@wizmail.org>
AuthorDate: Wed Apr 18 23:27:15 2018 +0100
Commit: Jeremy Harris <jgh146...@wizmail.org>
CommitDate: Wed Apr 18 23:27:15 2018 +0100
Docs: rewrite description of 'leaky' ratelimit. Bug 1298
---
doc/doc-docbook/spec.xfpt | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt
index 63a78fc..b1cc468 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
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim
details at http://www.exim.org/ ##
