X-Git-Url: https://git.exim.org/users/heiko/exim.git/blobdiff_plain/3e46c1aa025624c859503f0c33b9a449d5f9ea93..a0d6ba8acc09196843fdea4132bb0814b2e81132:/doc/doc-txt/ChangeLog

diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 1f0b5dbd1..13e8b4272 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.259 2005/11/14 15:28:48 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
 -------------------------------------------
@@ -120,6 +120,16 @@ PH/10 Exim was violating RFC 3834 ("Recommendations for Automatic Responses to
 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
 -----------------