Black FridayCyber Monday 2026
13Days
14Hrs
16Mins
30Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

WordPress Emails Going to Spam: SPF, DKIM and DMARC Explained

When WordPress emails land in spam, the cause is usually sender identity. Learn what SPF, DKIM and DMARC check and how to set them up in order.

wpallsolution 6 min read

When WordPress emails going to spam is your problem, the messages are sent, but the receiving provider does not trust them. Order emails, password resets and form notifications that land in a junk folder cost you customers and leads. The cause is usually sender identity: the From address, how the message leaves your server, and whether your domain proves that the message is really yours. This guide explains what SPF, DKIM and DMARC check in plain terms and the order in which to fix them.

Quick answer

Use a From address on your own domain, send through authenticated SMTP rather than plain PHP mail, and publish SPF, DKIM and DMARC records for your domain. Google’s sender guidelines say that all senders to Gmail must set up SPF or DKIM, and that bulk senders (5,000 or more messages a day) need SPF, DKIM and DMARC. Most small sites are not bulk senders, but the same authentication improves trust. These steps lower the chance of spam placement; they cannot guarantee inbox delivery.

How this guide was prepared: it is research-based. We used Google’s email sender guidelines and the IETF standards listed under Sources, checked on October 23, 2026. We did not test your domain, and each mail provider decides for itself what to do with a message.

What SPF, DKIM and DMARC do

  • SPF (RFC 7208) is a DNS record that lists the servers allowed to send mail for your domain. A receiver checks whether the sending server is on that list.
  • DKIM (RFC 6376) adds a digital signature to each message. The receiver verifies it with a public key published in your DNS, which shows the message was authorised by the domain and not changed on the way.
  • DMARC (RFC 7489) tells receivers what to do when SPF and DKIM fail for your domain, and where to send reports. It also needs the visible From domain to line up with the domain that passed SPF or DKIM.

Plain PHP mail from a web server often passes none of these for your domain, which is why it lands in spam so often.

The decision tree: what is missing?

Flowchart for WordPress emails going to spam: five questions about the From address, SMTP, SPF, DKIM and DMARC
Five questions show which sender check is missing.
  1. From address not on your domain? Use one that is (Step 1).
  2. Site sends through plain PHP mail? Use authenticated SMTP (Step 2).
  3. No SPF record for your sender? Add or fix it (Step 3).
  4. Messages not signed with DKIM? Turn it on (Step 4).
  5. No DMARC policy? Start with a monitoring policy (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
Form or order emails always in spamSender address or transport not trustedSteps 1 and 2
Spam only at some providersMissing SPF or DKIM for your domainSteps 3 and 4
Messages rejected with an authentication messageSPF or DKIM failing, or a strict DMARC policySteps 3 to 5
Email worked, then stopped after you changed providerOld SPF or DKIM records do not match the new senderSteps 3 and 4

5 steps to stop WordPress emails going to spam

Step 1: Use a From address on your own domain

Set the sender (the From name and email) of your WordPress emails, forms and shop to an address on your domain, such as support@yourdomain.com. A visitor’s address or a free mailbox as the From address looks forged to receivers. Put the visitor’s address in Reply-To instead. Our guide on Contact Form 7 not sending email shows this for forms, and WooCommerce emails not sending covers store emails.

Step 2: Send through authenticated SMTP

Connect WordPress to a mail service with a plugin or your host’s SMTP settings, so messages leave through a mail server that is set up to send for your domain. Use a real mailbox or a sending service, and keep passwords out of chat and email. Send a test message from the mail plugin and read the headers to see the results of SPF, DKIM and DMARC checks; most mail clients can show the original message.

Step 3: Publish or fix your SPF record

Your email provider or SMTP service shows the exact SPF value to add as a DNS TXT record for your domain. A domain should have one SPF record, so merge the entries instead of adding a second one. Wait for DNS to update and test again. Remove services you no longer use, and avoid copying records from random posts.

Step 4: Turn on DKIM

In your email or SMTP provider, enable DKIM for your domain and add the DNS records it gives you. Once the records are in place, messages are signed and receivers can verify them. Google’s guidelines list SPF or DKIM as a requirement for all senders and say bulk senders need both.

Step 5: Publish a DMARC policy and read the reports

Add a DMARC record for your domain, starting with a monitoring policy (p=none) and a report address, so you can see who is sending mail as your domain before you enforce anything. Google notes that for bulk senders the policy may be set to none. Move to a stricter policy later only after the reports show that all your legitimate mail passes.

Version and hosting differences

  • Each provider shows different record values, so use the ones your own provider gives you.
  • If your website host and your email host differ, SPF must include every service that sends for you.
  • Large mailing lists have extra rules; Google’s guidelines for bulk senders include one-click unsubscribe.

How to verify the fix

  • A test message shows SPF, DKIM and DMARC as passing in the original headers.
  • Test messages reach the inbox at more than one provider.
  • Your DMARC reports show your legitimate senders passing.

How to prevent it from happening again

  • Update SPF and DKIM when you change email providers or add a new sending service.
  • Do not use someone else’s address as the From address.
  • Check email delivery after major site or hosting changes; see what WordPress maintenance includes.

Frequently asked questions

Why do my WordPress emails go to spam?

Often because they are sent from a server not authorised for your domain, with a sender address that does not match. Fix the sender, send through SMTP and authenticate the domain.

Do I need SPF, DKIM and DMARC?

Google requires SPF or DKIM from all senders and all three from bulk senders. Setting up all three is good practice for any domain that sends email.

Will these records guarantee inbox delivery?

No. They improve trust, but providers also look at content, reputation and user behaviour.

Can I fix this with a plugin alone?

A mail plugin handles the sending, but SPF, DKIM and DMARC are DNS records that you or your provider must publish.

What to do next

Fix the sender, connect SMTP and publish the three records. If you would rather not edit DNS yourself, wpallsolution offers plugin support and WordPress maintenance packages. We cannot promise inbox placement.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us