Need help?

Our experts have had an average response time of 13.14 minutes in February 2024 to fix urgent issues.

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

SMTP Error (535): Authentication failed – How we Fixed it

by | Apr 12, 2019

Everyone expect mails to work flawlessly, but that doesn’t always work.

Occasionally, mail servers may reject emails with some strange errors, such as “SMTP Error (535): Authentication failed

At Bobcares, we often get requests from customers to fix SMTP errors as part of our Technical Support Services.

Today, we’ll see how our Support Engineers help our customers to resolve such tough email errors.

 

What is SMTP Authentication?

Mail client like Outlook uses SMTP (Simple Mail Transfer Protocol) to send messages. Later, to download the mails E-mail clients use either POP or IMAP protocol.

But, for any reason, if the authentication fails, mail client like Outlook generates an appropriate error message.

“SMTP Error (535): Authentication failed” error is usually related to the bad user email settings in Microsoft Outlook.

That’s why, Email client configuration always need special attention. Now, let’s see the reasons behind this error and how our Support Engineers correct it for customers.

 

Causes For the “Error 535: Authentication failed”

From our experience in managing servers, we often see customers experiencing Auth error 535 due to the following reasons:

 

1. Incorrect Username and Password

When the username and password entered in the Email client are incorrect, it ends up in Error 535. Again, using the wrong the mail server can also cause authentication failures.

Usually, such mismatch in email login and password will be recorded in the mail server logs. This helps greatly in finding the exact email account with problems.

 

2. Account Disabled

Similarly, at times account can be disabled because of reasons like payment dues or spamming issue. This will also result in SMTP Error (535): Authentication failed.

So, it’s worth to login to the control panel and check the status of the customer account as well as the email account.

 

3. SMTP Authentication

If your email client do not have SMTP authentication turned ON, it can also result in error. Now, we’ll check on how to enable SMTP Authentication in the server side and client side.

 

How to configure SMTP Authentication in a Mail client

Turning OFF SMTP Authentication in the email client, show up errors such as: “Server says: SMTP Error (535): Authentication failed: Authentication failure.”

Luckily, configuring SMTP authentication is simple procedure. It involves modifying the SMTP configuration settings and making necessary changes.

For example, to turn ON SMTP Authentication in Mozilla Thunderbird,

  1. Open Thunderbird, go to Tools -> Account Settings -> Outgoing Server (SMTP)
  2. Select the outgoing server by clicking on it, then click the Edit button
  3. Under Security and Authentication, check the “username and password” option
  4. Fill in your email account username and click Ok.

Finally, configuration will show up as below.

 

Enable SMTP auth in the server

We already saw how to turn on SMTP Auth in email client. But, for this to work, the mail server should support SMTP Authentication. Let’s see how our Dedicated Engineers enable this for our customers.

 

SMTP Auth in Plesk server

SMTP connections on a Plesk server typically need authentication. Recently, one of our customers requested us to fix the “SMTP Error (535): Authentication failed”. Here, the server was not having SMTP auth turned ON. Therefore, our Support Engineers solved the issue by enabling “SMTP authentication” from his Plesk server.

The exact sequence of steps that we did were:

  1. We logged into Plesk
  2. We checked the SMTP authorization status under Tools & Settings > Mail Server Settings > Relay options.
  3. Finally, we ensured correct settings in Tools & Settings > Mail Server Settings > Enable SMTP service on port 587 on all IP addresses.

 

Enable SMTP Authentication In cPanel

Let’s have look on the steps to enable SMTP auth in cPanel server. SMTP authentication in cPanel allow sending messages via POP-before-SMTP. Here, once when the Outlook download the mails, there is no need to re-authenticate to send mails through SMTP.

Usually, SMTP authentication will be disabled in WHM by default. To enable SMTP Authentication , we go to WHM >> Service Configuration >> Service Manager and select the Antirelayd checkbox.

[Struggling with SMTP Auth problems? We can fix it for  you.]

 

Conclusion

In short,“ SMTP Error (535): Authentication failed” error happens when there is a problem with SMTP configuration of email clients. Today, we saw how Bobcares solved “SMTP Error 535 Authentication failed”.

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";

6 Comments

  1. stephen taylor

    And I Understand NONE of the above, can you explain this for mere mortals

    Reply
    • Maheen Aboobakkar

      Hello,

      We’ll be glad to chat with you (click on the icon at right-bottom).

      Reply
  2. TJ

    i’m encountering this problem with a Mail.com account using K-9 Mail mobile program. I ‘ve retyped my password, and confirmed its validity by signing in via the web. The settings in K-9 such as port, etc., are the same as other other accounts for Mail.com.

    Reply
    • Hiba Razak

      Hi,
      Please contact our support team via live chat

      Reply
  3. ABUZAR KHAN

    Authentication failed. Please check your username/password.
    Server returned error: “535-5.7.8 Username and Password not accepted. Learn more at 535 5.7.8 https://support.google.com/mail/?p=BadCredentials fy26-20020a05622a5a1a00b0031f41ea94easm11180244qtb.28 – gsmtp , code: 53

    Reply
    • Hiba Razak

      Hi,

      Our Experts can help you with the issue, we’ll be happy to talk to you on chat (click on the icon at right-bottom).

      Reply

Submit a Comment

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

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
_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

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