• 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.

Plesk 11.5.30 after Update #6 --- no such user in mail authorisation database

KazimierasS

New Pleskian
[solved]Plesk 11.5.30 after Update #6 --- no such user in mail authorisation database

Immediatelly after update all users can't retrieve their emails
syslog shows:

Jul 21 11:55:38 panel authpsa[1775]: No such user '[email protected]' in mail authorization database
Jul 21 11:55:38 panel courier-imaps: LOGIN FAILED, [email protected], ip=[::ffff:IP.ADD.DDD.RES]
Jul 21 11:55:43 panel authpsa[1772]: No such user '[email protected]' in mail authorization database
Jul 21 11:55:43 panel courier-imaps: LOGIN FAILED, [email protected], ip=[::ffff:IP.ADD.DDD.RES]
Jul 21 11:55:48 panel authpsa[1772]: No such user '[email protected]' in mail authorization database
Jul 21 11:55:48 panel courier-imaps: LOGIN FAILED, [email protected], ip=[::ffff:IP.ADD.DDD.RES]


any suggestions ?

authlib uses module
authmodulelist="authpsa"
 
Last edited:
Thanks, Nikolay
ran /usr/local/psa/admin/sbin/mchk --with-spam, this fixed my issue

but got a new one that aliased domains stopped receiving emails

Jul 23 17:53:48 panel postfix/error[10975]: 8128E9FE1: to=<[email protected]>, relay=none, delay=0.12, delays=0.12/0/0/0, dsn=5.0.0, status=bounced (User unknown in virtual alias table)
Jul 23 17:53:48 panel postfix/bounce[10976]: 8128E9FE1: sender non-delivery notification: 9E450A023
 
Back
Top