• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue mail_auth_dump Invalid or unsupported Unicode character

kevinjansen

Basic Pleskian
Server operating system version
Centos 7
Plesk version and microupdate number
Obsidian 18.0.50
Dear Community,

We runned against a problem that the renewed LE certificated are not replaced on the mail server.
The files got updated but the mailserver did not pickup the changes.
Therefore i runned "plesk repair mail -y" but that maked the issue even bigger.

All accounts got deleted and the repair tool ended with:

[2023-03-29 18:04:43.496] 27976:6424619b78a3f DEBUG [util_exec] [5b69522ebac954a2c0c04c85bf01a673-0] Starting: mail_auth_dump.worker --start
[2023-03-29 18:04:43.522] 27976:6424619b78a3f DEBUG [util_exec] [5b69522ebac954a2c0c04c85bf01a673-0] Finished in 0.02423s, Error code: 1
[2023-03-29 18:04:43.523] 27976:6424619b78a3f ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/mail_auth_dump.worker' '--start'] with exit code [1]
[2023-03-29 18:04:43.525] 27976:6424619b78a3f DEBUG [panel] Execute: '/usr/local/psa/admin/bin/send-error-report' 'warning'
Error: /usr/local/psa/admin/bin/mail_auth_dump.worker[29044]: Input parse error: Invalid or unsupported Unicode character or escape sequence found in string. UTF8 encoded characters and '\u' escape sequences are not supported. Error occured at offset 640, character '\'.

I have tried:
Users are not able to log into mailboxes: Invalid or unsupported Unicode character or escape sequence found in string - Support Cases from Plesk Knowledge Base
but without success.

The mail_auth_dump process shows the same error as above. And in /var/log/plesk/panel.log it says:

[2023-03-29 18:09:04.741] 45932:642462a0aec49 ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/mail_auth_dump.worker' '--start'] with exit code [1]
[2023-03-29 18:09:04.741] 45932:642462a0aec49 ERR [panel] PleskUtilException: '/usr/local/psa/admin/bin/mail_auth_dump.worker' '--start' failed with code 1.

stdout:


stderr:
/usr/local/psa/admin/bin/mail_auth_dump.worker[46997]: Input parse error: Invalid or unsupported Unicode character or escape sequence found in string. UTF8 encoded characters and '\u' escape sequences are not supported. Error occured at offset 640, character '\'.

file: /usr/local/psa/admin/plib/Service/Agent/Transport/Local/Exec.php
line: 60

code: 0

What i understand is that a password is not using a assci character, but it does not print me what account it is.
I tried to search in the database to all accounts, and compaired all the mail accounts (usernames) but none are using non alphabetical letters beside the . numbers and -_

But to change all the passwords is a last resort i want to do, cause then all that customers needs to be called since most of them are using there own email as communication and they are then not getting a password reset email.

What we can do now to resolve it?
 
Back
Top