[jira] [Updated] (MIME4J-282) DefaultMessageWriter.writeMessage doesn't produces the same original eml

["Raffaele Gambelli (JIRA)" <mi...@james.apache.org>]

     [ https://issues.apache.org/jira/browse/MIME4J-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Raffaele Gambelli updated MIME4J-282:
-------------------------------------
    Description: 
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 ?

  was:
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


> 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
>    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)