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

Postfix + SASL authentication failure: no secret in database

m0rpheu5

Regular Pleskian
Hello, guys i´m having problems with a form with a client, i´m having no issues with postfix at all, but one client, is having, i already check the password of the account and it´s ok, i can send and receive emails from horde etc. but when i try to fill the form and send the email i got the error above from maillog.

Nov 10 15:57:20 br01 postfix/smtpd[21587]: table hash:/var/spool/postfix/plesk/poplock(0,lock|fold_fix) has changed -- restarting
Nov 10 15:57:20 br01 postfix/smtpd[21591]: table hash:/var/spool/postfix/plesk/poplock(0,lock|fold_fix) has changed -- restarting
Nov 10 13:57:20 br01 postfix/smtpd[21734]: connect from unknown[127.0.0.1]
Nov 10 15:57:20 br01 postfix/smtpd[21734]: warning: SASL authentication failure: no secret in database
Nov 10 15:57:20 br01 postfix/smtpd[21734]: warning: unknown[127.0.0.1]: SASL DIGEST-MD5 authentication failed: authentication failure
Nov 10 15:57:20 br01 postfix/smtpd[21734]: disconnect from unknown[127.0.0.1]


What could be? the password is right, i already try to set my user and password, and i got the same problem, what could be??

Thanks
 
it´s centos x86_64, i already find the problem, it was on /usr/lib64/sasl2/smtpd.conf, i needed to edited then and remove from the line mech_list: the option DIGEST-MD5, so in this line now i have only:

mech_list: CRAM-MD5 PLAIN LOGIN

but why this??

Thanks
 
Back
Top