Hi Isomorphic,
I have a question regarding mail headers (from, subject) and umlauts.
To me it seems there is some difference in how you set those.
This is my mail configuration in .ds.xml:
It results in such an email header (some fields redacted):
As you can see, some encoding information is set to the Subject. This does not happen to From and To.
Subjects are then displayed just fine in email programs, in to and from all umlauts are just removed - not there.
For to I do some replacement before. A user "Max Müller" <max.mueller@test.de> does not care if his name is written as "Max Mueller" <max.mueller@test.de> in general.
This is not true for from where there is normally a company name contained that should preserve the umlauts in a name.
I know that there is a javax setSubject() overload that is taking an encoding parameter and that there is no such thing for e.g. setFrom(), setsetRecipients(), but there must be some way to send umlauts here, I just can't find out how. Perhaps you can help as you either know this or can deduce it from the methods you are using when creating a mail.
In my .ds.xml, the velocity variables hold content fetched from the DB as normal type="text" field.
The text "original text with just umlauts removed" <xxx@yyy.net> from above in reality is "original text with just umlautsäöü removed" <xxx@yyy.net>
Best regards
Blama
I have a question regarding mail headers (from, subject) and umlauts.
To me it seems there is some difference in how you set those.
This is my mail configuration in .ds.xml:
Code:
<operationBinding operationType="fetch" operationId="writeMailLeadMovedToPicklist" serverMethod="writeMailLeadMovedToPicklist"> <mail contentType="text/html"> <from>$customerSettings.customerMailFrom</from> <to>$CASEWORKER_EMAILENTRY_USE</to> <bcc>$customerSettings.customerMailBCC</bcc> <subject>$t_translation.getTranslation($CASEWORKER_LANG_ISO_639_1_AL_2, "mail_leadMovedToPicklistTemplateReseller", "subject")</subject> <templateFile>mails/leadMovedToPicklistTemplateReseller.html</templateFile> </mail> </operationBinding>
Code:
Return-Path: <xxx@yyy.net> Delivered-To: xxx@yyy.net Received: from server.net by server.net with LMTP id ABCDEFGHIJKLM (envelope-from <xxx@yyy.net>) for <xxx@yyy.net>; Thu, 16 May 2019 10:45:20 +0200 Return-path: <xxx@yyy.net> Envelope-to: xxx@yyy.net Delivery-date: Thu, 16 May 2019 10:45:20 +0200 Received: from server.net ([1.2.3.4]:44330 helo=mytomcat) by server.net with esmtpsa (TLSv1:ECDHE-RSA-AES256-SHA:256) (Exim 4.91) (envelope-from <xxx@yyy.net>) id 1hRC0u-001Wm0-8o; Thu, 16 May 2019 10:45:20 +0200 Date: Thu, 16 May 2019 10:45:21 +0200 (CEST) [B]From: "original text with just umlauts removed" <xxx@yyy.net>[/B] [B]To: Givenname Surname <email@server.de>[/B] Message-ID: <478510790.490.1557996321528.JavaMail.tomcat@mytomcat> [B]Subject: =?Cp1252?Q?Ein_neues_Lead_ist_f=FCr_Sie_verf=FCgbar?=[/B] MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Subjects are then displayed just fine in email programs, in to and from all umlauts are just removed - not there.
For to I do some replacement before. A user "Max Müller" <max.mueller@test.de> does not care if his name is written as "Max Mueller" <max.mueller@test.de> in general.
This is not true for from where there is normally a company name contained that should preserve the umlauts in a name.
I know that there is a javax setSubject() overload that is taking an encoding parameter and that there is no such thing for e.g. setFrom(), setsetRecipients(), but there must be some way to send umlauts here, I just can't find out how. Perhaps you can help as you either know this or can deduce it from the methods you are using when creating a mail.
In my .ds.xml, the velocity variables hold content fetched from the DB as normal type="text" field.
The text "original text with just umlauts removed" <xxx@yyy.net> from above in reality is "original text with just umlautsäöü removed" <xxx@yyy.net>
Best regards
Blama
Comment