summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPhilip Hazel <ph10@hermes.cam.ac.uk>2005-04-07 15:37:13 +0000
committerPhilip Hazel <ph10@hermes.cam.ac.uk>2005-04-07 15:37:13 +0000
commitd71748467d1443be8c3b84a23839ea975c125b0d (patch)
treec98b9a77f8a5b55ce3c7ee0ceb17ded20bf80baf /doc
parent9c4e8f608a0cb5dc688e3c8ac3bc13ef3cb42620 (diff)
Move duplicate checking till after routing. Should fix several subtle
bugs.
Diffstat (limited to 'doc')
-rw-r--r--doc/doc-txt/ChangeLog20
1 files changed, 19 insertions, 1 deletions
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index cb661b943..758317801 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.122 2005/04/07 10:54:54 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.123 2005/04/07 15:37:13 ph10 Exp $
Change log file for Exim from version 4.21
-------------------------------------------
@@ -212,6 +212,24 @@ PH/35 ACL_WHERE_MIME is now declared unconditionally, to avoid too much code
PH/36 The change PH/12 above was broken. Fixed it.
+PH/37 Exim used to check for duplicate addresses in the middle of routing, on
+ the grounds that routing the same address twice would always produce the
+ same answer. This might have been true once, but it is certainly no
+ longer true now. Routing a child address may depend on the previous
+ routing that produced that child. Some complicated redirection strategies
+ went wrong when messages had multiple recipients, and made Exim's
+ behaviour dependent on the order in which the addresses were given.
+
+ I have moved the duplicate checking until after the routing is complete.
+ Exim scans the addresses that are assigned to local and remote
+ transports, and removes any duplicates. This means that more work will be
+ done, as duplicates will always all be routed, but duplicates are
+ presumably rare, so I don't expect this is of any significance.
+
+ For deliveries to pipes, files, and autoreplies, the duplicate checking
+ still happens during the routing process, since they are not going to be
+ routed further.
+
A note about Exim versions 4.44 and 4.50
----------------------------------------