[
https://issues.apache.org/jira/browse/MIME4J-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614385#action_12614385
]
Stefano Bagnara commented on MIME4J-53:
---------------------------------------
Sorry I've been Off Topic.
About THIS specific issue the problem was that the epilogue was not parsed at
all (I don't know why). 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. The CR LF conversion issue is already taken in consideration
in the mailing list and deserve its own JIRA issue once we defined what we
expect from the library.
> 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]
