From 14702f5b13007409b29615f2a2ad1b141a4b9561 Mon Sep 17 00:00:00 2001 From: Philip Hazel Date: Wed, 17 Nov 2004 15:21:10 +0000 Subject: Respect the 75-character limit for "encoded words" when doing RFC 2047 encoding, and increase the buffer size for ${rfc2047: expansion. --- doc/doc-txt/ChangeLog | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/doc-txt/ChangeLog b/doc/doc-txt/ChangeLog index 4f49ef8e5..251de3fd4 100644 --- a/doc/doc-txt/ChangeLog +++ b/doc/doc-txt/ChangeLog @@ -1,4 +1,4 @@ -$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.29 2004/11/17 14:32:25 ph10 Exp $ +$Cambridge: exim/doc/doc-txt/ChangeLog,v 1.30 2004/11/17 15:21:10 ph10 Exp $ Change log file for Exim from version 4.21 ------------------------------------------- @@ -122,6 +122,13 @@ Exim version 4.44 is then used to implement four new variables: $spool_space, $log_space, $spool_inodes, and $log_inodes. +32. The RFC2047 encoding function was originally intended for short strings + such as real names; it was not keeping to the 75-character limit for + encoded words that the RFC imposes. It now respects the limit, and + generates multiple encoded words if necessary. To be on the safe side, I + have increased the buffer size for the ${rfc2047: expansion operator from + 1024 to 2048 bytes. + Exim version 4.43 ----------------- -- cgit v1.2.3