Guillermo Grandes (JIRA) wrote:
[ http://issues.apache.org/jira/browse/JAMES-648?page=comments#action_12439630 ] Guillermo Grandes commented on JAMES-648:
-----------------------------------------

Reject... (I change corrupt but readable, by mail to trash), No, I don't like 
the idea,...

Well, rejecting it make the sender aware of the problem.
Otherwise you receive it corrupted: either way the message is invalid so it id not a big problem if it is corrupted even more.

But seem that in this case the one that violates more the RFC is JavaMail, that places 
"quoted-printable" instead of "7bit" in a message without 
Content-Transfer-Encoding when modify any header of msg.

Well, I don't like JavaMail, and I lost a lot of days try to workaround its MANY bugs, but I think this time it is not javamail that is doing it wrong.

It is clearly stated everywhere that you cannot have 8bit chars in the text of a message unless you use Content-Transfer-Encoding: 8bit. If no content-transfer-encoding is there there is no rule about what to do.

Javamail adds quoted-printable simply because it find the 8bit char: try removing the 8bit char and I bet that Javamail won't add the Content-Transfer-Encoding anymore.

So the source message is wrong: if you add Content-Transfer-Encoding: 7bit you will change the message and corrupt it more anyway... There is no (I can't see it) clean solution/workaround for this: you can fix some mail, but mangle much more the others if you add workarounds.

Stefano

Corrupted MIME message with 8bit in body
----------------------------------------

                Key: JAMES-648
                URL: http://issues.apache.org/jira/browse/JAMES-648
            Project: James
         Issue Type: Bug
   Affects Versions: Trunk
        Environment: James 3.0
           Reporter: Guillermo Grandes
        Assigned To: Norman Maurer
        Attachments: 
4D61696C313135393436303732323938332D323834.Repository.FileStreamStore, 
james-proccesors.xml, traces.txt



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to