WordPress Contact Form Emails Not Arriving? Fix It With SMTP

A contact form that doesn’t deliver is worse than no form at all. Visitors think they’ve reached you, and you never find out they tried. It’s one of the most common problems we fix on small business WordPress sites, and it almost never has anything to do with the form plugin itself.

The good news: once you understand why the emails disappear, the fix takes about fifteen minutes and usually works for good.

Why WordPress form emails go missing

When someone submits a form built with Contact Form 7, WPForms, Elementor Forms or most other builders, the plugin passes the message to a WordPress function called wp_mail(). Out of the box, that function hands the email to PHP’s built-in mail system on your web server.

That sounds fine, but there’s a catch. The server sends the email without logging in to any mail account. It simply claims to be wordpress@yourdomain.com (or whatever address the form uses) and hopes the receiving mail service believes it.

1. A visitor submits your formContact Form 7, WPForms or Elementor Forms receive the message
2. WordPress calls wp_mail()By default this hands the email to your server’s PHP mail function
3. Your server sends it without logging inOften from a shared IP address with a mixed reputation
4. Gmail or Outlook checks SPF, DKIM and DMARCThe From address claims your domain, but the server can’t prove it
5. Spam folder, or silently droppedYou never see the enquiry

SMTP fixes step 3: WordPress logs in to a real mailbox before sending.

Modern inboxes are much stricter than they used to be. Gmail, Outlook and Yahoo check three things before trusting a message:

• SPF: is this server allowed to send email for this domain?
• DKIM: is the message signed with the domain’s key?
• DMARC: what should happen if the first two checks fail?

A shared web server sending unauthenticated mail often fails one or more of these. The result is a message that lands in spam, or is quietly rejected without anyone being told.

First, confirm the problem

Before changing anything, check a few basics. It saves time if the issue turns out to be something simpler.

1. Check spam and junk folders on the address that should receive the form, including any filters or forwarding rules.
2. Check the form’s recipient setting. In Contact Form 7 that’s the Mail tab of the form; the default is your site’s admin email, which may not be the inbox you actually read.
3. Submit the form yourself and note the time. Look for a green success message; a red error usually means the server refused to send at all.
4. Ask your host whether PHP mail is enabled. Some hosts switch it off entirely to stop spam, in which case nothing will arrive until you add SMTP.

The fix: send through SMTP

SMTP (Simple Mail Transfer Protocol) is how real email programs send mail. Instead of your web server pretending to be your domain, WordPress logs in to an actual mailbox and sends the message from there, just like Outlook on your laptop does. Because it’s authenticated, receiving servers can verify it and deliverability improves dramatically.

We’ll use WP Mail SMTP in the steps below because it’s free, widely used and supports most providers. FluentSMTP and Easy WP SMTP work in a very similar way if you prefer them.

Choose where your emails will be sent from

The most important decision is which mailbox or service WordPress will log in to. Here’s how the common options compare for a small site:

Set up WP Mail SMTP with your host’s mailbox

This is the simplest route and the one we use most often for small business sites on cPanel hosting.

1. Create the mailbox if you don’t have one, for example info@yourdomain.com, in your hosting control panel. Note its password.
2. Find your SMTP details. In cPanel, open Email Accounts, click Connect Devices next to the mailbox and look for the Outgoing Server and SMTP Port. Use the SSL/TLS settings, not the “non-SSL” ones.
3. Install WP Mail SMTP from Plugins → Add New and activate it. Skip the setup wizard if you prefer to fill in the settings directly.
4. Set the From Email to the mailbox address, and tick Force From Email. A mismatched From address is the single most common reason SMTP “works” but mail still lands in spam.
5. Choose “Other SMTP” as the mailer and enter the SMTP Host, Encryption and SMTP Port. Port 465 goes with SSL; port 587 goes with TLS.
6. Turn Authentication on and enter the mailbox address as the SMTP Username and its password as the SMTP Password. Save.
7. Send a test from WP Mail SMTP → Tools → Email Test to a Gmail or Outlook address you can check. Then submit your real form once more.

If you use Outlook or Microsoft 365

This is where many older tutorials now give the wrong advice. Microsoft has been retiring “basic authentication” (a plain username and password) for sending mail.

• For personal Outlook.com, Hotmail and Live accounts, WP Mail SMTP’s own documentation says password sign-in no longer works with the generic “Other SMTP” option, so emails will stop sending.
• For Microsoft 365 business accounts, Microsoft delayed its original 2026 deadline. It now plans to turn off basic authentication for SMTP by the end of December 2026 for existing organisations, and new organisations created from January 2027 won’t be able to use it at all.

The practical answer is the same either way: choose the Outlook mailer in WP Mail SMTP, which signs in with Microsoft’s modern OAuth login instead of a stored password. If you set up Outlook with a password in the past and it has stopped working, this is almost certainly why.

If you use Gmail or Google Workspace

Google no longer accepts your normal account password for SMTP. You have two choices:

• App password: turn on 2-Step Verification for the Google account, create an app password in your Google Account security settings, and use it as the SMTP password with host smtp.gmail.com, port 587 and TLS.
• Google sign-in: WP Mail SMTP’s dedicated Google option connects through Google’s own login instead of a password. It takes a few more steps to set up but is more robust.

Either way, the From address must be the Gmail or Workspace address you signed in with (or an alias the account is allowed to send as).

Check your domain’s SPF and DKIM records

SMTP gets your emails authenticated, but your domain’s DNS records are what let other mail servers verify them. If you use your host’s mailbox, open Email Deliverability in cPanel. It shows whether SPF and DKIM are valid and offers a Repair button when they aren’t.

If your DNS is managed somewhere else, such as Cloudflare, copy the suggested records from cPanel into your DNS provider. If you send through Google, Microsoft or a transactional service, add the SPF and DKIM records that service gives you. A basic DMARC record (for example v=DMARC1; p=none;) is also worth adding so providers see that the domain is managed.

Frequently asked questions

Working on Elementor pages too? See our guide to fixing Elementor changes that don’t show on the live site.

Sources: WP Mail SMTP: Setting up the Other SMTP mailer; Microsoft: Updated Exchange Online SMTP AUTH deprecation timeline; Office 365 for IT Pros: SMTP AUTH retirement delayed; Contact Form 7 FAQ. Checked September 2026.

More in How-To & Fixes

How-To & Fixes

Elementor Changes Not Showing? Clear These Caches in Order

Saved a change in Elementor but the live page still looks old? Here's how to find which cache is holding the old copy and clear each layer in the right order.

Sep 28, 2026 · 8 min read