---
title: "WordPress Not Sending Emails? 6 Fixes That Work"
description: "WordPress hands email to your server's mail() by default, so it often never arrives. Test it, use your own domain, send via SMTP and add SPF and DKIM."
source: https://wpos.ai/blog/wordpress-not-sending-emails/
updated: 2026-11-13
---

[Black Friday](https://wpos.ai/black-friday/): 15,000 free credits + 50% off ends Nov 30

# WordPress Not Sending Emails? Why It Happens and How to Fix It

Password resets that never arrive, contact forms that go quiet, order emails in spam. By default WordPress hands every email to your server's own mail program, with no login and a sender address that may not exist, and many hosts and inboxes won't accept that. Here is how to find where the email stops, and fix it for good.

- Email delivery

- Step by step

- 2026

## The short answer

**WordPress doesn't log in to a mail server by default: it passes each email to PHP's `mail()` on your hosting server, from an address like `wordpress@yoursite.com`.** When the host blocks that, or Gmail and Yahoo can't verify the sender, the email disappears or lands in spam. Work through these in order:

- **Find out where it stops.** Send a test email and keep a log, so you know whether WordPress sends it at all.
- **Check the email is switched on** and goes to the right address, in WordPress, your form plugin or WooCommerce.
- **Send from your own domain,** never from a Gmail or Yahoo address.
- **Send through SMTP or an email service** with a plugin such as WP Mail SMTP or FluentSMTP.
- **Add SPF, DKIM and DMARC** records for your domain, so inboxes trust the mail.
- **Keep the log on,** so you can answer the next complaint in a minute.

## Why WordPress emails go missing

Every email WordPress sends, from password resets and new-user notices to comment alerts, form notifications and WooCommerce order emails, goes through one function, `wp_mail()`. In WordPress 7.1 it builds the message with the PHPMailer library and hands it to PHP's own `mail()` function, which passes it to whatever mail program the server has. There's no SMTP login and no settings screen.

That causes three kinds of trouble:

- **The server won't send it.** Some hosts switch `mail()` off or limit it to fight spam. WordPress's default sender, `wordpress@` plus your domain, doesn't help: a comment in WordPress's own code warns that "some hosts will block outgoing mail from this address if it doesn't exist".
- **"Sent" doesn't mean delivered.** The [PHP manual](https://www.php.net/manual/en/function.mail.php) is blunt: `mail()` returning true means the message was accepted for delivery, and "it does NOT mean the mail will actually reach the intended destination." WordPress reports success at the same point.
- **The inbox won't trust it.** [Gmail's sender guidelines](https://support.google.com/a/answer/81126) ask every sender to authenticate with SPF or DKIM, and say unauthenticated messages "might be marked as spam or rejected with a 5.7.26 error". [Yahoo](https://senders.yahooinc.com/best-practices/) asks the same. Mail sent straight from a web server rarely passes those checks.

| What you see | Most likely cause | Start with |
| --- | --- | --- |
| No email from the site arrives, not even a password reset | The host blocks or limits PHP's mail() | Steps 1 and 4 |
| Emails arrive, but in spam | No SPF or DKIM for your domain, or a From address on another domain | Steps 3 and 5 |
| Only one form's or plugin's emails are missing | That notification is off or goes to the wrong address | Step 2 |
| WooCommerce order emails are missing | The email is disabled or skipped, or it's a delivery problem | The WooCommerce section |
| It stopped after a move to a new host | The new server can't send, or isn't in your SPF record | Steps 4 and 5 |

## 1. Find out whether the email leaves the site

Before changing anything, find out which half is broken: WordPress sending the email, or the email reaching the inbox.

- **Send a test.** [Check & Log Email](https://wordpress.org/plugins/check-email/) (90,000+ active installs, updated 22 October 2026) sends a simple test email to an address you choose. WP Mail SMTP has a test email too.
- **Use WordPress itself.** Log out and request a password reset for your own account at `/wp-login.php?action=lostpassword`.
- **From the command line,** WP-CLI's [wp eval](https://developer.wordpress.org/cli/commands/eval/) runs one line of PHP and prints `bool(true)` or `bool(false)`:`wp eval 'var_dump( wp_mail( "you@example.com", "Test from WordPress", "It works." ) );'`
- **Turn on a mail log.** [WP Mail Logging](https://wordpress.org/plugins/wp-mail-logging/) (300,000+ active installs, updated 14 October 2026) records every outgoing email with its content and lets you resend one. FluentSMTP and Check & Log Email keep logs too.

Then read the result:

- **An error, or `bool(false)`:** WordPress couldn't hand the email over. The server's mail is off or broken, so go to step 4.
- **"Sent" or `bool(true)`, but nothing in the inbox or the spam folder:** the email left WordPress and was lost or rejected on the way. Steps 3 to 5 fix that.
- **It arrives in spam:** delivery works, trust doesn't. Steps 3 and 5.

## 2. Check the email is switched on and addressed correctly

If only some emails are missing, the notification itself may be the problem:

- **Admin notices** go to **Settings → General → Administration Email Address**. If you change it, WordPress emails the new address a confirmation link, and "the new address will not become active until confirmed". A typo there, or a change nobody confirmed, sends admin mail to the old address or nowhere.
- **Comment alerts** depend on **Settings → Discussion → Email me whenever**: "Anyone posts a comment" and "A comment is held for moderation".
- **Form notifications** are set in each form's own settings. Check the To address, and that the notification is switched on.
- **WooCommerce emails** each have their own switch; see the WooCommerce section below.
- **Critical error alerts** go to the admin address too. When a plugin or theme crashes the site, WordPress emails a recovery link, at most once a day by default. With broken mail that email never comes, which is one more reason to fix it now. Our [guide to the critical error](https://wpos.ai/blog/wordpress-critical-error/) explains what to do with the link.

## 3. Send from an address on your own domain

The From address decides which domain the inbox checks. Get it wrong and even a perfectly delivered email looks forged.

- **Use a real address on your site's domain,** such as `hello@yourdomain.com` or `notifications@yourdomain.com`, instead of WordPress's default `wordpress@yourdomain.com`, which often doesn't exist.
- **Never send as Gmail, Yahoo or Outlook.** [WooCommerce's email guide](https://woocommerce.com/document/email-faq/) warns that a @gmail.com or @yahoo.com From address "is likely to cause emails to land in spam folders or be blocked", because your server isn't allowed to send for those domains. Gmail also tells senders not to impersonate Gmail From: headers. The one exception is mail that really goes out through your Google account with an SMTP plugin.
- **Contact forms: put the visitor in Reply-To, not From.** A form that sends "from" the visitor's own address fails the same checks. Send from your domain and set Reply-To to the visitor, so pressing Reply still works.

SMTP plugins let you set the From name and address once for every email the site sends. Under the hood WordPress passes them through its `wp_mail_from` and `wp_mail_from_name` filters, so one setting covers core, form plugins and WooCommerce alike, unless a plugin sets its own.

## 4. Send through SMTP or an email service

This is the fix for most sites. An SMTP plugin takes over the last step of `wp_mail()`, usually through WordPress's `phpmailer_init` hook, and sends every email through a real mail service with a login instead of the server's `mail()`. All four below were tested with WordPress 7.1.4, according to their WordPress.org listings on 13 November 2026:

| Plugin | Active installs | Last updated | Good to know |
| --- | --- | --- | --- |
| [WP Mail SMTP](https://wordpress.org/plugins/wp-mail-smtp/) | 4,000,000+ | 11 Nov 2026 | Setup wizard and a test email; Gmail, Outlook, Amazon SES, Brevo or any SMTP server. The email log is in the paid Pro version. |
| [FluentSMTP](https://wordpress.org/plugins/fluent-smtp/) | 700,000+ | 4 Nov 2026 | Free, with an email log you can resend from, failure alerts and a fallback connection that takes over if the main one fails. |
| [Easy WP SMTP](https://wordpress.org/plugins/easy-wp-smtp/) | 500,000+ | 12 Aug 2026 | SMTP for Gmail, Office 365, Outlook or any server, with email logs. |
| [Post SMTP](https://wordpress.org/plugins/post-smtp/) | 300,000+ | 24 Sep 2026 | Email logs, alerts and a backup SMTP connection. |

Then choose what it sends through:

- **Your email provider's SMTP,** such as Google Workspace or Microsoft 365. Fine for a small site's notifications.
- **A transactional email service,** such as Amazon SES, SendGrid, Mailgun, Postmark or Brevo, built for website mail and usually connected with an API key. WooCommerce's guide notes that "an average site can usually stay within free usage".

Setting one up takes about ten minutes:

- Install the plugin and open its setup.
- Pick your mail service and enter its SMTP details or API key.
- Set the From name and a From address on your own domain (step 3).
- Send a test email, then trigger a real one, such as a password reset or a form entry.

**Use port 587 or 465, not 25.** Many servers block outgoing connections on port 25 because spammers abuse it. [Google Cloud](https://cloud.google.com/compute/docs/tutorials/sending-mail), for example, blocks port 25 to outside servers "due to the risk of abuse", while 587 and 465 stay open. If the plugin times out while connecting, check the port first.

## 5. Add SPF, DKIM and DMARC

These three DNS records tell inboxes that the service sending your mail is allowed to send for your domain. Gmail requires SPF or DKIM from every sender, and SPF, DKIM and DMARC, with the From domain aligned, from anyone sending more than 5,000 messages a day to Gmail accounts. Yahoo's rules match.

- **SPF** lists the servers allowed to send for your domain; your mail service tells you what to add, usually an `include:`. Keep **one** SPF record and add each service to it: under the SPF standard (RFC 7208) two SPF records make the check fail, and so do more than 10 lookups.
- **DKIM** signs each message with a key published in your DNS. The mail service generates it; Google asks for keys of at least 1024 bits and recommends 2048.
- **DMARC** tells inboxes what to do with mail that fails SPF and DKIM, and can send you reports. Gmail accepts a starting policy of `none`:

`_dmarc.yourdomain.com TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com"`Add the records where your domain's DNS is managed (often your domain registrar or your host), give them time to update, then send another test. Most mail services have a verify button that checks the records for you.

## WooCommerce order emails not sending

WooCommerce sends its emails through the same `wp_mail()`, so everything above applies. Two checks are WooCommerce's own, from its [email FAQ](https://woocommerce.com/document/email-faq/):

- **Is the email switched on?** Go to **WooCommerce → Settings → Emails**, open the email (for example, Processing order) and make sure **Enable this email notification** is ticked. Order emails also depend on the order reaching that status: a paid order stuck in Pending payment is a payment gateway problem, not an email one.
- **Did WooCommerce try to send it?** Go to **WooCommerce → Status → Logs** and open the source `transactional-emails`. Each attempt is listed as Sent (handed to the mail system), Failed (with the reason), Disabled or Skipped, and sent or failed order emails are also added to the order as private notes.

If the log says Sent but the customer got nothing, it's a delivery problem: steps 3 to 5. WordPress's own emails, such as password resets, aren't in that log; use a mail log plugin for those. For order emails that carry tracking numbers, see our guide to [shipment tracking emails](https://wpos.ai/blog/woocommerce-shipment-tracking-email/).

## Still not arriving?

- **Ask your host two questions:** is PHP's mail function enabled on my plan, and are outgoing connections on ports 587 and 465 allowed?
- **Read the error in the mail log.** A rejection that mentions 5.7.26 is Gmail refusing unauthenticated mail, so go back to step 5.
- **Watch your spam rate** if you also send newsletters from the same domain. Gmail and Yahoo both ask senders to keep reported spam below 0.3%.
- **Test again after every move or DNS change.** A new host is the most common way working email breaks: the new server isn't in your SPF record, or the old SMTP settings didn't come along.

## Where WPOS fits

**WPOS can't make an inbox accept your mail; DNS records and the mail service do that.** Where it helps is the checking. WPOS puts an AI agent inside wp-admin on the sites you already run, on any host, and it checks its own work before it reports a change as done. An email check across a site becomes one request:

> “List every plugin on this site that sends email and the From address each one uses, tell me whether mail goes through an SMTP plugin or the server's own mail, and send a test email to me@example.com.”

WPOS is our product, so weigh this section accordingly; you can [try it free for 30 days](https://app.wpos.ai/signup?ref_page=wordpress-not-sending-emails&ref_cta=body-cta) with 5,000 credits, a live site plus a staging sandbox, and no card.

## Frequently Asked Questions

**Why is WordPress not sending emails?**

By default WordPress hands every email to PHP's mail() function on your hosting server, with no login and a wordpress@ sender address. If the host blocks or limits that, or Gmail and Yahoo can't verify the sender, the email never arrives or lands in spam. Sending through SMTP or an email service, with SPF and DKIM set up, fixes most cases.

**How do I test whether WordPress can send email?**

Send a test with a plugin such as Check & Log Email or WP Mail SMTP, or request a password reset for your own account. With WP-CLI, wp eval and a one-line wp_mail() call prints true if WordPress handed the email over. True doesn't prove it arrived, so check the inbox and the spam folder too.

**Do I need an SMTP plugin for WordPress?**

On most hosts, yes. WordPress has no SMTP settings of its own, so a plugin is the usual way to send through a real mail service with a login and proper authentication. Some managed hosts relay mail for you; ask yours before you add one.

**Why do my WordPress emails go to spam?**

Usually because the message isn't authenticated for the domain in its From address, or the From address is on another domain such as gmail.com. Send from an address on your own domain through an SMTP or email service, and add SPF, DKIM and DMARC records for that domain.

**Why are WooCommerce order emails not sending?**

Check WooCommerce > Settings > Emails that the email is enabled, then WooCommerce > Status > Logs, source transactional-emails. Sent means WooCommerce handed the email to WordPress, so the problem is delivery; Failed includes the reason; Disabled and Skipped tell you what to switch on or fill in.

**Can I use my Gmail address as the From address?**

Not for mail your website server sends. Your server isn't allowed to send for gmail.com, so the message fails the checks inboxes run and lands in spam or is blocked. Use an address on your site's domain and set Reply-To to your Gmail. The exception is mail actually sent through your Google account with an SMTP plugin.

**Black Friday**ends Nov 30

## Start free with 15,000 credits.

Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.

## Know every email your site sends arrives.

WPOS puts an AI agent inside wp-admin on the sites you already run, on any host, and it checks its own work. Free for 30 days: 5,000 credits, a live site plus a sandbox, no card.

[Claim 15,000 credits](https://app.wpos.ai/signup?ref_page=wordpress-not-sending-emails&ref_cta=prefooter-cta): Start free
