Articles in this section

Unicode special characters in messages sent from Plesk server are displaying incorrectly after the upgrade to Plesk Obsidian 18.0.65: Failed to build output message as bytes.; 'ascii' codec can't encode characters in position X: ordinal not in range(128)

kb: bug kb: fixed Plesk Obsidian for Linux

Symptoms

  • Plesk Outgoing Mail Control is enabled.

  • Plesk was upgraded to 18.0.65

  • Accentuated Unicode characters (such as à, é, è) in mail messages sent from Plesk server are showing like <?> (�).

  • Error messages like below can be found in /var/log/maillog:

Oct 30 12:34:56 plesk psa-pc-remote[1417]: 1234567890AB: py-limit-out: stderr: INFO:__main__:Setting 'X-PPP-Vhost' header to 'plesk.example.com'
Oct 30 12:34:56 plesk psa-pc-remote[1417]: 1234567890AB: py-limit-out: stderr: WARNING:__main__:Failed to build output message as bytes. Will try as string instead, which may result in extra modifications. Cause: 'ascii' codec can't encode characters in position 468-469: ordinal not in range(128)

Cause

Product issue:

  • #PPPM-14661 "Fixed the issue where, on Plesk servers with the “Outgoing Mail Control” and/or “Fix Incorrectly Set Sender for Outgoing Mails” features enabled, special characters (such as umlauts or accents) in multi-part messages could be replaced with other characters, such as “�”."

Fixed in:

Resolution

Please update Plesk to the latest version: How to install Plesk updates

Was this article helpful?

Comments

13 comments
Date Votes
  • The error also affects umlauts and only occurs if an e-mail contains an attachment.

    1
  • Das ist auch keine Lösung ein Fix des Problems ist eine Lösung aber die Sicherheitseinstellungen ab zu schalten, ist keine Lösung.

     

    1
  • Same thing started yesterday with Greek Characters when email has been sent from roundcube or thunderbird, outlook was ok.

    and only if you attach a file (.ini / .exe / .pdf / .dll )

    after your suggestion the problem has been resolved for now.

    1
  • Same issue, even without attachement, solved with the recommandations above BUT this reduce the security and quality of mail services so i hope this gonna be solved soon, no?

    ;b

    2
  • This fix does not help, it also affects characters like &euro; in latin-1 
     &euro; was converted to  ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ï¿½ 
    With the fix to: �.
    Forwarded to another Plesk server to: ���

    Lets hurry with the proper fix please!

    3
  • Same

    1
  • same here, outgoing limit off is a huge problem for security. Hope a patch will land soon! Thanks a lot!

    1
  • The fix does not work, I hope the problem is being fixed soon as this affecting alot of businesses. And its costing us money.

    1
  • This bug should have maximum priority, because the workaround is a real security problem. But at this point it seems to be the only solution to calm my customers.

    2
  • We need a solution asap! Either your mails looks like shit or your server is not able to sent all mails successfully - not what my customers are paying for…

    1
  • We have 6 servers with Plesk 18.0.65 and this issue is happening in all 6 servers! I think this should have maximum priority too, we have a lot of complains from our customers.

    2
  • We are experiencing numerous issues with this encoding bug, and the problem has persisted for over a week. Please resolve it NOW.

    1
  • Update about the issue…

    Few hours ago update of ( Plesk Obsidian 18.0.65 Update #1 ) has been published and fixes the above problems.

    installed and try it myself and everything works as it should be. 

    1

Please sign in to leave a comment.