---
title: Why WordPress emails land in spam, and how SPF, DKIM and DMARC fix it
description: Contact forms and order emails that vanish are usually an authentication problem. What Gmail, Yahoo and Outlook now require, and how to set up the three DNS records.
url: https://ironhelmsuite.com/blog/wordpress-email-spam-spf-dkim-dmarc/
---

# Why WordPress emails land in spam, and how SPF, DKIM and DMARC fix it

Contact forms and order emails that vanish are usually an authentication problem. What Gmail, Yahoo and Outlook now require, and how to set up the three DNS records.

Published 2026-07-01 in Email.

"The contact form stopped working" is one of the most common support requests we see. Almost every time, the form works fine. The email it sends is quietly going to spam, or being refused, because nothing proves the message really comes from the domain it claims.

## Why WordPress mail is suspicious by default

Out of the box, WordPress sends email with PHP's `mail()` function, through whatever mail server your web host runs. The message says it is from `wordpress@yourdomain.com` or from your contact form's address, but it leaves from a shared hosting server that your domain has never vouched for. To Gmail, that looks exactly like spoofing.

Three DNS records fix this, and since 2024 the large mailbox providers have stopped treating them as optional.

## The three records

**SPF** (RFC 7208) is a TXT record listing the servers allowed to send mail for your domain. The receiving server checks whether the message came from one of them.

**DKIM** (RFC 6376) adds a digital signature to each message. Your email service signs outgoing mail with a private key, and publishes the matching public key in DNS so receivers can check that the message was not altered and was authorised by the domain.

**DMARC** (RFC 7489) ties the two to the address people actually see. It tells receivers what to do when a message fails (nothing, quarantine or reject) and where to send reports. Crucially, DMARC requires *alignment*: the domain that passed SPF or DKIM must match the domain in the From address.

## What the big providers require now

In February 2024 Google and Yahoo started enforcing new rules. Every sender needs SPF or DKIM. Bulk senders, which Google defines as sending around 5,000 or more messages a day to Gmail addresses, need SPF, DKIM *and* DMARC, aligned with the From address, plus one-click unsubscribe on marketing mail and a spam complaint rate kept under 0.3 percent (Google recommends staying below 0.1).

Microsoft followed on 5 May 2025 for Outlook.com, Hotmail and Live addresses: domains sending more than 5,000 messages a day must pass SPF, DKIM and DMARC, or their mail is routed to Junk.

A small business site is nowhere near those volumes. It still benefits, because the same checks decide whether a single order confirmation looks trustworthy.

## Setting it up

1. **Send through a real email service** rather than the web server: your email host's SMTP, or a transactional service. They give you the SPF and DKIM records to publish.
2. **Publish SPF** with every service that sends for your domain in one record. A domain can have only one SPF record; two break both.
3. **Publish DKIM** using the selector and key your service provides.
4. **Start DMARC at monitoring**: `v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com`. Read the reports for a few weeks, fix anything legitimate that fails, then move to `quarantine`.
5. **Send a test to a Gmail address** and use "Show original" to see SPF, DKIM and DMARC results.

## In Ironhelm

Email delivery sends site email through a real email service, keeps a log of every message with its result, and checks your DNS for SPF, DKIM and DMARC, telling you exactly which record is missing. Notifications can tell you when an email fails, so a broken form does not go unnoticed for weeks.

## Sources

- IETF, [RFC 7208: Sender Policy Framework (SPF)](https://datatracker.ietf.org/doc/html/rfc7208)
- IETF, [RFC 6376: DomainKeys Identified Mail (DKIM) Signatures](https://datatracker.ietf.org/doc/html/rfc6376)
- IETF, [RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)](https://datatracker.ietf.org/doc/html/rfc7489)
- Google, [Email sender guidelines FAQ](https://support.google.com/a/answer/14229414)
- Microsoft Tech Community, [Strengthening email ecosystem: Outlook's new requirements for high-volume senders](https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730) (April 2025)
