Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.98 minutes in June 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

Plesk SASL authentication failure error – How to resolve

by | Jun 16, 2021

Stuck with Plesk SASL authentication failure error? We can help you.

As part of our Server Management Services, we assist our customers with several Plesk queries.

Today, let us discuss the symptoms, cause, and fix to this error.

 

What causes Plesk SASL authentication failure error?

When you attempt to connect with the mail client registers you can see the following errors in the log file /var/log/maillog:

postfix/smtpd[5810]: warning: SASL authentication failure: no secret in database
postfix/smtpd[5810]: warning: example.com[0.0.0.0]: SASL DIGEST-MD5 authentication failed: authentication failure

postfix/smtpd[4288]: Unable to open database(readonly) /plesk/passwd.db: unable to open database file
postfix/smtpd[4288]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory

You might be unable to send or receive emails in Postfix after updating to Plesk Obsidian 18.0.34 in Debian 9 OS.

In some cases the Postfix service might be down.

It might cause if the Postfix smtpd.conf configuration file is corrupt.

 

How to resolve Plesk SASL authentication failure error?

Today, let us see the steps followed by our Support Techs in order to resolve this error.

  • Firstly, connect to the server via SSH.
  • Then, back up the Postfix configuration file /etc/postfix/master.cf:
# cp -a /etc/postfix/master.cf{,.backup}
  • Edit the Postfix configuration file /etc/postfix/master.cf, enable the chroot to the smtp, smtps and submission processes configuration:

From:

smtp inet n – – – – smtpd
smtps inet n – – – – smtpd -o smtpd_tls_wrappermode=yes
submission inet n – – – – smtpd -o smtpd_enforce_tls=yes -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination

To:

smtp inet n – y – – smtpd
smtps inet n – y – – smtpd -o smtpd_tls_wrappermode=yes
submission inet n – y – – smtpd -o smtpd_enforce_tls=yes -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,permit_sasl_authenticated,reject_unauth_destination
  • Then, back up the Postfix SASL configuration file /etc/postfix/sasl/smtpd.conf:
# cp -a /etc/postfix/sasl/smtpd.conf{,.backup}
  • Next, edit the Postfix SASL configuration file /etc/postfix/sasl/smtpd.conf, configure the saslauthd_path with the relative chrooted path:

From:

pwcheck_method: auxprop saslauthd
auxprop_plugin: plesk
saslauthd_path: /var/spool/postfix/private/plesk_saslauthd
mech_list: CRAM-MD5 PLAIN LOGIN
sql_engine: intentionally disabled
log_level: 4

To:

pwcheck_method: auxprop saslauthd
auxprop_plugin: plesk
saslauthd_path: /private/plesk_saslauthd
mech_list: CRAM-MD5 PLAIN LOGIN
sql_engine: intentionally disabled
log_level: 4
  •  Finally, restart Postfix to apply the changes:
# systemctl restart postfix

 

[Failed to resolve Plesk error? Feel free to contact us at anytime]

 

Conclusion

In short, today we saw the steps followed by our Support Techs to resolve authentication failure error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

server management

Spend time on your business, not on your servers.

TALK TO US

Or click here to learn more.

GET UP TO 25% OFF

Plesk Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management & end-user tech support to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.
server management

Spend time on your business, not on your servers.

TALK TO US

Or click here to learn more.

GET UP TO 25% OFF

Plesk Support

Spend time on your business, not on your servers.

Managing a server is time consuming. Whether you are an expert or a newbie, that is time you could use to focus on your product or service. Leave your server management & end-user tech support to us, and use that time to focus on the growth and success of your business.

TALK TO USOr click here to learn more.

Categories:

Tags:

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF