summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPhilip Hazel <ph10@hermes.cam.ac.uk>2006-02-09 14:50:58 +0000
committerPhilip Hazel <ph10@hermes.cam.ac.uk>2006-02-09 14:50:58 +0000
commit727071f81598850285bc4f6270a5bd9ad40c61ba (patch)
tree59a3baaaaeac791dfd9a3639e361a40a4e0bb7db /doc
parent1c098beb73a88ff34536904610cfcc3c8af839c9 (diff)
If a message is older than the "first failed" time when computing a
retry, use the message arrival time instead of the "first failed" time.
Diffstat (limited to 'doc')
-rw-r--r--doc/doc-txt/ChangeLog12
1 files changed, 11 insertions, 1 deletions
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index dd11682f1..cc82287fe 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.288 2006/02/08 16:10:46 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.289 2006/02/09 14:50:58 ph10 Exp $
Change log file for Exim from version 4.21
-------------------------------------------
@@ -106,6 +106,16 @@ PH/18 If quota_warn_message contains a From: header, Exim now refrains from
adding the default one. Similarly, if it contains a Reply-To: header, the
errors_reply_to option, if set, is not used.
+PH/19 When calculating a retry time, Exim used to measure the "time since
+ failure" by looking at the "first failed" field in the retry record. Now
+ it does not use this if it is later than than the arrival time of the
+ message. Instead it uses the arrival time. This makes for better
+ behaviour in cases where some deliveries succeed, thus re-setting the
+ "first failed" field. An example is a quota failure for a huge message
+ when small messages continue to be delivered. Without this change, the
+ "time since failure" will always be short, possible causing more frequent
+ delivery attempts for the huge message than are intended.
+
Exim version 4.60