Seeing “There was a problem while sending the test email.” in WP Mail SMTP with this extra line:
This means we were able to connect to your SMTP host, but were not able to proceed using the email/password in the settings.
In plain English. Your site can reach the SMTP server, but the server is rejecting your login. That usually means the email or password is wrong, or your provider requires an app password or a different mailer. Below is a step by step path you can follow yourself or send to your host.
WP Mail SMTP shows:
There was a problem while sending the test email.
This means we were able to connect to your SMTP host, but were not able to proceed using the email/password in the settings.
How do I fix this?
Short version
This error is about authentication, not connection.
WP Mail SMTP reached your SMTP host. The server then refused to continue with the email and password you supplied.
Most of the time it is one of these:
We will first confirm your WP Mail SMTP settings. Then we will fix account details and app passwords. After that we will look at provider specific notes and error logs.
If you want to jump ahead:
The plugin message:
There was a problem while sending the test email.
This means we were able to connect to your SMTP host, but were not able to proceed using the email/password in the settings.
tells us two things.
In SMTP logs, that often shows as:
SMTP Error: Could not authenticate.
535 5.7.x Authentication unsuccessful
So we focus on who you are logging in as and what password or token you are using.
First, confirm you are using the correct mailer and basic settings.
If you are using Other SMTP:
smtp.gmail.com for Gmail.smtp.office365.com for Microsoft 365.If any value is wrong, fix it using your provider documentation. WP Mail SMTP has an Other SMTP guide that lists common hosts and ports.
Click Save Settings after changes, then go to WP Mail SMTP → Tools → Email Test and send a new test. If the error persists, move on.
This error often appears when:
Many SMTP providers expect these to match or at least be allowed as a send as address.
In WP Mail SMTP → Settings:
Still in the settings:
[email protected].Do not copy and paste with extra spaces. If you are unsure, reset the mail account password in your email control panel, then paste the fresh value into WP Mail SMTP.
Save settings, then send another test email.
If the error remains and you use a large provider like Google, Microsoft, Yahoo, Zoho, or iCloud, you probably need an app password instead of your normal login.
Many email providers do not allow your normal account password for SMTP logins from apps. They require a special password or token just for SMTP.
These include:
If you see a message like “This means we were able to connect to your SMTP host, but were not able to proceed using the email/password” and you are using one of these, it is very likely you are still using the normal account password.
The exact steps differ per provider. In general you:
Then:
The WP Mail SMTP docs have provider specific links inside the app password section. Those walk through Gmail, Outlook, Yahoo, Zoho, Proton, and others.
If you still see the error after switching to an app password, look at the provider specific notes next.
If your SMTP Host is smtp.gmail.com:
Follow the Gmail steps in the official WP Mail SMTP docs:
Gmail SMTP settings and app password.
Also:
If you keep hitting authentication errors with Gmail SMTP, consider switching to the Gmail mailer in WP Mail SMTP. That uses OAuth and avoids many SMTP login issues:
Gmail mailer setup.
If your SMTP Host is smtp.office365.com:
Recommended settings from the WP Mail SMTP guide:
Important. Microsoft is retiring basic SMTP authentication for many tenants. If SMTP AUTH is disabled, you will see logs like:
535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant
In that case you must:
You can see the official notes here:
Outlook mailer setup guide.
If your business has SMTP AUTH disabled on purpose, you will need to use the Outlook mailer or another transactional provider instead of direct SMTP.
If you use a custom mail server or shared hosting mail:
Many shared hosts give cPanel. In cPanel you can:
Copy exactly what they show into WP Mail SMTP. Then send a new test email.
If you still see authentication errors, check the detailed debug log.
WP Mail SMTP can show a detailed log of what the server replied when login failed.
If it fails, you should see a link or section for a full error log. Copy that text.
In the log, look for lines like:
SMTP Error: Could not authenticate.
535 5.7.8 Username and Password not accepted
or
Authentication unsuccessful, SmtpClientAuthentication is disabled
These messages come directly from your email provider. They tell you whether it is a plain wrong password, a blocked login, or a disabled SMTP feature.
If you open a ticket with your host or email provider, include this log. It speeds up their diagnosis.
You can also review the general troubleshooting guide from WP Mail SMTP here:
Troubleshooting WP Mail SMTP.
If you have checked settings and tried an app password but tests still fail, your provider needs to look at their side.
When you open a ticket, include:
There was a problem while sending the test email. This means we were able to connect to your SMTP host, but were not able to proceed using the email/password in the settings.Then ask them to confirm:
Often they will adjust a setting like SMTP AUTH or unblock your server, and the next test will work.
You are in good shape when:
Hit Continue Chat below and tell me:
I can help you turn that into clear next steps you can follow or send to your provider.
Scroll down to the contact form below. Enter your name, email, and WordPress needs. Atiba will get back to you as soon as possible.
WP Assistant is a free tool created by Atiba Software, a WordPress design and development company located in Nashville, TN. If you need more personalized WordPress assistance let us know, and we’ll get back to you ASAP!