Ошибка аутентификации сервера smtp

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 a 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”.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Piping in late on a two-year-old closed thread, but since I have also encountered the same error, I’d like just to add my .02 …

Under PHP 7.4/Roundcube 1.4.3, ‘clearing’ those variables really means:

$config['smtp_user'] = '';
$config['smtp_pass'] = '';

Setting them to null will not work.

Under Ubuntu 20.04, Roundcube will be installed with at least a defaults.inc.php which gets loaded before config.inc.php (as it should be). So, skipping those two settings will not work, since defaults.inc.php has the following settings:

$config['smtp_user'] = '%u';
$config['smtp_pass'] = '%p';

So these two configuration variables must be explicitly overwritten in config.inc.php with the empty string '', or else SMTP will refuse to authenticate.

Of course, some Roundcube configurations may be even more convoluted and include several other configuration files beyond these. Actually, I had a few of those around, which I thought weren’t being included, but, to be on the safe side, I backed them up and deleted them — just keeping defaults.inc.php around, since it’s expectable that it will be overwritten with sensible defaults when Roundcube 1.4.4 ships. In other words, if the only configuration file you have is defaults.inc.php, do not touch it, but keep it intact, and just override what you wish/need on config.inc.php. I believe that at least those two are guaranteed to work, but it’s possible that some configurations only ship with defaults.inc.php (and you need to add your own config.inc.php) or possible just config.inc.php, filled in with all possible configuration values, which you may change — until the next Roundcube version comes around and wipes it clean…

An extra 👍 on the request for documenting this properly! After all, it might just require an extra comment line on defaults.inc.php… as @johnnyutahh so well mentioned, there are at least 3 ways to interpret ‘clearing’, according to context (i.e. each configuration variable may be ‘cleared’ differently…).

Jan
22
2022