[
https://issues.apache.org/jira/browse/EMAIL-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Neidhart resolved EMAIL-104.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.3.2
Fixed in r1532531 by using the appropriate setText() methods in case of text
content.
The corresponding unit tests can be further improved but there seems to be a
bug in junit when using non-standard charsets.
> 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.1#6144)
