[
https://issues.apache.org/jira/browse/MIME4J-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796511#action_12796511
]
Nevin commented on MIME4J-138:
------------------------------
I have tried the latest version from the svn, my testcases are passed now.
The problem originated from the wrong DecoderUtil.java(old version) attached in
this page.
I guess MEMERJ-142 is also originated from the attached DecoderUtil.java.
> DecoderUtil.decodeEncodedWords() fails if encoded-text starts with an equals
> sign
> ---------------------------------------------------------------------------------
>
> Key: MIME4J-138
> URL: https://issues.apache.org/jira/browse/MIME4J-138
> Project: JAMES Mime4j
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Markus Wiederkehr
> Assignee: Markus Wiederkehr
> Fix For: 0.7
>
> Attachments: DecoderUtil.diff, DecoderUtil.java, mime4j-138.patch,
> RegexDecoderUtil.java
>
>
> For example "=?utf-8?Q?=20test?=" should be decoded as " test". Instead it
> does not get decoded at all.
> The problem is that DecoderUtil.decodeEncodedWords() falsely identifies
> =?utf-8?Q?= as the encoded word which cannot be decoded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
