Add check_rfc2047_length to disable length checking for encoded words.

[exim.git] / doc / doc-txt / ChangeLog

diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 2215122b5f19c72044592978b529dd3c1fa7f077..13e8b4272f698d3f7caa623c35d3f0c17844db92 100644 (file)
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.258 2005/11/14 13:56:49 ph10 Exp $
+$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.262 2005/11/15 10:08:24 ph10 Exp $
 
 Change log file for Exim from version 4.21
 -------------------------------------------
@@ -117,7 +117,18 @@ PH/10 Exim was violating RFC 3834 ("Recommendations for Automatic Responses to
            processes, except for messages which are automatic responses to
            other messages.
 
+PH/11 Added "${if def:sender_address {(envelope-from <$sender_address>)\n\t}}"
+      to the default Received: header definition.
 
+PH/12 Added log selector acl_warn_skipped (default on).
+
+PH/13 After a successful wildlsearch lookup, discard the values of numeric
+      variables because (a) they are in the wrong storage pool and (b) even if
+      they were copied, it wouldn't work properly because of the caching.
+
+PH/14 Add check_rfc2047_length to disable enforcement of RFC 2047 length
+      checking when decoding. Apparently there are clients that generate
+      overlong encoded strings. Why am I not surprised?
 
 
 Exim version 4.54
@@ -147,6 +158,10 @@ TF/01 The control=submission/name=... option had a problem with syntax
 PH/05 Some modifications to the interface to the fake nameserver for the new
       testing suite.
 
+PH/06 Add ${if def:sender_address {(envelope-from <$sender_address>)\n\t}}
+      into the default Received: header string.
+
+
 
 Exim version 4.53
 -----------------