james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Wiederkehr (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Commented: (MIME4J-182) DecoderUtil.decodeEncodedWords() fails when the encoded word starts with a hex sequence
Date Wed, 15 Dec 2010 20:42:01 GMT

    [ https://issues.apache.org/jira/browse/MIME4J-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971826#action_12971826
] 

Markus Wiederkehr commented on MIME4J-182:
------------------------------------------

Just for the sake of completeness, this was fixed in MIME4J-138.

+1 for a 0.6.1 release.

> DecoderUtil.decodeEncodedWords() fails when the encoded word starts with a hex sequence
> ---------------------------------------------------------------------------------------
>
>                 Key: MIME4J-182
>                 URL: https://issues.apache.org/jira/browse/MIME4J-182
>             Project: JAMES Mime4j
>          Issue Type: Bug
>          Components: parser (core)
>    Affects Versions: 0.6
>            Reporter: Niklas Therning
>            Priority: Critical
>
> The perfectly legal encoded word =?ISO-8859-1?Q?=41?= should be decoded to A but in 0.6
the input is returned as if the input wasn't ok. I've backported the DecoderUtil.decodeEncodedWords()
method from 0.7 and it seems to work as expected. I'd say that a 0.6.1 should be released
quite soon with a fix for this issue since it's very likely to affect users. I could check
in the test case and the backported code. Should I create a bug fix branch for 0.6 then?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message