Gmail sender rules: now enforced, not new
Drafted through my n8n + AI pipeline, edited by me.
Here is the 2026 update on Gmail and Yahoo: the sender rules have not changed since February 2024. What changed this year is enforcement. Gmail stopped tolerating partial setups, and a large share of senders are quietly losing mail to spam for reasons that are entirely preventable.
What Gmail sender rules still require
- SPF, DKIM, and DMARC authentication that passes and aligns.
- A spam-complaint rate under 0.10 percent, treated now as a hard line, not a goal.
- One-click unsubscribe on bulk mail, using the RFC 8058 header, not just a visible link.
The one most people still miss
The most under-implemented requirement is the one-click unsubscribe header. Teams add a visible 'unsubscribe' link and assume they are covered, but skip the List-Unsubscribe-Post header that Gmail actually checks for. Two years in, more than a third of commercial senders are still partially non-compliant, and that is enough to leak delivery to the spam folder.
What I'd check today
Diagram: mail from your domain is checked by SPF and DKIM, DMARC checks alignment, and the verdict routes the message to inbox or spam.
- Confirm SPF and DKIM both pass and align under DMARC, for every service that sends as you.
- Check that the List-Unsubscribe-Post header is actually present, not just an unsubscribe link.
- Watch your complaint rate in Google Postmaster Tools and clean the list before it spikes.
Bring me the workflow that sends your email, invoices, reminders, outreach, all of it, and I'll tell you which of these is quietly broken.
Building something this should run inside?
Book a callKeep reading
email
Why your email lands in spam, and the DNS fix most people skip
Why inboxes quietly filter small businesses now, and the exact order to fix it so your invoices, reminders, and outreach actually land.
google workspace
Fill with Gemini now cites its sources: what to check
Fill with Gemini can now show its web sources and fill 3,000 cells at once. Here is how to use it without trusting it blindly.
n8n
Your n8n 3.0 upgrade needs a migration check first
n8n 3.0 drops npm installs and several legacy nodes. Here is the n8n 3.0 upgrade checklist to run before your instance updates.
Stay in the loop
The occasional system worth stealing, automation notes and the odd offer. No spam, unsubscribe anytime.