summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPhilip Hazel <ph10@hermes.cam.ac.uk>2006-02-28 11:25:40 +0000
committerPhilip Hazel <ph10@hermes.cam.ac.uk>2006-02-28 11:25:40 +0000
commit30dba1e609d941013dc8421de5104dad387ac5b1 (patch)
tree03360092d0a084fef98cc6392464a294b21b6ece /doc
parent8e3e25cac127659fa8b15f1ead18e1a39642f66b (diff)
Add References: support to autoreply.
Diffstat (limited to 'doc')
-rw-r--r--doc/doc-txt/ChangeLog5
-rw-r--r--doc/doc-txt/NewStuff13
2 files changed, 16 insertions, 2 deletions
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 45ea2866d..bbf590a1e 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.313 2006/02/23 12:41:22 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.314 2006/02/28 11:25:40 ph10 Exp $
Change log file for Exim from version 4.21
-------------------------------------------
@@ -236,6 +236,9 @@ PH/45 When the plaintext authenticator is running as a client, the server's
challenges. If an invalid string is ignored, an empty string is placed in
the variable.
+PH/46 Messages that are created by the autoreply transport now contains a
+ References: header, in accordance with RFCs 2822 and 3834.
+
Exim version 4.60
-----------------
diff --git a/doc/doc-txt/NewStuff b/doc/doc-txt/NewStuff
index c807d931b..04fedd633 100644
--- a/doc/doc-txt/NewStuff
+++ b/doc/doc-txt/NewStuff
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/NewStuff,v 1.90 2006/02/23 12:41:22 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/NewStuff,v 1.91 2006/02/28 11:25:40 ph10 Exp $
New Features in Exim
--------------------
@@ -87,6 +87,17 @@ PH/13 When the plaintext authenticator is running as a client, the challenges
this way. If an invalid base64 string is received when client_ignore_
invalid_base64 is set, an empty string is put in the $auth<n> variable.
+PH/14 Messages created by the autoreply transport now contain a References:
+ header. This is constructed in accordance with rules that are described
+ in section 3.64 of RFC 2822, which states that replies should contain
+ such a header line, and section 3.14 of RFC 3834, which states that
+ automatic responses are not different in this respect. However, because
+ some mail processing software does not cope well with very long header
+ lines, no more than 12 message IDs are copied from the References: header
+ line in the incoming message. If there are more than 12, the first one
+ and then the final 11 are copied, before adding the message ID of the
+ incoming message.
+
Version 4.60
------------