[
https://issues.apache.org/jira/browse/MIME4J-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670123#action_12670123
]
Markus Wiederkehr commented on MIME4J-68:
-----------------------------------------
Currently non-canonical line endings can be produced if:
* the raw value of a header field contains non-canonical line endings
* the preamble or epilogue of a multipart contains non-canonical line endings
* a TextBody contains non-canonical line endings and is not transfer-encoded
accordingly
* a BinaryBody contains non-canonical line endings and is not transfer-encoded
accordingly
Header fields, preamble and epilogue could be canonicalized easily using a
regex search and replace or something similar.
A TextBody could be canonicalized using a filter stream.
A BinaryBody that is not transfer encoded is probably intentional (HTTP) and
should be left as is.
Anyway, I think we should postpone this one to 0.7..
> Message.writeTo should produce canonical MIME end of lines.
> -----------------------------------------------------------
>
> Key: MIME4J-68
> URL: https://issues.apache.org/jira/browse/MIME4J-68
> Project: JAMES Mime4j
> Issue Type: Wish
> Affects Versions: 0.4
> Reporter: Stefano Bagnara
> Fix For: 0.6
>
>
> Opening this issue to track the status of the DOM part of the complicated
> line delimiter issues described in MIME4J-60. Leave MIME4J-60 for the parsing
> issue, only.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
