Bobcares

“SASL login authentication failed generic failure”- Here’s how to fix

by | Dec 3, 2018

I can’t login to my email account via Outlook. No errors are shown, the window with login and password pops up again and again. Please help!

That was a recent support request that we received in our Outsourced Technical Support helpdesk for Web Hosts.

On checking the server logs, we saw the error “SASL login authentication failed: generic failure“.

Today, let’s see the top causes for this error and how we fix them.

 

What is SASL?

Before seeing the details of the error, we’ll first understand about SASL.

Simple Authentication and Security Layer (SASL) is a method for authentication and data security in email protocols.

SASL supports various mechanisms for authentication like “PLAIN“, “shared secret“, etc.

The PLAIN mechanism works by transmitting a userid, an authentication id, and a password to the server. And, the server then determines whether that is an allowable triple.

Only when this is successful, server allows further transaction of email data.

 

What causes “SASL login authentication failed: generic failure” ?

Now that we have an idea about SASL, let’s check the causes for the error.

This error mainly happens when the SMTP authorization does not work, even with valid email login credentials. As a result, in a Postfix server, the exact lines in the log file read as :

Sep 26 13:39:58 mail postfix/smtpd[11102]: warning: SASL authentication failure: Password verification failed

Sep 26 13:39:58 mail postfix/smtpd[11102]: warning: unknown[x.x.x.x]: SASL PLAIN authentication failed: generic failure

Mostly, this is a result of bad configuration of the SASL plugin. Additionally, this happens when trying to send emails using the secure ports like 465, 587, etc. with SSL/TLS.

 

How to fix “SASL login authentication failed: generic failure”?

In Postfix, the error happens due to wrong configuration of TLS in /etc/postfix/master.cf file.

To ensure that the mail server accepts no mail without TLS encryption, we need to tweak a variable called “smtpd_enforce_tls“.

So to fix the error, our Support Engineers first take a backup of the configuration file. And, then set the value as  “smtpd_enforce_tls = yes” in the /etc/postfix/master.cf file.

After the edit, the entries will look like :

# grep 'submission' /etc/postfix/master.cf
192.0.2.2:submission inet n - y - - smtpd -o smtpd_enforce_tls=yes

Additionally, we ensure that the sasl config file contains no incorrect data.

In RedHat servers, the file is at /usr/lib64/sasl2/smtpd.conf and in Debian or Ubuntu servers, it is at  /etc/postfix/sasl/smtpd.conf

Altogether, these changes fixes the error and customers will be able to send mails fine.

 

Conclusion

SASL login authentication failed generic failure” error mainly happens due to wrong configuration of authentication mechanism in mail server. Today, we’ve seen the causes for the error and how our Support Engineers fix it.

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.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

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

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

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
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

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

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

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