SPF, DKIM, DMARC for D2C: Why Emails Go to Spam (2026)
SPF, DKIM and DMARC for D2C brands on Brevo, Klaviyo or MoEngage. Why marketing emails go to spam, the Gmail and Yahoo rules, and a real DNS setup.

Updated October 2026.
Marketing emails go to spam for four reasons, in this order. The domain isn't authenticated with SPF, DKIM and DMARC, too many people mark the mail as spam, too few people open or click it, and the list is full of dead or cold addresses. Spam trigger words are rarely the problem. SPF, DKIM and DMARC fix the first reason, and since February 2024 Gmail and Yahoo require all three from anyone sending in bulk.
I've run email for D2C brands on CRM platforms, starting at Zymrat, and I fix delivery problems for a living, like the month we took a brand's WhatsApp delivery from 23% to 44%. Below is the setup I'd give any D2C brand on Brevo, Klaviyo, MoEngage or WebEngage, using my own domain as the worked example.
Why are my emails going to spam?
Mailbox providers decide where your email lands from two things. Can they prove the mail came from you, and do their users want it? Authentication answers the first. Complaints, opens, clicks, replies and deletes answer the second.
These are the usual suspects, from most to least common in my experience.
- No custom authentication. The brand sends from its ESP's shared setup, so mail is signed with the platform's domain, not the brand's.
- Spam complaints. Customers who don't remember signing up click "Report spam" instead of unsubscribe.
- Low engagement. Weekly blasts to the full list, where most people haven't opened in months.
- List hygiene. Imported or bought lists, old addresses, typos and spam traps.
- Sudden volume. A sale where a brand that sends twice a week suddenly sends daily to everyone.
SPF, DKIM and DMARC explained
These are three DNS records on your domain. Each one answers a different question for the receiving server.
| Record | What it checks | What it looks like |
|---|---|---|
| SPF | Is this server allowed to send for the bounce domain? | TXT on your domain, starts v=spf1 |
| DKIM | Was this message signed by the domain in its signature, and unchanged? | Public key in TXT or CNAME at selector._domainkey |
| DMARC | Does SPF or DKIM pass for the domain in the From line, and what if not? | TXT at _dmarc, starts v=DMARC1 |
The part most pages get wrong is alignment. SPF checks the bounce address (the return path), which your customer never sees. DKIM checks the domain in the signature. Neither one, on its own, checks the From address your customer reads.
DMARC closes that gap. A message passes DMARC only if SPF or DKIM passes and the domain it passed for matches the From domain. By default the match is relaxed, so a signature from mail.yourbrand.com aligns with a From address at yourbrand.com, because both share the same registered domain. One aligned pass is enough.
DMARC policy has three values, and only three. p=none means report but take no action, p=quarantine asks receivers to treat failing mail as suspicious (usually the spam folder), and p=reject asks them to refuse it. At least one page ranking for "dmarc" today lists "accept" as a policy. There's no such value.
Sources: RFC 7489 (DMARC, alignment and policy values) and RFC 9989, the May 2026 standard that replaced it and keeps the same three policies.
Gmail and Yahoo bulk sender requirements
Since February 2024, Gmail and Yahoo have published rules for bulk senders. Gmail defines a bulk sender as anyone who sends close to 5,000 or more messages to personal Gmail accounts in 24 hours, and once you hit that, you're treated as a bulk sender permanently. A D2C brand with a mid-sized list crosses that on its first sale email.
| Rule | Gmail | Yahoo |
|---|---|---|
| Authentication | Both SPF and DKIM | Both SPF and DKIM |
| DMARC | A record, at least p=none, aligned with SPF or DKIM |
At least p=none, and DMARC must pass |
| Spam rate | Below 0.1%, never 0.3% or higher | Below 0.3% |
| One-click unsubscribe | Required on marketing mail, HTTPS link in the header | Required on marketing mail, RFC 8058 POST method highly recommended |
| Honour unsubscribes | Within 48 hours recommended | Within 2 days |
Gmail says it began ramping up enforcement on non-compliant mail in November 2025, with rejections or the spam folder for mail that fails. Transactional mail, like order confirmations, doesn't need the one-click header. A plain unsubscribe link in your footer doesn't count as one-click on its own.
Compare that with US law. The CAN-SPAM Act gives senders 10 business days to process an opt-out. Gmail and Yahoo want it done in two. The mailbox providers' rules are the ones that decide whether you reach the inbox.
Sources: Google's email sender guidelines FAQ, Yahoo's sender best practices, RFC 8058 (one-click unsubscribe) and the FTC's CAN-SPAM compliance guide, all checked October 2026.
A real SPF, DKIM and DMARC setup, line by line
Here's what's live on compoundlab.in, my own domain, as of 20 October 2026. I use Google Workspace for my inbox and Brevo for marketing email.
| Record | Value on compoundlab.in |
|---|---|
| MX | |
| SPF | v=spf1 include:_spf.google.com -all |
| DKIM | Two Brevo keys, as CNAMEs at brevo1._domainkey and brevo2._domainkey |
| DMARC | v=DMARC1; p=quarantine; pct=100; rua= Cloudflare's DMARC reporting address |
Look at the SPF record. Brevo isn't in it, and it doesn't need to be. Brevo's own help page says SPF and MX records aren't required to authenticate a domain on its shared setup. On shared sending, the bounce address belongs to the platform, so SPF would pass for the platform's domain, not mine, and couldn't align anyway. DMARC passes through the DKIM signature, which is signed as compoundlab.in and matches my From address.
That matters because SPF has a hard ceiling. A receiver may follow at most 10 DNS lookups while checking SPF (each include, a, mx, ptr, exists and redirect counts), and past 10 the check returns a permanent error. Brands that paste in an include for every tool they've ever tried hit that limit and break SPF for everything. Google's include is one lookup. Mine has room to spare.
The -all at the end is a hard fail. Any server that isn't Google, sending with a compoundlab.in bounce address, fails SPF.
One more detail. pct=100 was a valid tag under RFC 7489. RFC 9989 retired pct and replaced its testing use with a t tag, and receivers ignore tags they don't recognise. Since 100 was always the default, my record behaves the same either way.
A note on where this comes from. At the brands I've worked with, the CRM platforms handled DNS. They gave us the records and the brand's tech team added them. compoundlab.in is the domain I set up myself, record by record, which is why it's the example here.
Sources: Brevo's help article on authenticating a domain, RFC 7208 section 4.6.4 (the SPF lookup limit) and RFC 9989 appendix A.6 (removal of pct).
DMARC setup for a D2C brand on an ESP, step by step
The steps are the same on Brevo, Klaviyo, MoEngage or WebEngage. The platform gives you the records. Your job is to add them in the right order and check they work.
- Set up custom DKIM on your own domain. In your ESP's domain settings, authenticate your sending domain and add the DKIM records it gives you. Until you do, your mail is signed with the platform's domain and won't align.
- Send from your own domain. Use a From address on the domain you authenticated, such as
hello@yourbrand.com, never a Gmail address. - Keep SPF short. Add an ESP's
includeonly if its documentation says you need one for your setup. Count your lookups and stay under 10. - Publish DMARC at
p=nonewith reports. Add aruaaddress so mailbox providers send you aggregate reports. This changes nothing about delivery. It shows you every service sending as your domain. - Read the reports for a few weeks. Look for legitimate senders that fail, such as a helpdesk or a review app, and set up DKIM for each.
- Move to
p=quarantine, thenp=reject. Once everything you send passes, tighten the policy. That stops anyone else spoofing your brand to your customers. - Check alignment on a real email. Send a campaign to your own Gmail, open the menu, choose "Show original" and look for DKIM and DMARC passing with your domain.
- Turn on one-click unsubscribe. Most ESPs add the header for you. Confirm it's there in "Show original" by looking for
List-Unsubscribe-Post. - Watch your spam rate in Google Postmaster Tools. Google tells bulk senders to use it. Verify your domain there and check the spam rate after every big send.
Email warm-up: send to your most engaged people first
Authentication gets you through the door. Engagement keeps you in the inbox. This is the part I'd spend the most time on.
At a D2C brand I worked with, we sent the same email on the same day to two groups. People who had opened before got roughly five times the open rate of people who hadn't, and a higher share of the emails were delivered at all. In a separate send, a cold imported list opened at a fraction of the main list's rate.
That's the warm-up principle. Mailbox providers watch how recipients react. Send to engaged people first and the reaction is good. Send to everyone at once and the dead addresses drag the whole send down.
This is how I'd run it on a new domain, a new ESP or a cold list.
- Start with recent buyers and recent openers. Use RFM segments to pick them.
- Widen in steps. Add the next-most-engaged group only after a send with low complaints and normal opens.
- Lead with your automations. Welcome series, cart and post-purchase emails go to people who just acted, so they are your best-engaged mail. My flows vs campaigns post covers why they also earn more.
- Bring a cold list in last, and in small batches.
One caveat on opens. Apple Mail Privacy Protection has inflated open rates since 2021, so judge engagement on clicks where you can.
Email list cleaning and a sunset policy
At Zymrat, my first email job, non-openers were never removed from the list. We added WhatsApp around the same time, and every resend to non-openers recovered only a small slice of them.
A sunset policy fixes that. It's a rule for when someone stops getting your regular campaigns.
- Define inactive. For example, no open or click in 90 days and no order in that time.
- Send a short re-engagement series. Two or three emails asking if they still want to hear from you. My win-back campaigns post covers what to say.
- Move non-responders to a lower frequency, then stop sending.
- Reach them on another channel. A customer who ignores email may still read WhatsApp, if your WhatsApp delivery rate is healthy.
- Remove hard bounces immediately. Never import an old list without checking it first.
Festive season sends: ramp volume before the sale
Diwali is where I see D2C brands get burned. A brand that sends twice a week goes to daily sends to the full list, including people it hasn't emailed in a year. Complaints climb with the volume, and the sale email lands in spam in the one week it matters.
Ramp up in the weeks before the sale instead. Raise frequency slowly to your engaged segments, bring older segments back gradually, and keep the full-list blast for the one or two sends that justify it. Good subject lines help once you're in the inbox, and my ecommerce email subject lines post covers those. They won't get you out of spam.
Gmail Promotions tab vs spam
The Promotions tab isn't spam. It's a tab inside the inbox where Gmail sorts marketing mail. Authentication won't move you out of it, and you shouldn't try to disguise a sale email as a personal note to escape it. If your mail sits in Promotions, you're delivered. If it sits in spam, read the sections above.
Email deliverability myths
| Myth | What's true |
|---|---|
| Words like "free" or "sale" send you to spam | Gmail's and Yahoo's published rules cover authentication, complaints and unsubscribes. Neither lists banned words |
| SPF alone is enough | Gmail and Yahoo require both SPF and DKIM for bulk senders, plus DMARC |
| Every sending tool must be in SPF | Your ESP's DKIM can carry DMARC. Too many includes break SPF past 10 lookups |
p=none protects your domain |
It only reports. Spoofed mail still gets through until quarantine or reject |
| A bigger list means more revenue | Mailing people who never open hurts delivery for those who do |
Where I fit
Most delivery problems I see aren't technical once the records are in. They come from sending everything to everyone. Compound Lab is a retention agency, and deciding who gets which email, and when, is the job. Book a 30-minute call and we'll check your authentication, your spam rate and which segments are dragging your sends down.
FAQ
Why are my emails going to spam all of a sudden? A sudden drop usually follows a change. Common causes are a big jump in volume, a send to an old or imported list, a spike in spam complaints, or a broken DNS record, such as an SPF record that went past 10 lookups after a new tool was added.
How do I stop emails going to spam? Authenticate your domain with SPF, DKIM and DMARC, send from your own domain, add one-click unsubscribe, and keep spam complaints below 0.1% as Gmail asks. Then send to your most engaged subscribers first and stop mailing people who haven't opened or clicked in months.
How do I get mail in the inbox instead of spam? Mailbox providers reward mail that people open, click and reply to, and punish mail they report or ignore. Pass DMARC with an aligned DKIM signature, keep complaints low, and grow volume gradually from your engaged segments.
What is DMARC? DMARC is a DNS record that tells receiving mail servers how to treat email that claims to come from your domain but fails authentication. A message passes if SPF or DKIM passes for a domain that matches the From address, and the policy can be none, quarantine or reject.
Do I need SPF if I have DKIM? For bulk senders to Gmail and Yahoo, yes, because both require SPF and DKIM. For DMARC, one aligned pass is enough, and on most ESPs that pass comes from your DKIM signature, so you don't need to add every sending tool to your SPF record.
What is the DMARC policy p=none? p=none is monitoring mode. Receivers send you reports about mail using your domain but take no action on failures, so it's the right first step and the minimum Gmail and Yahoo accept, but it doesn't stop anyone spoofing your brand until you move to quarantine or reject.
Does DMARC need both SPF and DKIM? No. DMARC passes when either SPF or DKIM passes and is aligned with the domain in the From address. For marketing email sent through an ESP, aligned DKIM on your own domain is usually the one that does the work. Set up both anyway.
Is DMARC really necessary? For a brand sending marketing email at volume, yes. Gmail and Yahoo require a DMARC record from bulk senders, and without it anyone can send mail that appears to come from your domain.
How do I add DMARC to my email? Add a TXT record at _dmarc.yourdomain.com in your DNS, starting with v=DMARC1; p=none; and an address for aggregate reports. Read the reports for a few weeks, fix any tool that fails, then move to p=quarantine.
Sale emails landing in spam? Book a 30-minute call.