[
https://issues.apache.org/jira/browse/EMAIL-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107950#comment-14107950
]
Mike Gratsas commented on EMAIL-104:
------------------------------------
Trying to send E-mail messages from the Sharp IMG Viewer web site
http://sharpimg-viewer.appspot.com powered by Google AppEngine using the latest
Commons Email version 1.3.3 I found an issue. I called the method
mail.setHtmlMsg(html); where mail is an instance of HtmlEmail class. However,
the HTML body is interpreted as plain text now since the content type was
changed from EmailConstants.TEXT_HTML to EmailConstants.TEXT_SUBTYPE_HTML in
version 1.3.2.
> 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
> Fix For: 1.3.2
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)
