[
https://issues.apache.org/jira/browse/MIME4J-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16628455#comment-16628455
]
Stefano Bagnara commented on MIME4J-282:
----------------------------------------
Here is the FIRST example from the Quoted Printable RFC:
Thus if the "raw" form of the line is a single unencoded line that says:
Now's the time for all folk to come to the aid of their country.
This can be represented, in the Quoted-Printable encoding, as:
Now's the time =
for all folk to come=
to the aid of their country.
If you use Javamail to encode that line you won't get the result reported in
the RFC, and no one expect this. You just need a result that WHEN DECODED will
be the same of the original message. That's the point of QP.
https://www.ietf.org/rfc/rfc2045.txt
> DefaultMessageWriter.writeMessage doesn't produces the same original eml
> ------------------------------------------------------------------------
>
> Key: MIME4J-282
> URL: https://issues.apache.org/jira/browse/MIME4J-282
> Project: James Mime4j
> Issue Type: Bug
> Components: dom
> Affects Versions: 0.8.1
> Reporter: Raffaele Gambelli
> Priority: Major
> Attachments: mirmps_1.eml, mirmps_1_mime4j.eml
>
>
> I'm using mime4j to parse messages starting from a javax.mail.Message.
> Then, my application needs to store in a String the original message too,
> that is the "eml", I did it in this way:
> {code:java}
> ByteArrayOutputStream baos = new ByteArrayOutputStream();
> MessageWriter writer = new DefaultMessageWriter();
> writer.writeMessage(message, baos);
> this.originalMessage = baos.toString();{code}
> Unfortunately I've seen that above code, does QP encoding so the final output
> is different from the original message.
> But in this way, the final eml results in a different eml from the original
> one, so for example the digital signature is not more valid.
> For example if you open the generated eml with a client like Outlook, it
> warns user that the digital signature is not valid.
> Now, I would like to know if exists a way to, starting from an eml generated
> with the above code, generate the correct version, so without QP encoding.
> Attached to this issue, I put an original eml and that one generated with
> above code, thanks
> Maybe this issue is related or caused to this other #MIME4J-186 ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
