---
title: "WordPress Email Not Sending: Fixes for Spam and Failures"
url: https://hostmy.blog/wordpress-email-not-sending/
date: 2026-11-04
modified: 2026-11-04
lang: en
author: "Aditya Sharma"
description: "When WordPress email is not sending, it is one of four things. How to tell which, test WordPress itself, check SPF, DKIM and DMARC, and fix the usual causes."
categories:
  - "WordPress"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2672-1024x538.jpg
word_count: 1304
---

# WordPress Email Not Sending: Fixes for Spam and Failures

When WordPress email is not sending, the cause is nearly always one of four things. WordPress never handed the message over, the server refused or dropped it, the receiving provider sent it to spam, or a form or plugin never asked for it. Knowing which of the four you have saves hours, because each has a different fix.

This post on WordPress email not sending is a way to find out which one you have, and then to fix the usual causes. It covers contact forms, password resets, order emails and newsletters sent from WordPress. It uses Google's published sender guidelines for the authentication rules, since Gmail is where most failures show up, and it assumes no server skills beyond running a few commands.

![Numbered outline of this post, WordPress Email Not Sending: Fixes for Spam and Failures: 1 First decide what kind of failure it is; 2 Why the default often fails; 3 The three records that prove you are who you say; 4 Check the plugin and the log; 5 Spam folders and reputation; 6 When the receiving end is the problem.](https://hostmy.blog/wp-content/uploads/2026/10/hmb-diagram-2672.png)The route through this post.

## First decide what kind of failure it is

| Symptom | What it usually means | Where to look first |
| ------- | --------------------- | ------------------- |
| No email arrives, and the form says it sent | WordPress handed it over and something dropped it | The mail method and the host's limits |
| The form says it failed | WordPress could not hand it over | A plugin conflict, or a blocked mail function |
| Email arrives in spam | It sent but authentication failed or looks suspicious | SPF, DKIM, DMARC, and the From address |
| Some arrive and some do not | Rate limits, or one provider rejecting you | Bounce messages and the provider's limits |
| Email arrives late | The server or provider queued it | Queue and provider status |
| Nothing is ever attempted | The form or plugin never triggered a send | The plugin's own settings |

The table matters because the usual advice, install an SMTP plugin, fixes only some rows. Check the symptom before you change anything.

## Test WordPress itself

The fastest test removes the form and the plugin from the picture and asks WordPress to send one message directly. This sends a test and prints whether WordPress accepted it.

`wp eval 'var_dump( wp_mail( "you@example.com", "Test", "This is a test." ) );'`

A result of true means WordPress handed the message to the mail system. It does not mean the message was delivered. If it prints false, WordPress itself could not send, and the cause is on the server or in a plugin that filters mail. If it prints true and nothing arrives, the message left WordPress and was lost or filtered afterwards, which points to the next layers.

## Why the default often fails

By default, WordPress sends mail through the server's own mail function, with no sign-in. Many hosts restrict or disable it to stop abuse, and even where it works, mail sent that way often lacks the authentication that receiving providers now expect. It is a weak default for a site that cares whether messages arrive.

The usual fix is to send through an authenticated service instead, with an SMTP plugin or a transactional email provider. The site then logs in to that service, which sends from servers with a good reputation and the right records. The details depend on the service you choose, and the point is the principle: the message should come from a source that proves it is allowed to send for your domain. This site also uses an SMTP plugin and not the host's default.

## The three records that prove you are who you say

To trust a message, the receiving provider checks records published in your domain's DNS. Google's [email sender guidelines](https://support.google.com/a/answer/81126) set the minimum for anyone sending to Gmail accounts. All senders must set up SPF or DKIM, use TLS, keep valid forward and reverse DNS records for their sending domains or addresses, and keep their spam rate in Postmaster Tools below 0.3 percent. The page recommends keeping it below 0.10 percent.

For bulk senders, defined as more than 5,000 messages a day to Gmail, the bar is higher. They need SPF, DKIM and DMARC. The domain in the From address must align with the SPF or DKIM domain. Marketing messages must support one-click unsubscribe and show a clear unsubscribe link. Most blogs are nowhere near that volume, but the same records help a small sender, and a newsletter that grows can cross the line.

These commands show what your domain publishes.

`dig +short TXT yourdomain.com
dig +short TXT _dmarc.yourdomain.com
dig +short TXT yourselector._domainkey.yourdomain.com`

The first should include a record starting with v=spf1, which lists who may send for you. The second should return a DMARC record if you have one. The third shows the DKIM key for a given selector, and your mail service tells you which selector it uses. Google also says DKIM keys should be at least 1,024 bits, and recommends 2,048 bits if your provider supports it.

## Match the From address to the sender

A common mistake is sending from an address at a domain the sending service does not control. A form that sends as your own address while the mail goes out through a different service fails the alignment check, and many providers then treat it as suspicious. Make the From address use your own domain, and configure the service to send for that domain, with its records in place.

## Check the plugin and the log

A contact form plugin may send through its own settings, ignoring your SMTP plugin, or may have a notification turned off. Open the form's notification settings and check the recipient, the From address and whether it is enabled. A mail log plugin shows each message, its status and any error from the server, which turns guesswork into reading. If your host provides a mail log in the control panel, read that too, because it shows the final answer from the receiving side.

## Spam folders and reputation

If messages arrive in spam, the cause is usually authentication or content. Check the records above first. Then look at what you send: a message with only an image, or with a link to a domain that has a bad reputation, scores worse. A new sending address also starts without a reputation, so volume should start small. The WordPress.org hacked-site guide adds a warning worth knowing: a compromised site can be abused to send spam, which gets its address blacklisted and breaks your real mail too. If mail stopped suddenly, [WordPress malware redirect: first-hour steps for spam hacks](/wordpress-malware-redirect-fix/) is worth a look.

## Test, then keep testing

`1. Send a test with wp_mail and read the result.
2. Send to two providers, such as Gmail and your own domain.
3. Check SPF, DKIM and DMARC with dig.
4. Check the From address matches the sending service.
5. Read the mail log for errors and bounces.
6. Submit each form once a month and confirm the message arrives.`

The last step is the one that prevents the next failure. Contact forms break silently, and nobody tells you. [What breaks on a WordPress site when nobody is watching](/what-breaks-when-nobody-is-watching/) lists forms among the things that go wrong without an error. [What to actually monitor on a WordPress site](/wordpress-monitoring/) shows what to check.

## When the receiving end is the problem

Sometimes your records are right and the message still goes astray. A recipient's own filter, a company mail gateway or a full mailbox can reject mail that passes every authentication check. If only one recipient is affected, ask them to check their spam folder and any quarantine, and to add your address to their safe list. If many recipients are affected, the cause is on your side.

Last checked in October 2026 against Google's email sender guidelines. Mailbox providers change their rules, so check the current guidelines for the providers your readers use.

## Where Host My Blog fits

Email delivery is one of the checks we run before taking on a blog, since a site that cannot send mail is losing messages without knowing it. If you would rather have someone confirm that your forms and resets arrive, [our care for bloggers](/for-bloggers/) includes it.

If you filled in your own contact form right now, would you be sure the message reaches you?