SPF, DKIM and DMARC: the one-hour inbox build
Bulk mail without SPF, DKIM and DMARC now bounces at Gmail, Yahoo and Outlook. Publish the three records and one-click unsubscribe in about an hour.

This sheet contains partner links. A purchase through one earns Runbook a commission at no additional cost to you. How we make money.
If your newsletters or follow-up emails quietly stopped getting replies, there is a decent chance they stopped arriving at all. Gmail, Yahoo and Outlook now bounce mail from senders who have not proven who they are, and the proof is three settings on your domain, not better writing. By the end of this build your emails carry that proof, your unsubscribe works in one tap, and a free monitor warns you before trouble. The stack is your domain settings, your email platform, and one free Google tool. Setup runs about an hour.
The rules changed under you. Gmail and Yahoo set hard sender requirements in February 2024, Microsoft added its own for Outlook in May 2025, and through late 2025 all three moved from "we will put you in spam" to "we will reject you outright."
What you'll build
- Three DNS records that prove your email is really from you. DNS records are settings attached to your domain name, like entries in a public phone book that inbox providers check.
- One-click unsubscribe that processes opt-outs automatically.
- A clean, engaged list and a reputation monitor so you catch trouble early.
The three records, in plain words: SPF is the public list of who is allowed to send email for your domain. DKIM is a digital signature proving nobody tampered with the message. DMARC is your instruction to inbox providers on what to do with mail that fails those checks. Gmail and Yahoo require all three for bulk senders, defined as anyone sending more than 5,000 messages a day to their users. (Google's sender guidelines and the Yahoo Sender Hub both spell it out.) Microsoft brought in the same for Outlook in May 2025. One-click unsubscribe is required on marketing mail, opt-outs must be honored within two days, and your spam complaint rate must stay under 0.3%, ideally under 0.1%. Through November 2025 the providers escalated from spam-foldering to permanent rejection, meaning the email bounces back and is never delivered. (Proofpoint tracked the escalation.)
Stack
- Your domain's DNS panel: the settings page wherever you bought the domain (GoDaddy, Namecheap, and so on).
- An email platform that generates the DKIM signature and adds one-click unsubscribe for you. Kit handles this for newsletters. GoHighLevel does it for automated follow-up tied to a CRM.
- Google Postmaster Tools, free, to watch how Gmail rates your sending reputation.
- For cold outreach, a sender that warms new domains gradually, such as Instantly.
The stack
Steps
Wire the records once and they sit there doing their job unattended. Everything after that first hour is two small habits.
The build, in order
Publish the three records
p=none, which means "just report, block nothing") so no legitimate mail breaks, confirm your mail passes, then tighten later. In most email tools this lives under Settings then Sending domain or Authentication.Turn on one-click unsubscribe
Clean the list so only people who asked get mail
Wire up the reputation monitor
Your move this week
The part that breaks
The quieter failure is reputation. Every message marked as spam teaches the providers to trust your domain less, and that follows your domain into every future send. A botched newsletter blast can poison your one-to-one replies to prospects. The same discipline pays off in any lead-to-CRM automation flow, where inbox placement decides whether the rest of the pipeline ever runs.
The third trap is the complaint cap. At 0.1% you can afford one complaint per thousand emails. One send to people who never really wanted you can torch a domain you spent months building trust on.
Copy this
Publish this DMARC record first, at the gentlest setting, with reports sent to you so you can confirm everything passes before tightening:
Host: _dmarc.yourdomain.com
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com; fo=1
Leave it at p=none for a few weeks, read the reports, fix any source that fails, then change p=none to p=quarantine.
Upgrade path
Once authentication and unsubscribe are clean:
- For cold outreach, receiving servers still expect the records, and a poisoned domain ruins everything. A sender like Instantly that warms the domain gradually and keeps volume sane is the safer route.
- Tie your follow-up to your CRM so a verified sending domain carries your automated sequences.
Email is the cheapest channel you actually own, which matters more as website traffic gets scarcer in the AI Overviews shift for small business. For where discovery is heading next, see how AI tools surface recommendations. The automation hub covers the rest of the follow-up picture.
Frequently asked questions
Which DNS record do I publish first: SPF, DKIM or DMARC?
Order matters less than the starting policy. Add the SPF record listing who sends for you, switch on DKIM signing with the keys your email platform generates, then publish DMARC at the gentlest setting, p=none, so nothing legitimate gets blocked while you confirm alignment. Tighten to p=quarantine only after a few clean weeks of reports.
Where do these settings live in my email platform?
Look under Settings, then Sending domain or Authentication. The platform generates the DKIM keys and usually shows the exact SPF and DMARC values to paste into your DNS panel, wherever you bought the domain. Kit does this for newsletters; GoHighLevel does it for CRM follow-up sending.
How long does the deliverability build take?
About an hour of actual work: publish the three records, confirm one-click unsubscribe is on, and connect Google Postmaster Tools. Then leave DMARC at p=none for a few weeks while the reports confirm every sending source passes, and tighten after.
Do I need this setup if I send under 5,000 emails a day?
Yes. The strict bulk rules trigger above 5,000 messages a day to Gmail or Yahoo addresses, but most receiving servers now expect SPF and DKIM from any sender, and complaint rates count at every volume. The records are the baseline for landing in an inbox at all.
About Runbook
AI tools and automation builds for marketers. What to use, how to wire it, and the workflow to copy this week. How we work
GET THE NEXT DISPATCH
Run the next build before your competitors read about it.
One short email when an AI tool or automation actually changes the work, with the build to copy.
No send unless there is a build worth running.
// keep_reading
Related builds

Zapier alternatives for automation in 2026
Zapier is easiest to start, but Make, n8n and GoHighLevel can be cheaper or cleaner for the right automation job.

Best CRM for automated lead follow-up in 2026
GoHighLevel wins for built-in speed-to-lead SMS and email. Three CRMs for lead follow-up automation, with pricing and the step that trips every builder.

Best AI automation tools for marketing teams in 2026
Make bills by credit, Zapier by task. Four automation tools marketing teams run, priced at real volume, with the job each handles and where each breaks.