Bug#326642: fails to translate UTF-8 headers

Andreas Metzler ametzler at downhill.at.eu.org
Tue Nov 15 18:37:58 UTC 2005


On 2005-09-05 Andreas Metzler <ametzler at downhill.at.eu.org> wrote:
> On 2005-09-04 Zap-W <zapw at maild.mine.nu> wrote:
[...]
>> 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.
[exim does not accept overlong rfc2047-words]

4.60 will feature this change.
| 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?

which will allow exim to be configured to decode broken RFC 2047.
           cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde




More information about the Pkg-exim4-maintainers mailing list