Bobcares

WHMCS SMTP error could not authenticate – Quick Fix!!

by | Nov 29, 2019

Is WHMCS SMTP error could not authenticate troubling you? We can help you with it.

Usually, this error occurs due to incorrect SMTP settings.

At Bobcares, we often receive requests to resolve these errors as part of our Server Management Services.

Today, let’s have a deep look at this error and see how our Support Engineers fix it easily.

 

Why do WHMCS SMTP error could not authenticate occur?

Isn’t it really frustrating to get error messages while sending important mails?

Usually, when such error occurs, we navigate to Utilities > Logs > Activity Log. And, we review the logs for the error message that occurred at the time of email sending.

Sometimes, the problem could be an authentication error due to incorrect SMTP settings.

An authentication error happens when the mail server rejects the provided SMTP details.

 

How we fix this SMTP could not authenticate error?

So, for getting more detailed information about the error, we usually add the below line to the configuration.php file,

$smtp_debug = true;

And, this will give a lot of debugging information regarding the error that has occurred while sending the email.

 

1. Incorrect SMTP settings

Sometimes, the general SMTP settings like port, host, username, password, etc stored in Setup > General Settings > Mail tab, maybe given incorrectly.

In such cases, the mail server blocks connections from the server upon which WHMCS has been installed.

So, in order to resolve the error, we need to make sure that we have provided the correct SMTP details.

Similarly, this error also occurs when an inappropriate SMTP port has been specified for use with the SSL Type option selected.

For instance, selecting SSL and port number 25 will cause this error.

 

2. SMTP restrictions

Recently, one of our customers approached us with a WHMCS SMTP error. He was getting authentication error messages whenever he tried to send emails.

Our Support Engineers checked the error in detail and found SMTP restrictions problem in it.

SMTP restrictions in WHM allow configuring the server so that only the MTA, Mailman mailing list software, and the root user can connect to the remote SMTP server.

And, it will automatically re-route any SMTP traffic leaving the server back to the localhost.

So, we disabled this option in WHM, Home >> Security Center >> SMTP Restrictions. This resolved the error and mail services worked fine.

 

[Need more assistance to resolve this error?- We’ll help you.]

 

Conclusion

In short, WHMCS SMTP error could not authenticate occur mainly due to incorrect SMTP settings and SMTP restrictions. Today, we have discussed this error in detail and saw how our Support Engineers fix this error for our customers.

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

2 Comments

  1. arabic keyboard

    thanks for the article but this is not working form me

    any other fix to try ?

    Reply
    • Maheen Aboobakkar

      If you are still facing 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 *

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