Bug#326642: fails to translate UTF-8 headers

[Andreas Metzler]

On 2005-09-04 Zap-W <zapw at maild.mine.nu> wrote:
> Package: exim4-daemon-heavy
> Version: 4.50-8
> Severity: normal

> Hi, i use Exim filters to extract $header_from and $header_subject from
> emails my .forward file looks as follows:

> # Exim filter
> if error_message then finish endif
> headers charset "UTF-8"
> save Maildir/
> pipe "/home/zapw/sms $header_from $header_subject"
[...]
> Now it works perfectly with email headers encoded in  cp1255 ,
> ISO-8859-8 ( these are Hebrew ) and even with UTF-8 , Except! for
> some weird reason in UTF-8 headers once the header reaches a certain
> length it dosen't get translated ?! exim extracts the headers as it
> is without processing/translating them, why?

Hello,
Confirmed but not a bug.

e.g. this:
echo foo | mail -s \
  '=?iso-8859-1?B?bG9uZ/b29vbE9vb29sT29vb2xPb29vbE9vb29sT29vb2xPb29vbE9vb29sT29vb2xPb29vbE?=' \
  ametzler at localhost
will demonstrate the behavior. 

However this message is broken with respect to
http://www.ietf.org/rfc/rfc2047.txt
| An 'encoded-word' may not be more than 75 characters long, including
| 'charset', 'encoding', 'encoded-text', and delimiters.

By converting this to a valid message, implementing the suggestion in
the rfc

| If it is desirable to encode more text than will fit in an
| 'encoded-word' of 75 characters, multiple 'encoded-word's (separated
| by CRLF SPACE) may be used.

echo foo | mail -s \
'=?iso-8859-1?B?bG9uZ/b29vbE9vb29sT29vb2xPb29vbE9vb29sQ=?=
 =?iso-8859-1?B?9vb29sT29vb2xPb29vbE9vb29sT29vb2xA==?=' \
ametzler at localhost

we get a correct message and exim decodes the subject without any
problems.
               cu andreas
-- 
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"