Issue Email encoding after upgrade to 18.0.65

[manteca]

Server operating system version

Ubuntu 22.04.5 LTS

Plesk version and microupdate number

Plesk Obsidian 18.0.65

Hello,

This morning we updated to version 18.0.65 and the emails sent with the phpMailer library have started to arrive with strange characters when everything worked correctly before.

Here are some examples:
Tel��fono
Asunto: Informaci��n
Pa��s

 

[H.W.B]

After the update to version 18.0.65 i got a problem with sending emails.
I send messages to Germany in German and so a many special characters are used.
I did not change anything in the sending software.
But after the update to 18.0.65 these characters are not shown good anymore.


This was yesterday.
Today it is shown :

You can see the differnce.

Looks like the encoding is wrong, but how can i change this, or is this a BUG??

Henk

 

[YSP]

Can confirm.
We've also got the problem with incorrect email (html, multipart) encoding of umlauts and special chars after updating to 18.0.65.
It's obviously a serious bug.

 

[ChristophRo]

I can confirm this problem/bug on at least our Debian 11 servers (maybe a side effect of the PPPM-14624 fix?)

Did not dig to much into the details yet, but seems to also happens on receiving emails, when they get forwarded to a second mail address. (on same server)

 

[manteca]

I have the same problem. I was in the wrong forum when I posted it.

Issue - After upgrading to 18.0.65 charset mail problems

Hello, This morning we updated to version 18.0.65 and the emails sent with the phpMailer library have started to arrive with strange characters when everything worked correctly before. Here are some examples: Tel��fono Asunto: Informaci��n Pa��s

talk.plesk.com

 

[ipapachristoudis]

Same problem for us and for multiple servers (4-6).

 

[Sebahat.hadzhi]

Hey, everyone. We are sorry to hear about the issue you are all experiencing. I discussed the case with our team and we are currently investigating it. I will keep you posted on the matter.

 

[ipapachristoudis]

Hello
1. We use Postfix
2. Problem existed for emails sent both from mail clients like thunderbird and online php forms. From webmail things are better, we think there is no problem there.
3. We have no clue about this.

Some more info: yesterday when the problem arose, we thought it was a thunderbird issue in combination with the email signature and the email's format. In thunderbird, we found that when the email was sent both as html and plain text the problem arose. So when we changed the setting to only send emails as html to problem disappeared. My conclusion was that a problem exists in multipart emails, international characters and encoding. (Sorry for my bad english)

 

[Bitpalast]

Let's deactivate Plesk auto-updates again ;-) ...

 

[H.W.B]

I already made a ticket with the Support at Plesk. The Developers are looking in to it.

 

[_sashok]

YES

when forwarding letters - such ****

how can I quickly fix or roll back?

 

[ipapachristoudis]

problem can also occur from webmail (rouncube), trying to find a workaround

 

[Hangover2]

This bug also indicates that Plesk Obsidian does not appear to be the server admin panel of choice for Plesk’s own team when managing their services. Otherwise, this bug would have been identified by Plesk immediately, rather than by its users. It’s disappointing to see.

 

[ipapachristoudis]

For one of our customers we solved the problem at roundcube only when we set roundcube to use MIME encoding for 8-bit characters. So my main conclusion is that "default values" about encoding have changed somewhere into email functionality since the last update. It is really annoying, some customers may have the problem and may have not noticed it yet, we cannot find a proper workaround for everyone and we are in the dark.

 

[Maarten]

This bug also indicates that Plesk Obsidian does not appear to be the server admin panel of choice for Plesk’s own team when managing their services. Otherwise, this bug would have been identified by Plesk immediately, rather than by its users. It’s disappointing to see.

That's a bit harsh. Let's give the developers a chance to identify the bug and understand what’s causing the issue before jumping to conclusions. Plesk is a complex system, and sometimes unexpected issues pop up in specific setups. A bit of patience could go a long way here.

 

[_sashok]

Hey, everyone. We are sorry to hear about the issue you are all experiencing. I discussed the case with our team and we are currently investigating it. I will keep you posted on the matter.

any update?

or how can I quickly fix or roll back ?