[
https://issues.apache.org/jira/browse/NIFI-11977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757498#comment-17757498
]
David Handermann commented on NIFI-11977:
-----------------------------------------
[~markap14] Thanks for highlighting this area for improvement. An alternative
approach would be set the character set argument in MimeMessage.setSubject() in
the relevant places. Although UTF-8 is commonly used across the framework, it
would be helpful to evaluate the full impact of this change in terms of various
components that use the Jakarta Mail library.
> Update bootstrap.conf to specify mail.mime.charset
> --------------------------------------------------
>
> Key: NIFI-11977
> URL: https://issues.apache.org/jira/browse/NIFI-11977
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration, Core Framework
> Reporter: Mark Payne
> Priority: Major
> Labels: beginner, easyfix, newbie
>
> The PutEmail processor makes use of the Jakarta Mail library. The does not
> allow specifying the character set used for the email subject, though it does
> for the message body. As a result, if there are unicode characters, they do
> not come across properly in the subject but instead have a bunch of question
> marks instead.
> However, the issue appears to be resolved by updating conf/bootstrap.conf
> with the following:
> {quote}java.arg.mail.charset=-Dmail.mime.charset=UTF-8
> {quote}
> Given that we make UTF-8 the default everywhere else that we have the ability
> to specify it, we should include this by default in bootstrap.conf
--
This message was sent by Atlassian Jira
(v8.20.10#820010)