This month Gmail started rejecting a share of non-compliant bulk mail. Until now it sent warnings and temporary errors. If a client's campaign bounced this week with a 550 error, the cause is rarely a missing record. The client's domain almost certainly has an SPF record, and it often has DKIM too. The failures sit in alignment. They also sit in the tools that send as the client without anyone thinking of them, like the booking system's confirmations, the invoicing app's reminders and the newsletter account someone opened years ago and never closed.
The 2024 bulk sender requirements are easier to meet than they look, if you work in a fixed order. List the senders first. Then fix SPF, then DKIM, then DMARC alignment, then one-click unsubscribe, and leave complaint rates for last. Each step depends on the one before it, so this order means you never redo work. It's how you audit and repair every client domain in one afternoon. Complaint rates are the one item an afternoon can't fix, so for those your job today is to start measuring them.
Below you'll find each step with the records to publish, what you should see when it's done and the mistake that catches people at that point. At the end you'll have a pass or fail sheet you can reuse for every client you sign from now on.
By tonight every client domain will have a pass or fail sheet and a fix list
Your output today is one spreadsheet. Each client domain gets one row. Each row gets a pass or fail mark for SPF, DKIM, DMARC alignment, one-click unsubscribe and complaint monitoring, plus a short fix list for anything that failed. You'll send it to clients, keep it for renewals and fill in a new row every time you onboard someone.
| Domain | Senders found | SPF | DKIM aligned | DMARC | One-click unsub | Postmaster verified | Fix list |
|---|---|---|---|---|---|---|---|
| client-example.com | Email platform, booking, invoicing | Pass | Fail | Pass (p=none) | Pass | Yes | Custom DKIM in invoicing app |
| salon-example.co.uk | Email platform, old newsletter account | Fail | Pass | Missing | Fail | No | Merge SPF, publish DMARC, close old account |
Get these ready before you start, because a missing login is what turns an afternoon into a week.
- DNS login for every client domain, or a named client contact who can publish records today
- Admin access to every tool that sends as the client, not just your email platform
- A personal Gmail inbox and a Yahoo inbox for test sends
- A Google account you'll use for Postmaster Tools across all clients
- A mailbox or report service to receive DMARC aggregate reports
The 2024 bulk sender requirements are now being enforced with rejections, not warnings
Here's where things stand in the week of 13 April 2024. Gmail and Yahoo announced the 2024 bulk sender requirements in October 2023, and enforcement began on 1 February 2024. Through February and March Gmail mostly returned temporary errors on non-compliant mail. In April it moved to rejecting a share of that traffic outright. The one-click unsubscribe deadline is 1 June 2024, so you have seven weeks to get that part right.
Google defines a bulk sender as one sending close to 5,000 messages a day to personal Gmail accounts. That figure counts every message from the primary domain and its subdomains together. It isn't per sending tool. A client sending 3,000 campaign emails from the main domain and 2,500 from news.client-example.com counts as 5,500. Once a domain reaches that level, Google treats it as a bulk sender permanently, even if volume drops later.
| Requirement | All senders | Bulk senders |
|---|---|---|
| SPF or DKIM | Required | Both SPF and DKIM required |
| Valid forward and reverse DNS, TLS, RFC 5322 formatting | Required | Required |
| Spam rate in Postmaster Tools | Below 0.3% | Below 0.3%, aim for under 0.1% |
| DMARC | Recommended | Required, at least p=none |
| From domain aligned with SPF or DKIM | Recommended | Required |
| One-click unsubscribe on marketing mail | Not required | Required by 1 June 2024, opt-outs honoured within two days |
Small clients sending far below 5,000 a day still have obligations. SPF or DKIM is required of every sender, and so is a spam rate below 0.3%. Fix them anyway, because the full setup costs nothing extra and protects a client the day their list grows. The clients hit first this month are the high-volume ones with a shared DKIM signature or no DMARC record. Retail lists before a sale, membership organisations and anyone mailing a large, old list fall into that group.
Read more: How to Use Automated Domain Warmup to Ensure High Deliverability for New Clients
Step 1: List every service that sends as the client's domain before you touch DNS
Start with a conversation, not a DNS panel. Go through the client's tools and note every one that sends email with their domain in the From line. The usual suspects are the CRM, booking system, invoicing app, helpdesk, e-commerce store, your email platform and any old newsletter account still holding a list. Then check the evidence. If the domain already has a DMARC record, its aggregate reports name every IP and service that has sent as the domain. If it doesn't, open the headers of a few recent bounces and client emails and read the Return-Path and the DKIM d= value. Unfamiliar names there are senders nobody mentioned.
What you should see. A short, named list per domain, usually three to six services, each with a note on whether you have admin access to it.
Common mistake. Fixing the records for the email platform only. A week later the invoicing app's payment reminders start bouncing, and the client blames the change you made. If the old newsletter account still has a list in it, close it, or run that list through automated email list verification before anyone mails it again.
Step 2: Keep SPF to one record and under ten lookups
Look up the domain's current TXT records and find every one that starts with v=spf1. Merge the senders from Step 1 into a single record and end it with ~all, or -all if you're confident the list is complete.
dig TXT client-example.com +short
# One merged record
v=spf1 include:_spf.your-email-platform.example include:mail.booking-tool.example include:invoicing-app.example ~all
What you should see. One SPF record on the domain, and an SPF lookup checker reporting ten or fewer DNS lookups.
Common mistakes. Two SPF records on one domain make both fail, so receivers treat the domain as if it had none. A record ending in +all authorises the whole internet to send as your client. Stacking includes past the ten-lookup limit returns a permerror, which counts as a failure. Each include can trigger lookups of its own, so remove senders from Step 1 that are no longer in use.
There's a quirk to understand before Step 4. SPF checks the envelope sender, the Return-Path address, and on a hosted platform that's often the platform's own domain. Your client's SPF passes, but against a domain that isn't theirs, so it doesn't align. That's why DKIM usually carries alignment for platform mail. DNS changes typically show up within the record's TTL, often five minutes to an hour, so you can retest the same afternoon.
Step 3: Sign with DKIM on the client's own domain, not the platform's
In each sending tool on your list, open the domain authentication settings and set up custom DKIM so the d= value is the client's domain or a subdomain of it. The tool gives you selector records, usually CNAMEs, sometimes a TXT record with the public key. Publish them exactly as shown. Pick 2048-bit keys where the tool offers a choice.
s1._domainkey.client-example.com CNAME s1.dkim.your-email-platform.example
s2._domainkey.client-example.com CNAME s2.dkim.your-email-platform.example
What you should see. Each tool's verification screen showing the client's domain as authenticated, and a test email whose header reads d=client-example.com.
Common mistake. Leaving the default shared signing domain in place. The mail passes DKIM, signed by the tool's own domain, but it never aligns with the client's From address, so DMARC fails. This is the most common answer to the question of why DMARC fails when SPF and DKIM both say pass. Both checks passed for someone else's domain.
Step 4: Publish DMARC at p=none with reporting, then prove alignment
Add a TXT record at _dmarc on the client's domain. Point the rua tag at a mailbox or report service you actually read.
_dmarc.client-example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@your-agency.example"
Alignment is simpler than it sounds. The domain in the visible From line has to match the DKIM d= domain or the SPF envelope domain. Under relaxed alignment, which is the default, a subdomain counts as a match. So mail from hello@client-example.com signed with d=news.client-example.com aligns. That's why sending client marketing from a subdomain works well. It keeps campaign reputation apart from the main domain's day-to-day mail and still passes DMARC. Our guide to using secondary domains for high-volume client outbound covers how to set that split up.
What you should see. The record resolving when you look it up, and within 24 to 48 hours aggregate reports listing each source and whether it passed aligned.
Common mistakes. Treating a published record as proof of compliance, when only the reports show whether each sender aligns. Publishing a second DMARC record. Pointing rua at an inbox nobody opens. Jumping straight to p=reject before the reports are clean, which blocks the forgotten booking tool along with the spoofers.
Step 5: Add one-click unsubscribe headers and honour opt-outs within two days
Every marketing send needs two headers. One is List-Unsubscribe, carrying an https URL. The other is List-Unsubscribe-Post, which tells Gmail and Yahoo that a single POST request to that URL removes the subscriber, with no login and no confirmation page. That's the RFC 8058 method, and it's what the 1 June 2024 deadline asks for. Keep a visible unsubscribe link in the email body as well, because the header doesn't replace it. Then check how fast opt-outs take effect. Every removal has to be processed within two days.
List-Unsubscribe: <https://unsubscribe.client-example.com/u/8f3k2a>, <mailto:unsubscribe@client-example.com?subject=unsubscribe>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Receipts, booking confirmations, password resets and invoice reminders don't need the header. They're transactional, and the rule covers marketing mail only. So the booking tool you found in Step 1 needs SPF and DKIM, but it doesn't need one-click unsubscribe. The old newsletter account does, if it's still sending.
What you should see. An unsubscribe option beside the sender's name at the top of the message in Gmail and in Yahoo, and both headers present when you open the raw message.
Common mistake. Sending a mailto-only header, or pointing the URL at a preference centre that asks the subscriber to log in. Neither one counts as one-click. The other trap is opt-outs that never leave the tool they were made in. If someone unsubscribes from the client's newsletter while the CRM keeps mailing them, the client is breaking the rule and earning a spam complaint.
Step 6: Start measuring complaint rates today, because you cannot fix them today
An afternoon can't lower a complaint rate. All you can do today is start watching it. Add each client domain to Google Postmaster Tools using the Google account you set aside earlier. Google gives you a TXT record to publish at the root of the domain, and once it resolves, you click verify.
client-example.com. TXT "google-site-verification=Xq7...your-token"
The number that matters is the user-reported spam rate. Keep it below 0.3% and aim for under 0.1%. Under the 2024 bulk sender requirements, a domain that goes over 0.3% sees more of its mail sent to spam or rejected. It also loses Google's help with deliverability problems until the rate has stayed low for a sustained period. One complaint per 1,000 delivered messages is where you want each client to sit.
What you should see. A verified domain in Postmaster Tools. The dashboards fill in only once the domain sends enough daily volume to personal Gmail accounts, so a small client's blank screen is normal. It doesn't mean the setup is broken. Mark the column as verified and look again after their next big send.
Common mistake. Re-mailing an old list to test the new setup. Fresh DNS records don't make a three-year-old list safe to mail, and one send like that can push a domain over 0.3% in a day. The slower mistake is mailing non-openers forever. Build a segment of people who haven't opened in recent campaigns, send them less often, then stop. SendTo builds that segment from past campaign activity, verifies addresses before each send, and offers bot-protected signup forms with optional double opt-in, so fewer reluctant subscribers get onto the list in the first place.
The infrastructure checks most agencies can leave to their sending platform
A few rules apply to the servers, not to the client's DNS. Sending IPs need valid forward and reverse DNS, meaning a PTR record that resolves back to a hostname, which in turn resolves to the same IP. Mail has to travel over TLS. Messages have to follow RFC 5322 formatting, with one From header, a valid Message-ID and a proper Date. Bulk mail must never show a gmail.com address in the From line, because Gmail's own DMARC policy now quarantines it.
If your clients send through a hosted platform, your job is to confirm these, not to build them. Read one raw header and check that TLS appears in the Received lines. Then check that the client's From address uses their own domain, not a personal Gmail address. If you run your own mail servers, all of this is yours, along with IP reputation and blocklist monitoring. Our comparison of self-hosted mail servers and third-party infrastructure sets out what that ownership costs you.
SendTo handles this layer for its partners. It applies automated warmup to new sending domains and paces dispatch per provider and per domain. It also spreads campaign volume across several brand-matched sending domains, so no single domain carries the full load. That last part is explained in how multi-domain distribution shields client reputation. The platform still can't publish records in a client's DNS. You or the client's contact has to do that.
Read more: How Automated Domain Warmup Prevents New Email Accounts Sending to Spam
Check it worked with a test send, then read the headers and the reports
Send a real campaign, not a plain test message, to your Gmail and Yahoo inboxes. In Gmail, open the message, choose Show original from the three-dot menu, and read the summary at the top. You want three passes, each against the client's domain.
SPF: PASS with IP 203.0.113.25
DKIM: 'PASS' with domain news.client-example.com
DMARC: 'PASS'
List-Unsubscribe-Post: List-Unsubscribe=One-Click
In Yahoo, open the message, choose More, then View raw message, and find the Authentication-Results line. It should read spf=pass, dkim=pass with header.d set to the client's domain, and dmarc=pass. Check that both inboxes show the unsubscribe option beside the sender, keeping in mind the Gmail caveat from Step 5. Then send one message from every other tool on your Step 1 list, such as a booking confirmation or an invoice reminder, and read their headers the same way.
Over the next 48 hours, read the DMARC aggregate reports. Look for any source you don't recognise, and any source that passes SPF or DKIM but fails alignment. Each one is either a sender you missed in Step 1 or someone spoofing the client. Once the reports are in, fill in that domain's row on the pass or fail sheet.
If mail is still bouncing, match the error to the step that caused it
Each failure points back to one step. Fix that step, wait out the record's TTL, and send another test. Change one thing at a time, or you won't know which change fixed it.
| Symptom | Likely cause | Step to revisit |
|---|---|---|
| Gmail 550 5.7.26 bounce citing unauthenticated mail or DMARC policy | SPF or DKIM missing, or neither aligned with the From domain | Steps 2 to 4 |
| DKIM pass, DMARC fail | Tool still signing with its shared d= domain | Step 3 |
| SPF permerror | More than ten lookups, or two SPF records on the domain | Step 2 |
| No unsubscribe option shown, raw headers missing List-Unsubscribe-Post | Post header absent or URL not https | Step 5 |
| Spam rate rising in Postmaster Tools | Old or unengaged list, or sending too often | Step 6 |
| One tool bounces while campaigns deliver | Sender missed in the inventory | Step 1 |
If you still see a 550 after every row on the sheet passes, the problem is almost always a sender that never made the inventory. Go back to the DMARC reports and find which source is failing. You don't need to rebuild the records you've already confirmed.
With every row filled in, you have a compliance check you can repeat for each new client in under an hour. You also have a clear seven weeks to finish one-click unsubscribe before 1 June. If you write for agency owners who sell email marketing, this checklist is the kind of help that gets them to trust a platform recommendation. SendTo's affiliate programme pays you 20% of the partner subscription each agency you refer pays us, every month they pay it. Attribution lasts 90 days from the first click, the first touch wins, and commission is paid monthly by PayPal. For plan costs, see the pricing page.
Get a referral link and earn 20% of the partner subscription of every agency you refer to SendTo.
Join the SendTo affiliate programme


