Unable to send or receive emails in Postfix after updating to Plesk Obsidian 18.0.34 in Debian 9 OS: SASL authentication failure: no secret in database

Follow

Comments

6 comments

  • Avatar
    Rcapaul

    It doesn't work with /private/plesk_saslauthd because this entry is already in the smtpd.conf. When i change it to /var/spool/postfix/private/plesk_saslauthd it works.

    0
    Comment actions Permalink
  • Avatar
    Mike

    Our Plesk auto updated an hour ago automatically and it completely broke Postfix.. so the fix to check for updates does not work! Ours said there were no updates available.  I made the changes by RCapaul which fixed our problem. 

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    Rcapaul @Mike

    Plesk Obsidian 18.0.34 Update 2 released March, 25, contains the bugfix. In case the update did not fix the issue for you, please contact Plesk Technical support or the technical support team of the reseller you bought a license from.

    0
    Comment actions Permalink
  • Avatar
    Rcapaul

    Leonid Gukhman

     

    It works only with ports 465 SSL and 25 without SSL but with 587 TLS it doesn't works. When i change in /etc/postfix/sasl/smtpd.conf to /var/spool/postfix/private/plesk_saslauthd it works!

    0
    Comment actions Permalink
  • Avatar
    Mike

    18.0.34 Update 2 installed - issue still there.  Any clients using STARTTLS on port 587 for smtp sending is getting an auth error still.. 465/SSL works fine:

    Mar 31 09:25:30 psa1 postfix/smtpd[20453]: warning: unknown[xx.xx.xx.xx]: SASL DIGEST-MD5 authentication failed: authentication failure
    Mar 31 09:25:30 psa1 postfix/smtpd[20453]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
    Mar 31 09:25:30 psa1 postfix/smtpd[20453]: warning: unknown[xx.xx.xx.xx]: SASL LOGIN authentication failed: generic failure

    I'm logging a support ticket now with Plesk.  It also broke spamassassin as well. 

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    Rcapaul, @Mike

    The developers have confirmed that the submission service at port 587 is still affected - until the hotfix is released (no ETA, as of now), please leave the workaround applied. I have also edited the article; note that some of our customers needed to specify /private/plesk_saslauthd.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request