You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Siegfried Goeschl (JIRA)" <ji...@apache.org> on 2011/09/06 23:39:10 UTC

[jira] [Commented] (EMAIL-104) The system property "mail.mime.charset" is not applied to contents.

    [ https://issues.apache.org/jira/browse/EMAIL-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098383#comment-13098383 ] 

Siegfried Goeschl commented on EMAIL-104:
-----------------------------------------

I'm not sure if I understand the problem correctly

+) setTextMsg() and setHtmlMsg() take the plain string
+) that plain strings are afterwards encoded when the MimeMessage is built (HTMLEmail.build())

Can you please clarify?

> The system property "mail.mime.charset" is not applied to contents.
> -------------------------------------------------------------------
>
>                 Key: EMAIL-104
>                 URL: https://issues.apache.org/jira/browse/EMAIL-104
>             Project: Commons Email
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Hiroshi Ikeda
>            Assignee: Siegfried Goeschl
>            Priority: Minor
>              Labels: charset
>
> Both of JavaMail and Commons Email encode subjects and personal names with the system property "mail.mime.charset" when no charsets are specified via methods. Also they encode attached filenames with the property when the other system property "mail.mime.encodefilename" is set (regardless of RFC). On the other hand, JavaMail encodes text contents with the property via setText methods when no charsets specified, but Commons Email doesn't encode the contents via setMsg/setTextMsg/setHtmlMsg methods. The partial difference of the behaviors makes confusion.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira