Go to the Source
The documentation was always there. Google published it. You chose the LinkedIn cold mail gurus instead. That's not ignorance anymore — that's defiance. Dead letter.
Deliverability Case Study: "Go to the Source"
"Go to the Source" is the album's final judgment — a gospel elegy for the sender who had every resource available and chose none of them. The lyric is precise about the specific unofficial sources that lead senders astray: LinkedIn cold mail gurus promising scale, inbox-hacking forum participants bragging about "warming up boxes," and growth hackers whose advice produces short-term open rates and long-term domain graveyards. The official documentation existed the entire time. It is still there.
The Postmaster is a 10-track album based on Google's Top 10 Gmail Sender Issues — the official Gmail Help Center list of the most common sender violations. This track covers issue #10: Go to the source.Here is the technical breakdown of the deliverability concepts detailed in the song:
Verse 1: The Unofficial Source Problem
"You scrolled through the valley of the LinkedIn feed / Where the cold mail prophets planted their seed / They promised you scale, they sold you a lie / Just 'warm up the boxes' and watch the stats fly / And now your domain is a graveyard of ghosts"
- The Deliverability Context: "Warm up the boxes" refers to inbox rotation tools — software that simulates engagement signals by having pools of accounts exchange emails with each other — presented as a substitute for legitimate IP warmup and authentic engagement. These tools violate the Terms of Service of Gmail, Yahoo, and most major mailbox providers. Accounts and domains using inbox rotation at scale are identified and penalized. "Brag on their posts" describes the engagement-bait pattern common in deliverability influencer content: case studies and screenshots of open rates that are either short-term results, measurement artifacts from Apple Mail Privacy Protection (MPP) inflation, or produced by practices that don't scale or last.
- The Domain Graveyard: Domains used for high-volume cold email campaigns with rotation-based "warmup" typically have lifespans of weeks to months before complaint rates and blocklist listings make them unusable. The practice requires a constant pipeline of fresh domains — the "graveyard of ghosts" is what's left.
Chorus: The Documentation Was There
"The documentation was always there / But you chose the wilderness, you chose the snare / Go to the source, and meet your end / The best practices are your only friends"
- The Deliverability Context: Google's bulk sender requirements and Top 10 Gmail Sender Issues — the source material for this entire album — are publicly available, regularly updated, and authoritative. They cover authentication (SPF, DKIM, DMARC), one-click unsubscribe (RFC 8058), spam rate thresholds (0.1% warning, 0.3% blocking), and sending practices. Every rule The Postmaster enforces is documented in those pages. "The documentation was always there" is not rhetorical — it is literally true.
- Additional Official Sources: Beyond Google's documentation, M3AAWG (Messaging, Malware and Mobile Anti-Abuse Working Group) publishes comprehensive best practice guides covering authentication, list management, and sending infrastructure at m3aawg.org. Yahoo's Sender Hub, Microsoft's SNDS documentation, and each major provider's postmaster pages are equally authoritative for their respective platforms. None require a paid subscription or an influencer to access.
Outro: The Verdict Is a Citation
"Read our bulk sender requirements. / Accept the verdict. / Amen."
- The Deliverability Context: The outro quotes — almost verbatim — the tone of Google's official guidance. The album closes with The Postmaster citing his own documentation. It is not a threat; it is a citation. Every violation covered on this album is in that documentation. Going to the source means going to the pages linked in this song's notes, and reading them before the next send.
- "Dead Letter": A postal and legal term for undeliverable mail with no return address — mail that cannot be delivered and cannot be returned. A domain destroyed by deliverability violations is the email equivalent: it exists, but nothing it sends arrives anywhere.
Read the Official Google Documentation
Google's postmaster documentation is the authoritative reference for Gmail deliverability. It is publicly available and updated by the team that builds the filtering infrastructure.
- Google's Bulk Email Sender Guidelines: The complete requirements for high-volume senders to Gmail, including authentication requirements, unsubscribe requirements, and spam rate thresholds. Required reading for any sender over 5,000 emails per day.
- Top 10 Gmail Sender Issues: The source document for this album. Ten issues, documented concisely, with specific guidance for each.
- Google Postmaster Tools Help: Documentation on interpreting Postmaster Tools data — domain reputation tiers, spam rate methodology, authentication reporting.
Consult the Other Major Providers
Google is the largest but not the only inbox. Yahoo, Outlook, and Apple Mail have their own documentation and postmaster resources.
- Yahoo Sender Hub (senders.yahooinc.com): Yahoo's official deliverability documentation, Complaint Feedback Loop enrollment, and postmaster tools.
- Microsoft SNDS (Smart Network Data Services): Data on the reputation of IP addresses sending to Outlook.com and Hotmail. Free registration at microsoft.com/en-us/SNDS.
- Every major provider's postmaster page is worth bookmarking. They update their documentation when requirements change — following official sources is the only way to stay current.
Use Industry-Standard Resources
Beyond provider documentation, the email industry maintains authoritative resources that cover best practices in depth.
- M3AAWG (Messaging, Malware and Mobile Anti-Abuse Working Group) at m3aawg.org publishes best practice documents on authentication, list hygiene, sending infrastructure, and anti-abuse. Peer-reviewed by major ISPs and ESPs. Free to download.
- The Spamhaus Project (spamhaus.org): The most widely used blocklist service. Their website documents how listings occur and how to request delisting. Understanding Spamhaus is basic operational knowledge.
- RFC documents: SPF is RFC 7208. DKIM is RFC 6376. DMARC is RFC 7489. One-click unsubscribe is RFC 8058. The actual protocol specifications are public and precise. When any source contradicts the RFC, the RFC wins.
Identify and Avoid Unofficial Sources
The deliverability advice ecosystem includes a large amount of content that is platform-specific, outdated, monetized, or simply wrong.
- Inbox rotation and engagement simulation tools violate Gmail and Yahoo Terms of Service. Domains using them at scale are identified and penalized. This advice does not appear in official documentation because it is a violation, not a strategy.
- Outdated guidance is common in deliverability content. Gmail's bulk sender requirements changed significantly in February 2024 (one-click unsubscribe mandate). Content written before that date may not reflect current requirements.
- "Growth hacking" email advice optimizes for short-term metrics using practices — purchased lists, misleading subject lines, high frequency — that produce long-term reputation damage. The case studies rarely follow the domain past six months.
- Treat any advice that contradicts official provider documentation as suspect. The provider documentation is authoritative; everything else is interpretation, at best.
Conclusion
The official documentation is public, free, current, and written by the people who built the infrastructure. Every rule on The Postmaster's list is in that documentation. Reading it is not optional for anyone who sends mail at scale — it is the minimum due diligence required to understand what the rules actually are, rather than what someone on LinkedIn says they are.
Your Official Sources Checklist:- Google Bulk Email Sender Guidelines bookmarked and read.
- Google Postmaster Tools documentation reviewed for correct metric interpretation.
- Yahoo Sender Hub and Microsoft SNDS documentation consulted for non-Gmail deliverability.
- M3AAWG best practice documents downloaded and referenced for list hygiene and authentication.
- All inbox rotation or warmup tool claims cross-referenced against official provider Terms of Service before use.
Deliverability is a moving target. This content reflects our best understanding at time of writing — but RFCs get updated, ISP policies shift, and best practices evolve. Spot an error or outdated info? Let us know and we'll fix it.