Skip to Content (Press Enter)
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP
3447Views
8Comments
"=?utf-8?Q?" in e-mail From field, caused by EmailAddressCreate?
Question
We got a complaint from one of our customers that the From field was illegible. It turned out it showed the quoted printable utf-8 encoding instead of the legible text. The full text read "=?utf-8?Q? MAIN=20Energie =0?=" <helpdesk@mainenergie.nl>, instead of "MAIN Energie" <helpdesk@mainenergie.nl>. Not all customers are effected though, most don't see the quoted printable but the intended name instead.

The e-mail address was composed by the platform built-in function EmailAddressCreate. Why does this function create a quoted printable From-field when all characters can be represented in plain ASCII? Is there a way to turn this off? (I guess not?) Is it only old e-mail programs having this problem with UTF-8 quoted printable, or is something else going on? If so, can we avoid it?



0
0
04 Jan 2016
Copy Link
2012-03-16 12-21-09
João Rosado
Staff
Hi Killian,

The quoted printable is only used when it has non-allowed characters.
Calling the EmailAddressCreate with "MAIN Energie" would not cause it to be encoded.
From what you wrote, that " =0" at the end is strange. Looks like your string is actually something like "MAIN Energie\0". ....but even with that I can't get the same result as yours:



Regards,
João Rosado
0
0
05 Jan 2016
Copy Link
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP
Hi João,

This is the exact code we use to create that e-mail address:

EmailAddressCreate(Site.NewMA_Notification_FromName, Site.NewMA_Notification_From)

Indeed the \0 is a bit strange. I checked the site property's value, and SQL returns 12 for the length when I query ossys_site_property, so it's really 'MAIN Energie' without any additional characters.

After typing the above, I decided to create a small test screen to see what happens. I basically did what was done in the original program, using EmailAddressCreate with two site properties. In my web mail client, it doesn't display a sender at all (!):



and when I inspect the headers, it says the From is:

From: "=?utf-8?Q?"MAIN=20Energie"=20?=" <ems@mainenergie.nl>

So in this case a spurious space after "MAIN Energie". I'm not sure where the problem lies, but as it is, it seems that the EmailAddressCreate function has some problems...
0
0
05 Jan 2016
Copy Link
2024-11-04 15-59-50
João Inácio
Hi,

We have the same problem, when the name has a space problem appears.


0
0
08 Jan 2016
Copy Link
2012-03-16 12-21-09
João Rosado
Staff
Hi,

I tracked the problem and it is as a side effect of a issue fix done in 9.0.1.35.
It's actually not an problem with the EmailAddressCreate but with the "From" field that is incorrectly double encoding the name just before the email is sent.

That issue (#997410) is going to be reverted (since it was to improve the usage of the from field without the need to use the EmailAddressCreate) and it's documentation improved.

So as workaround, until a that fix is made, do not use the EmailAddressCreate on the From field, writting directly the email in the
"Your Name <email@host.com>" format.

Regards,
João Rosado
0
0
08 Jan 2016
Copy Link
2017-05-24 05-47-08
Sivaramakrishna Repalle

João Rosado wrote:

Hi,

I tracked the problem and it is as a side effect of a issue fix done in 9.0.1.35.
It's actually not an problem with the EmailAddressCreate but with the "From" field that is incorrectly double encoding the name just before the email is sent.

That issue (#997410) is going to be reverted (since it was to improve the usage of the from field without the need to use the EmailAddressCreate) and it's documentation improved.

So as workaround, until a that fix is made, do not use the EmailAddressCreate on the From field, writting directly the email in the
"Your Name <email@host.com>" format.

Regards,
João Rosado

Hi Joao,

We are getting the same issue but with attachment file name & subject which is simple text and we did not used any encoding or built in functions. We have observed this behavior in Outsystems 11, used to work in 10.

Ex: If email attachment file name is "w4form2019.pdf", the email client receiving encoded string as "=?utf-8?Q?w4form2019.pdf?=" as file name. Similarly email subject also. 


Thanks,

Siva

0
0
19 Feb 2019
Copy Link
2020-09-15 13-07-23
Kilian Hekhuis
 
MVP
Hi João,

Thanks for the reply. Do you know what Platform version the "fix" will be reverted in?
0
0
11 Jan 2016
Copy Link
2016-07-15 19-11-34
Alexei

Hi, 

we are on Outsystems 10 and this issue is still present.  When you use the Mrs.  or Mr.  in the name. or an  ê for instance.


correction with a normal first name and last name also, on one DEV it is ok, but on TEST not

0
0
30 Aug 2018
Copy Link
2017-05-24 05-47-08
Sivaramakrishna Repalle

Alexei wrote:

Hi, 

we are on Outsystems 10 and this issue is still present.  When you use the Mrs.  or Mr.  in the name. or an  ê for instance.


correction with a normal first name and last name also, on one DEV it is ok, but on TEST not

Hi Alexei,

Do you able to fix this issues? we are facing the same issue with normal subjects as well after environment version upgrade to 11. 

Thanks,

Siva

0
0
23 Feb 2019
Copy Link
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.