[
https://issues.apache.org/jira/browse/MIME4J-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614390#action_12614390
]
Oleg Kalnichevski commented on MIME4J-53:
-----------------------------------------
Stefano,
Indiscriminate conversion of line delimiters regardless of their position
within the data stream is plain WRONG. I am still of an opinion
EOLConvertingInputStream is utterly and helplessly broken, at least for MIME
content transmitted over HTTP. The change you are proposing makes mime4j simply
useless for HttpClient and FileUpload
http://marc.info/?l=james-dev&m=121528134811461&w=2
> Now (not sure if this one have been fixed while solving MIME4J-55 or
> MIME4J-56) it is correctly parsed, so this specific issue is resolved for me.
Could you please then close the issue so it would be easier to tell which
issues still need attention?
Oleg
> decoding a message including a base64 encoded rfc822 message with mixed
> newlines result in parsing errors.
> ----------------------------------------------------------------------------------------------------------
>
> Key: MIME4J-53
> URL: https://issues.apache.org/jira/browse/MIME4J-53
> Project: Mime4j
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.4
>
>
> I just committed bad-newlines-multiple-parts.msg and
> bad-newlines-multiple-parts-base64.msg and respective expected output.
> The first is correctly decoded, the second is simply a base64 encoded rfc822
> mime content of the first one and show the bad result.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
