[request-tracker-maintainers] Bug#429560: request-tracker3.6: RFC 2047 header decoding is broken

[Niko Tyni]

Package: request-tracker3.6
Version: 3.6.1-4
Severity: normal
Tags: patch fixed-upstream

RT 3.6.1 decodes RFC 2047 MIME headers incorrectly when there are encoded
words mixed with unencoded equals ('=') signs in the same string. This
affects parsing of incoming emails, including their Subject lines, and
may result in a failure to extract the ticket number from the Subject
line of a ticket reply.

An example RFC 2047 encoded header is 

X-MyHeader: key="plain"; key="=?iso-8859-1?Q?encoded?="

Feeding this to the following one-liner:

% perl -Ilib -MRT::I18N -lne 'print RT::I18N::DecodeMIMEWordsToEncoding($_, "utf8")'

gives just 

"encoded" 

ie. everything before the encoded part is lost.

The attached patch was applied to upstream SVN branch 3.4-RELEASE as
revision 5822 (released in 3.4.6) and merged into branch 3.6-RELEASE
in revision 6039 (released in 3.6.2).

With the patch the above example decoder returns

X-MyHeader: key="plain"; key="encoded"

as expected.

I'll clone a separate bug to document this for the Etch 3.4 users too.

Cheers,
-- 
Niko Tyni   ntyni at iki.fi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: i18n.patch
Type: text/x-diff
Size: 600 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-request-tracker-maintainers/attachments/20070618/e1332399/attachment.patch