[jira] Resolved: (GERONIMO-4136) Encoding coversion issues with geronimo javamail

["Rick McGuire (JIRA)" <ji...@apache.org>]

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

Rick McGuire resolved GERONIMO-4136.
------------------------------------

    Resolution: Fixed

Committed revision 669901.  Geronimo specs
Committed revision 669902.  Geronimo javamail providers 

The JAF content handler for text used by javamail contained a TODO comment that encoding support still needed to be implemented.  Indeed it did.  That was the cause the problem.  All character/byte conversions in the data handler were being performed using the default encoding. 

> Encoding coversion issues with geronimo javamail
> ------------------------------------------------
>
>                 Key: GERONIMO-4136
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4136
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: mail
>    Affects Versions: 2.1.1
>            Reporter: Stefano Bagnara
>            Assignee: Rick McGuire
>         Attachments: TestAddFooter.java
>
>
> We have a test trying to add a footer to a message using iso-8859-15 charset:
> {code:title=AddFooterTest.java}
>     public void testAddFooterTextPlain() throws MessagingException, IOException {
>         // quoted printable mimemessage text/plain
>         String asciisource = "Subject: test\r\nContent-Type: text/plain; charset=ISO-8859-15\r\nMIME-Version: 1.0\r\nContent-Transfer-Encoding: quoted-printable\r\n\r\nTest=E0 and one\r\n";
>         String iso885915qpheader = "------ my footer =E0/=A4 ------";
>         String footer = "------ my footer \u00E0/\u20AC ------";
>         String res = processAddFooter(asciisource, footer);
>         assertEquals(asciisource + iso885915qpheader, res);
>     }
> {code}
> the result (using geronimo javamail) have an =80 instead of =A4 in the footer, meaning it probably used the cp1252 charset instead of the iso-8859-15 declared in the message header.
> processAddFooter(asciisource, footer) create a JAMES Mail object from sources and then runs it through the AddFooter mailet.
> The test has 4-5 dependencies and probably is not too hard to be run outside james:
> http://svn.apache.org/repos/asf/james/server/trunk/phoenix-deployment/src/test/org/apache/james/transport/mailets/AddFooterTest.java

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.