WordPress guide

WordPress emails not sending or going to spam: causes and fixes

Forms that never notify you, password resets that never arrive, orders with no confirmation. It is almost always the same problem: WordPress sends without authenticating. Here is how to diagnose and fix it.

Why WordPress doesn't send email reliably

WordPress sends all of its email with the wp_mail() function: form notifications, password resets, comments, admin notices and, if you run WooCommerce, order emails.

By default, wp_mail() hands the message to your hosting server with PHP's mail() function, without authenticating. The email leaves from a server that isn't authorised to send on behalf of your domain, and mailbox providers don't trust it: they send it to spam or reject it. Sometimes it doesn't even leave, because the host limits or disables sending.

The fix is to stop WordPress using mail() and send through an authenticated SMTP server, with a sender on your domain and SPF and DKIM records published.

Short answer

Install an SMTP plugin (FluentSMTP, WP Mail SMTP or Post SMTP), connect it to an SMTP service with your verified domain (SPF and DKIM), force a sender on your domain and send a test email. If the test fails, the plugin shows you the server's reply, which tells you what to fix.

Symptoms

Signs that sending is the problem

If any of these sound familiar, WordPress is most likely sending with mail() from your host:

  • Contact forms don't notify you, or the notifications land in spam.
  • Users don't receive the password reset email.
  • Customers don't receive their order confirmation.
  • Emails reach addresses on your own domain, but not Gmail or Outlook.
  • The received email shows it was sent “via” your host's server, or warns that the sender couldn't be verified.
  • It used to work and stopped after a migration or a change of host.
Causes

The most common causes

CauseWhat happensHow to fix it
Sending with PHP mail()The email leaves your host's server unauthenticated and without a DKIM signature for your domain.Send through authenticated SMTP with an SMTP plugin.
Missing SPF, DKIM or DMARCThe receiving server can't confirm the email is legitimate, so it filters or rejects it.Publish the sending service's DNS records and verify the domain.
Sender on another domainThe form uses the visitor's address as the sender, a Gmail one for example, and your server isn't authorised to send on behalf of that domain.Always use a sender on your domain and put the visitor's address in Reply-To.
Host limits or blocksThe host caps how many emails go out per hour or blocks outbound SMTP ports.Send with an external service on port 587 or 465.
A plugin changes the senderAnother plugin, such as a form or a store, overwrites the sender with an address that isn't on your domain.Force the sender in the SMTP plugin.
Diagnosis

How to diagnose it step by step

  1. 1Send a test to a Gmail or Outlook address: reset the password of a test user or fill in a form on your site.
  2. 2Check the recipient's spam folder and the promotions or other tabs.
  3. 3If it arrives, open the original message (in Gmail, Show original) and check the SPF, DKIM and DMARC results. If any of them isn't PASS, the problem is authentication.
  4. 4Look at the sender address. If it isn't on your domain, or it's the default wordpress address WordPress sets, change it to one of yours.
  5. 5If it never arrives, ask your host whether they limit or block sending with mail() or outbound SMTP ports.
  6. 6Install an SMTP plugin with an email log: from then on, every send is logged with its result and the server's reply.
Fix

The fix: send through authenticated SMTP

An SMTP plugin changes how wp_mail() delivers email: instead of mail(), it connects to an SMTP server with a username and password. No code changes, and it works for any plugin that sends with wp_mail().

Before setting it up, add your domain to the sending service and publish its DNS records: SPF and DKIM, plus DMARC if you don't have one yet. Then use these values in the plugin:

SettingValue with Mailiqo
SMTP serversmtpmq.mailiqo.com
Port587
EncryptionTLS (STARTTLS). If you use port 465, choose SSL
AuthenticationOn, with the domain's SMTP username and password (under Email → Domains)
SenderAn address on your verified domain, for example [email protected]
Force senderOn, so no other plugin can change it

The sender's domain must match the verified domain exactly: if you verify yourdomain.com, an address on shop.yourdomain.com isn't covered.

Plugins

Which SMTP plugin to choose

The three most used work with any SMTP service. WordPress.org figures as of 2 November 2026:

PluginActive installationsEmail logMost useful
FluentSMTP700,000+Included freeFallback connection if the main one fails and the option to store credentials in wp-config.php
WP Mail SMTP4 million+Pro version onlyThe most installed; lets you define the password with a constant in wp-config.php
Post SMTP300,000+Included freeSetup wizard and Fallback Mailing

Keep a single SMTP plugin active: with two, one overrides the other and it's hard to tell which one is sending.

Forms

Contact forms: the right sender

Form plugins (Contact Form 7, WPForms, Gravity Forms…) send with wp_mail(), so once the SMTP plugin is set up they also go out through the authenticated server. What fails most often is the sender:

  • The sender (From) must be an address on your domain, always the same one.
  • The visitor's address goes in Reply-To: when you reply, the answer reaches whoever wrote to you.
  • If a form won't let you change the sender, turn on force sender in the SMTP plugin.
  • After every change, send a real test from the form.
Spam

If emails arrive, but in spam

If sending is already authenticated and some messages still end up in spam, check the following:

  • SPF and DKIM verified in the sending service, and a DMARC record published (start with p=none).
  • The same sender on every email, on your domain and with a recognisable name.
  • Notification content, not advertising: a clear subject, little promotional copy and links to your own domain.
  • Real recipients: bounces and non-existent addresses hurt your domain's reputation.
  • If you're about to send much more volume than usual, ramp it up gradually.
FAQ

Frequently asked questions

Why don't WordPress password reset emails arrive?

Because they go out the same way as the rest: wp_mail() with PHP mail(). If your host doesn't deliver them or the recipient's provider filters them, they don't arrive either. Setting up an SMTP plugin with your verified domain fixes it for every email at once.

Can I keep using PHP mail() if I set up SPF?

SPF helps, but with mail() you depend on how your host has configured the server: whether it signs with DKIM for your domain, which limits it applies and which other sites share its reputation. And you get no record of what happens to each email.

Can I use Gmail or Outlook SMTP in WordPress?

You can, but those mailboxes are designed for people, not for a website's automated sending: they have usage limits and usually require app passwords or OAuth. For a site or a store, a transactional sending service with your own domain is a better fit.

Do I need to touch any code?

No. The SMTP plugin is configured from the WordPress dashboard and applies to every email sent with wp_mail(), including other plugins' emails.

How do I know whether an email arrived?

The plugin's email log tells you whether the SMTP server accepted it. To see what happened next, Mailiqo has Email → Logs, with the status of every send and, if it bounces, the destination server's reply.

Mailiqo

Send WordPress email with your domain

Mailiqo gives you authenticated SMTP for WordPress, with your verified domain and a log of every send in the dashboard. Start free, no card required.

Create a free account
Mailiqo Labs

Put the guide into practice

The tools let you check SPF, DMARC, headers, bounces and HTML with your own data, without registering.