summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPhilip Hazel <ph10@hermes.cam.ac.uk>2005-11-15 10:08:24 +0000
committerPhilip Hazel <ph10@hermes.cam.ac.uk>2005-11-15 10:08:24 +0000
commita0d6ba8acc09196843fdea4132bb0814b2e81132 (patch)
tree60566ea7c8ab043c20b4f9148535f8ab7ad88a3f /doc
parenteba0c039a556478f50aa1e4839684027746197f7 (diff)
Add check_rfc2047_length to disable length checking for encoded words.
Diffstat (limited to 'doc')
-rw-r--r--doc/doc-txt/ChangeLog6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog
index 050fa034b..13e8b4272 100644
--- a/doc/doc-txt/ChangeLog
+++ b/doc/doc-txt/ChangeLog
@@ -1,4 +1,4 @@
-$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.261 2005/11/15 09:44:33 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
-------------------------------------------
@@ -126,6 +126,10 @@ 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
-----------------