Web Design

WordPress Not Sending Email: The Real Cause Behind SMTP Errors

7 min read

Password resets never arrive, order notifications vanish. The problem is not the plugin — it is the identity of the mail.

A customer places an order and you never get the notification. A member forgets their password and the reset email never arrives. You send an invoice and the other side says it never came. Behind all of these sits one technical fact: the mail your server sends cannot be verified.

This article is written so that a business owner with no email background can follow it. The goal is to understand where the problem comes from and to be able to ask for the right fix.

The Root of It: How Mail Gets Accepted

Sending mail on the internet is like a postal system where you can write any name you like on the envelope. Receiving servers therefore treat every message with suspicion and ask one question: "Did this really come from a server authorised to send on behalf of this domain?"

If the answer is "no" or "unknown", the message goes to spam or is silently rejected. The default sending method on WordPress sites produces exactly that "unknown": the site hands the message to the server's basic mail function with no authentication behind it.

Years ago this worked. Today Gmail, Outlook and corporate mail systems are far stricter about unauthenticated senders. So "it used to work and now it does not" is entirely normal — nothing broke on your site; the rules on the other side tightened.

Symptoms: Which Case Are You In?

  • Nothing sends at all: sending may be disabled on the server, or the plugin settings are wrong.
  • Some addresses receive, others do not: the classic authentication problem — strict corporate recipients reject, lenient ones accept.
  • It arrives but lands in spam: identity partially checks out but reputation is weak.
  • It works for a while and then stops: you may be hitting a sending limit; shared servers enforce hourly caps.
  • You see an "SMTP error": this is actually good news — at least the system is telling you what went wrong. Silent loss is worse.

The Right Fix: Authenticated Sending

The permanent fix is to have the site send mail through a real mailbox, logging in with a username and password. This is SMTP sending. The difference: mail now leaves a verified mailbox that belongs to the domain, not an unknown source.

Points to watch during setup:

  • The sender address must match the account you log in with. If they differ, receiving servers become suspicious again. This is the single most common setup mistake.
  • Never use the visitor's address as the sender; put it in reply-to only.
  • The password must not sit in plain text in a configuration file. Share a server backup and you have shared your mailbox password.
  • The connection must be encrypted, or your mailbox password travels across the network in the clear.

Three Records on the Domain Side

SMTP alone may not be enough. Three DNS records answer the official question of who may send on your domain's behalf:

  1. An authorisation record listing which servers may send for you.
  2. A signature record that digitally signs outgoing mail so recipients can confirm it was not altered in transit.
  3. A policy record telling receiving servers what to do when verification fails, and sending you reports.

Set up correctly, these visibly improve deliverability. Set up wrongly, they make things worse — a misconfigured policy record can cause your working mail to be rejected too. These settings should be tested, not guessed.

Outbound Mail Problems Happen to Everyone

We hit this on our own server: a provider was rejecting our mail in bulk because of a gap in the server's reverse verification. This is not a "bad hosting" issue — it is a configuration matter anyone can run into. What matters is monitoring outbound mail so the failure does not stay silent.

What You Can Try Yourself

  • Install an SMTP plugin and configure sending through a real mailbox
  • Send the test message to three addresses on three different providers (corporate, Gmail, Outlook)
  • Check spam folders too
  • If your server panel has a mail log, read the rejection messages — they usually state the reason plainly

When You Need a Professional

If SMTP is configured and mail still does not land, the issue has moved to the domain and server reputation layer. If your domain has previously been listed as a spam source, recovery takes a process. On an e-commerce site sending order and invoice mail this cannot be postponed: an order confirmation that never arrives turns directly into refunds and complaints.

We covered disappearing enquiries separately in our contact form article; the two problems often appear together.

Why Delivery Is Critical on E-Commerce Sites

On a brochure site an undelivered mail is annoying; on an e-commerce site it touches money directly. Consider the mail an order generates: order confirmation, payment notice, tracking number, returns information, password resets. When one fails to arrive, the result is a support ticket, a refund or a complaint.

Some of these also fall under information obligations. "We sent it but it did not arrive" does not protect a business in distance selling. Keeping a sending log is therefore a commercial requirement, not only a technical one.

A practical recommendation: send transactional mail (orders, passwords, invoices) and marketing mail through separate channels. When a bulk campaign damages your reputation score, order confirmations leaving the same channel start landing in spam too. Separation stops one from sinking the other.

Domain Reputation: The Invisible Score

Every domain carries a reputation built from the history of what it has sent. The score is invisible but it decides delivery. What lowers it:

  • Mailing purchased lists. Complaint rates rise fast and the domain gets flagged.
  • Bulk spam leaving a compromised site. This is usually the longest-lasting damage after an attack: the site gets cleaned but reputation takes months.
  • High bounce rates. Repeatedly mailing invalid addresses signals a sender who does not manage their list.
  • Sudden volume spikes. A domain that has sent five mails a day for years suddenly sending ten thousand looks suspicious.

Once reputation falls, recovery takes time and cannot be rushed. Prevention is always cheaper: list hygiene, separate channels and routine delivery checks.

What Would It Cost If We Fixed It?

You do not have to guess, and you do not have to ask us. Tick the items you need in the calculator on our site and the total appears instantly. No forms, no waiting for a quote.

Calculate your price in one minute →

Frequently Asked Questions

Let's Find the Right Solution for Your Business

Get a custom quote for your website, SEO or chatbot needs.

See what your project would cost — right now

Tick the items you need and the total is calculated instantly. No phone call, no waiting.

Calculate price