[
https://issues.apache.org/jira/browse/MIME4J-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405000#comment-13405000
]
Andrzej Rusin commented on MIME4J-109:
--------------------------------------
I saw something like this in the wild:
Content-Type: application/octet-stream; name==?UTF-8?B?MDAwMDAwNDguUERG?=
and the name got not parsed in the content-type parameters.
Is it possible to do something about it? Esp. that RFC 2231 allows that...
> Support for MIME Parameter Value and Encoded Word Extensions
> ------------------------------------------------------------
>
> Key: MIME4J-109
> URL: https://issues.apache.org/jira/browse/MIME4J-109
> Project: JAMES Mime4j
> Issue Type: New Feature
> Affects Versions: 0.5
> Reporter: Markus Wiederkehr
> Assignee: Markus Wiederkehr
> Fix For: 0.8
>
> Attachments: rfc2231.patch
>
>
> See RFC 2231.
> Mime4j should be capable of correctly decoding and encoding these extensions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
