Email marketing

How to Meet the Gmail and Yahoo Bulk Sender Rules Before Enforcement Tightens in April

From April, Gmail starts rejecting part of the bulk mail that breaks its rules. Here's a domain-by-domain audit you can run on every client this month, in the right order.

Email marketing
Photo by Mohamed_hassan

February 2024 was the warning. April is when the rules start to bite. Since 1 February, Gmail has answered noncompliant bulk mail by sending back temporary errors on a small share of it. From April, it starts rejecting a share of that mail outright, and Google has said the share will grow gradually. If you set up SPF once for each client a few years ago and haven't touched it since, the risk isn't in the marketing platform. It's in the domains and tools nobody has opened since: the CRM, the invoicing tool, the helpdesk, the newsletter subdomain from a 2019 rebrand.

The safe move is to audit every client domain this month, always in the same order. Inventory first, then SPF, then DKIM, then DMARC alignment, then one-click unsubscribe, then spam rate. Each check depends on the one before it, so doing them out of order means doing them twice. This article walks you through that order as a Gmail and Yahoo bulk sender requirements checklist you can run with free tools, written in the week of 17 March 2024.

Every step follows the same pattern. You get the action, what you should see when it's done, and the mistake people make at that point. DNS records and header lines are shown in code formatting so you can copy them.

By the end you will have a compliance sheet for every client domain, and you need four things before you start

What you'll finish with is one spreadsheet. Each row is a client sending domain. Each column is a requirement, marked pass or fail. When a client asks whether they're ready for the Gmail and Yahoo changes, you send them their row. When something breaks in May, you know which column to check first.

The compliance sheet, with one filled-in row for a client running three sending tools
Sending domainServices sending as itSPFDKIM (own d=)DMARCAlignmentOne-click unsubscribeSpam rate (7 days)
harbourbakery.co.ukEmail platform, ecommerce store, invoicingPassFail (invoicing)Pass, p=noneFail (invoicing)Pass0.04%
news.harbourbakery.co.ukOld newsletter toolFail (no record)FailInherits rootFailFailNo data

You need four things in place before you start. Gather them first, because chasing a DNS login halfway through an audit is how a one-hour job turns into a two-week one.

  • DNS access for each client domain, or the name of the person at the client who has it. Write down where the DNS is hosted, because it's often not where the website is.
  • A Google Postmaster Tools account, signed in with the Google account you'll use to verify each client domain.
  • One Gmail and one Yahoo test inbox that you control, used only for audit sends.
  • A list of every tool that sends mail for each client. Step 1 builds this, but start it now from your onboarding notes and invoices.

The Gmail and Yahoo bulk sender requirements checklist is short, and April is what makes it urgent

Here's the timeline as it stands on 17 March 2024. The requirements took effect on 1 February 2024. Gmail began enforcing gently, with temporary errors on a small percentage of noncompliant traffic, so senders saw the problem in their bounce logs without losing the mail. From April 2024, Gmail starts rejecting a percentage of noncompliant traffic, and that percentage rises gradually. One-click unsubscribe for bulk senders has a later deadline of 1 June 2024.

So the change in April is the step from delay to loss. A temporary error means the sending server retries and the message usually arrives late. A rejection means it doesn't arrive at all, and your client's campaign report shows a bounce where a sale should be.

A bulk sender is anyone close to 5,000 messages a day to personal Gmail accounts, and the label sticks

Google defines a bulk sender as one that sends close to 5,000 messages or more to personal Gmail accounts within 24 hours. Messages from the same primary domain count together, so a client's store, newsletter and CRM all add to one total. Once a domain reaches that level on a single day, it keeps bulk sender status. It doesn't lose it by sending less next month.

If your client sends 3,000 emails a day, they aren't a bulk sender yet. One Black Friday blast to a 20,000-person list can change that permanently, though. Yahoo publishes no exact figure. Treat every client with a list that could ever top 5,000 as a bulk sender and set them up now.

Some rules apply to everyone, and the rest apply to bulk senders

What Gmail and Yahoo ask of all senders compared with bulk senders, as of March 2024
RequirementAll sendersBulk senders
AuthenticationSPF or DKIMSPF and DKIM
DMARC recordNot requiredRequired, p=none or stronger
From domain aligned with SPF or DKIMNot requiredRequired
Valid forward and reverse DNS (PTR) on sending IPsRequiredRequired
TLS for transmissionRequiredRequired
Messages formatted to RFC 5322RequiredRequired
Spam rate in Postmaster ToolsUnder 0.3%Under 0.3%
One-click unsubscribe on marketing mailNot requiredRequired by 1 June 2024

Reverse DNS, TLS and message formatting are your email platform's job, not yours. You only own them if a client runs their own mail server, and our breakdown of self-hosted mail servers against third-party delivery covers why that's rarely worth it. Yahoo's rules line up with Gmail's on every point that matters for this audit. Both want authentication, DMARC, one-click unsubscribe honoured within two days, and a low complaint rate.

Step 1: List every service that sends as each client's domain, including the ones nobody remembers

Start with the inventory, because every later step depends on it. For each client, list every system that puts their domain in the From address. That means the email marketing platform, the CRM, the ecommerce store, the invoicing or accounting tool, the helpdesk, the booking tool and the website contact form. Ask the client too. Their bookkeeper may have connected an invoicing app last spring without telling anyone.

Check subdomains as well as the root. An old news. or mail. subdomain set up for a previous newsletter tool still carries the client's name, and Gmail measures it against the same rules. If you use separate sending subdomains on purpose, our guide to using secondary domains for client outbound explains how to set them up so they help reputation instead of hiding problems.

What you should see. One row per sending domain on your sheet, with every service that sends as it listed beside it. A typical small retailer ends up with three to six services on the root domain.

The common mistake. Auditing only the marketing platform. Bulk sender status attaches to the domain, so once a client qualifies, every message carrying that domain is measured against the bulk rules. That includes the invoicing tool's receipts. If it sends from the root domain without aligned authentication, it fails, and it adds to the noncompliant traffic Gmail starts rejecting in April. Yes, a client's CRM or invoicing tool can break compliance for their marketing mail. You won't catch every one by asking, which is why Step 4 sets up DMARC reports to show you what you missed.

Step 2: Publish one SPF record per domain that passes and stays under ten DNS lookups

SPF (Sender Policy Framework) is a TXT record that lists the servers allowed to send for a domain. Look up the current record with a free DNS lookup tool, or from a terminal with dig. Then merge every service from your Step 1 list into a single record and end it with ~all (soft fail for anything not listed) or -all (hard fail).

dig +short TXT harbourbakery.co.uk

harbourbakery.co.uk.  TXT  "v=spf1 include:_spf.google.com include:spf.yourplatform.example include:mail.invoicetool.example ~all"

What you should see. Exactly one TXT record starting with v=spf1, and a lookup count of ten or fewer when you run it through a free SPF checker. Each include, a, mx, exists and redirect counts as a lookup, and includes nested inside includes count too.

The common mistakes. There are three. First, two SPF records on one domain, which happens when a new tool's setup guide says "add this record" and someone does, next to the old one. Two v=spf1 records is a permanent error, and SPF fails for every message. Second, going over ten lookups, which also produces a permanent error. Remove includes for tools the client no longer uses before you reach for flattening services. Third, assuming SPF protects the From address your client's customers see. It doesn't. SPF checks the envelope domain, the Return-Path, which your sending platform often sets to its own domain. That's why SPF can pass and DMARC can still fail, and why alignment gets its own step.

Step 3: Sign with DKIM on the client's own domain, not the platform's shared one

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each message, and receiving servers check it against a public key in the sender's DNS. Each sending service generates its own keys. In each tool's domain or authentication settings, find the DKIM setup page and copy the records it gives you, usually one to three CNAME records or a single TXT record, into the client's DNS. Choose 2048-bit keys wherever the service offers them, because 1024-bit keys are the old minimum.

s1._domainkey.harbourbakery.co.uk.  CNAME  s1.dkim.yourplatform.example.
s2._domainkey.harbourbakery.co.uk.  CNAME  s2.dkim.yourplatform.example.

What you should see. Send a test from each service to your Gmail inbox, open the message, click the three-dot menu and choose Show original. In the Authentication-Results header you want a line like the one below, with d= set to the client's domain.

dkim=pass header.i=@harbourbakery.co.uk header.s=s1 header.b=Xk3f9aQ2

The d= value, shown in the header as header.i or header.d, tells you whose domain signed the message. That's the part that matters for the next step, not the word pass.

The common mistake. Shared-domain signing. Plenty of tools sign by default with their own domain until you set up custom authentication. The message shows dkim=pass, so it looks fine, but the signing domain is the platform's and not your client's. DMARC then has nothing on the client's domain to align with, so the message fails DMARC even though SPF and DKIM both pass. Check d= on a real send from every service on your Step 1 list, and mark the DKIM column as failed for any service where it doesn't match the client's domain.

Step 4: Publish DMARC at p=none, then confirm the From domain aligns with SPF or DKIM

DMARC (Domain-based Message Authentication, Reporting and Conformance) ties the last two steps together. It tells receiving servers what to do when a message fails, and it sends you daily reports on every server that used the domain. Add a TXT record at _dmarc on each client's root domain with a policy of none and a reporting address you actually read.

_dmarc.harbourbakery.co.uk  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@youragency.co.uk"

If the rua address sits on your agency's domain rather than the client's, your domain has to authorise it. Publish a TXT record at harbourbakery.co.uk._report._dmarc.youragency.co.uk with the value v=DMARC1. Without it, some receivers won't send the reports at all.

Alignment means the From domain matches the domain that passed

DMARC passes when SPF or DKIM passes and the domain that passed matches the visible From domain. Gmail and Yahoo accept relaxed alignment, which means a match on the organisational domain is enough. So mail from news.harbourbakery.co.uk, signed with d=harbourbakery.co.uk, aligns. Mail from harbourbakery.co.uk, signed with d=someplatform.com and with a Return-Path on the platform's domain, doesn't. That second case is how SPF and DKIM both pass while DMARC fails. Neither passing domain belongs to your client.

What you should see. dmarc=pass in the Authentication-Results header of a test message, and the first aggregate reports landing in the rua mailbox within a day or two. They arrive as zipped XML. A free DMARC report reader turns them into a list of sending sources, which is your Step 1 inventory checked by the receivers themselves.

Is p=none enough? For the Gmail and Yahoo rules, yes. p=none is the stated minimum. Move to p=quarantine later, once a few weeks of reports show every legitimate sender aligned, because it also stops strangers spoofing your client's domain.

The common mistakes. p=none with no rua tag meets the rule on paper and tells you nothing, so you never find the forgotten helpdesk. Jumping to p=reject before every sender aligns sends your client's own invoices to nowhere. And sending marketing mail From a gmail.com address through any platform fails outright, because Gmail publishes its own DMARC policy at quarantine. Every client needs a From address on a domain they own.

Step 5: Add one-click unsubscribe headers before 1 June and remove people within two days

One-click unsubscribe lets a recipient leave a list from Gmail's or Yahoo's own interface, without opening a web page. It runs on two headers defined in RFC 8058. Every marketing message needs both, plus a visible unsubscribe link in the body.

List-Unsubscribe: <https://unsub.harbourbakery.co.uk/u/8f3a2c>, <mailto:unsubscribe@harbourbakery.co.uk>
List-Unsubscribe-Post: List-Unsubscribe=One-Click

The HTTPS address has to accept a POST request and unsubscribe the person straight away, with no login and no confirmation page. RFC 8058 also expects both headers to be covered by the DKIM signature, so a header added after signing doesn't count. Most email platforms add these headers for you. Your job is to confirm they're there on every marketing tool from your Step 1 list, including the ecommerce store's built-in newsletter.

Is June the real deadline? It's the deadline for bulk senders, but Yahoo already expects the headers now, and you're already in each client's settings this month. Do it while you're there. Unsubscribes have to be processed within two days, so a weekly manual export from one tool into another doesn't meet the rule.

Receipts, password resets, booking confirmations and other transactional mail are exempt. The rule covers marketing and subscribed messages. A receipt with a discount code and a product carousel in it starts to look like marketing, though, so keep the two apart.

What you should see. An Unsubscribe option next to the sender name at the top of the message in Gmail. It often doesn't appear for new or low-volume senders, even when the headers are correct. That's normal, so check the raw headers instead of relying on the button.

The common mistakes. A mailto-only header, which doesn't count as one-click. An HTTPS link that opens a preferences page asking the person to sign in. And a body link that's been hidden in light grey at 8 point, which pushes annoyed readers to the spam button instead.

Step 6: Measure spam rate in Postmaster Tools and aim for 0.1%, because 0.3% is the cliff edge

The only spam rate Gmail uses is the one it shows you in Google Postmaster Tools. Add each client domain there and verify it with the TXT record Postmaster Tools gives you, then open the Spam rate dashboard.

What you should see. A daily user-reported spam rate, once the domain sends enough mail to personal Gmail accounts. Low-volume domains show no data at all. That isn't an error. Google only displays figures above a daily volume threshold, so a client sending 400 emails a week stays blank. For them, watch complaints in your platform and keep the list clean.

Read the number carefully. It's spam reports divided by mail delivered to the inbox, not all mail sent. A list that mostly lands in spam folders produces few reports, because people can't mark as spam what they never see, so a struggling client can show a reassuringly low figure. Cross-check against opens and clicks from real humans.

Why 0.1% when the rule says 0.3%? Because Google treats 0.3% as the point where delivery gets hit, and recovery takes weeks of clean sending. A small client sending 10,000 messages needs only 30 complaints to reach 0.3%. One send to a list that hasn't been mailed since 2022 does that easily. Run old lists through automated email list verification before they go anywhere near a campaign.

The common mistakes. Reading the platform's own complaint figure instead of Postmaster Tools. Platforms count complaints from feedback loops, and Gmail doesn't report individual complaints back the way Yahoo does, so the two numbers differ. Checking one day instead of a seven-day trend is the other one.

Check it worked by reading one test message's headers and one week of Postmaster data

You don't need a paid deliverability tool for this. A real send, Gmail's raw message view and Postmaster Tools cover every column on the sheet. Run this routine for each client domain.

  1. Send a real campaign, not a test template, from each sending service to your Gmail and Yahoo test inboxes.
  2. In Gmail, open the message, click the three-dot menu and choose Show original.
  3. Check the summary at the top for SPF PASS, DKIM PASS and DMARC PASS.
  4. In the raw headers, confirm the DKIM line shows d= on the client's domain.
  5. Find List-Unsubscribe and List-Unsubscribe-Post on every marketing message.
  6. Look for TLS in the Received headers, which confirms the message was encrypted in transit.
  7. After seven days, check Postmaster Tools for SPF, DKIM and DMARC authentication rates near 100% and a spam rate under 0.1%.
Authentication-Results: mx.google.com;
  dkim=pass header.i=@harbourbakery.co.uk;
  spf=pass smtp.mailfrom=bounce.harbourbakery.co.uk;
  dmarc=pass (p=NONE) header.from=harbourbakery.co.uk

Yahoo's raw view, under More then View raw message, shows the same Authentication-Results lines. Its rules match Gmail's on everything in this audit, so a pass in both inboxes means the row is done. Mark it pass, then move to the next domain.

If it did not, one of five failures is almost always the cause, and SendTo removes most of them for its partners

Failed rows nearly always trace back to the same five faults. Work down the list in this order, because it follows the audit order.

  • Duplicate SPF or too many lookups: Delete the second v=spf1 record and merge its includes into the first. Remove includes for tools the client has stopped using.
  • DKIM signed on the wrong d=: Open the tool's domain authentication settings and finish custom DKIM setup. Until the header shows the client's domain, it doesn't count.
  • An unaligned third-party sender in DMARC reports: Find the source IP's owner in the report, authenticate that tool on the client's domain, or move it to its own subdomain.
  • Missing List-Unsubscribe-Post: The tool sends a mailto-only header. Switch on one-click unsubscribe in its settings or move marketing sends to a platform that adds it.
  • One bad list driving the spam rate up: Stop sending to it, verify the addresses, and restart with the most engaged segment first.

On SendTo, most of that list never reaches you. Every address is verified before a campaign sends. New sending domains get automated warmup, the same process covered in our guide to automated domain warmup for new clients. Dispatch speeds are governed per provider and per domain, so Gmail and Yahoo never receive a client's whole list in one burst. Volume is spread across several brand-matched sending domains, which is how multi-domain distribution protects client reputation on large sends. Suppression applies across the whole platform, so an unsubscribe from one campaign holds everywhere. An AI reviewer checks subject lines, structure, language, links and basic compliance before launch.

Read more: How Artificial Intelligence Reviewers Standardize Email Quality Control Across Agency Teams

Here's what SendTo doesn't do. It can't fix the DNS for mail your clients send from other tools. The invoicing app, the helpdesk and the store's order emails still need their own SPF, DKIM and alignment in each client's DNS. That stays your job, and it's why Step 1 comes first.

Finish one client's row today, then do the rest before April. If you write for agency owners who'd rather sell results than manage sending infrastructure, SendTo's affiliate programme pays you 20% of the partner subscription every agency you refer pays us, every month they pay it. It's never a share of what that agency's clients pay the agency. Attribution lasts 90 days from the first click, the first touch wins, and commission is paid monthly by PayPal.

Refer agencies to SendTo and earn 20% of their partner subscription every month they pay it.

Join the SendTo affiliate programme

Frequently asked questions

Is my client a bulk sender if they send under 5,000 emails a day?

Not yet. But all mail from one primary domain counts together, and a single day close to 5,000 messages to personal Gmail accounts makes the status permanent. One Black Friday blast does it, so set up any client whose list could ever pass 5,000 now.

What changes in April that didn't happen in February?

February brought temporary errors on a small share of noncompliant mail, so messages retried and usually arrived late. From April, Gmail rejects a share of that mail outright, and the share grows over time. A delay becomes a lost message and a bounce in your client's report.

Is a DMARC policy of p=none enough?

Yes, for these rules. Bulk senders need a DMARC record at p=none or stronger, plus a From domain that aligns with SPF or DKIM. Start at p=none and use the reports to find senders you missed before you think about anything stricter.

Why does my mail fail DMARC when SPF and DKIM both pass?

Because DMARC checks whose domain passed. SPF often passes on the platform's Return-Path domain, and DKIM often signs with the platform's shared domain. If neither matches the From domain your client's customers see, alignment fails. Check the d= value in Show original.

Do I need one-click unsubscribe right now?

Bulk senders have until 1 June 2024 for one-click unsubscribe headers on marketing mail. Don't leave it to the last week, though. Gmail and Yahoo both expect unsubscribe requests to be honoured within two days, so your removal process has to work too, not just the header.

Why aim for a 0.1% spam rate when the limit is 0.3%?

0.3% is where delivery starts to suffer, and a small client can jump from 0.08% to 0.4% after one send to a stale list. Holding 0.1% gives you room to make that mistake once without crossing the line.

Can a client's CRM or invoicing tool break their compliance?

Yes. Bulk status sticks to the domain, so receipts from an invoicing tool sending as the root domain without aligned authentication count as noncompliant traffic. That's why Step 1 lists every service that sends, and why DMARC reports are there to catch what you missed.

What does my email platform handle, and what's left for me in DNS?

Reverse DNS, TLS and message formatting are the platform's job unless a client runs their own mail server. You still own the DNS side: one SPF record under ten lookups, DKIM on the client's own domain, and a DMARC record. Postmaster Tools and test inboxes are free for checking it.

Everything this blog teaches, on a platform with your name on it.

Email campaigns, websites, landing pages and print for your clients, made from a short brief and sent under your brand. Create your account and look around with a sample workspace loaded.

No contract · Cancel any time · Explore everything before you pay