Posted October 12, 2026
Email Horror Stories, part 2 of 3
A cold sender that suddenly sends big looks exactly like the thing the filters were built to catch.
Last week was about the dead addresses on your list. This week is about the sender. Picture a domain or IP with no history that goes from a trickle to a flood overnight because someone senior decided the deadline was tonight. A mailbox provider can't tell that apart from a spammer who just bought a new domain.
I'm skipping the warm-up how-to, since you've read it already. What follows is what providers do when the spike lands, and which numbers decide whether you come out the other side.
The creature awakens
Google's sender guidelines already say what they expect from a new sender: start with a low sending volume to engaged users, increase it slowly, and avoid sudden volume spikes (Google email sender guidelines). They don't say how slowly, or for how long. No schedule appears on that page, so "slowly" is whatever the filter decides it means.
Validity reports that providers act on this directly. Its 2026 report says mailbox providers reject senders who suddenly increase volume, partly because their systems can't absorb the surge, and that rejections spiked over the holiday season as senders pushed volume to hit revenue goals (Validity 2026 Benchmark Report). The report's example is holiday retail. Political fundraising has the same problem on a tighter calendar.
The numbers that bite
Google asks bulk senders (more than 5,000 messages a day to Gmail accounts) to keep user-reported spam rates below 0.1% and to avoid ever reaching 0.3% (Google email sender guidelines). The rate is calculated daily. Cross 0.3% and you lose eligibility for mitigation support until the rate stays below 0.3% for seven consecutive days (Google FAQ).
Yahoo's line is 0.3% (Yahoo sender best practices). Validity puts the average complaint rate at 0.06% and says under 0.1% is now the expectation (Validity). That makes 0.3% the cliff edge, and healthy senders sit nowhere near it. If you're testing it, you're the outlier.
Programs built for campaigns use the same number. Gmail's verified sender program measures a 14-day average spam rate against 0.3%, and a violation costs you a seven-day suspension or permanent removal (Gmail Verified Sender Program policies). Verified or not, the line doesn't move.
Three mailbox providers, three moods
Gmail first. Google says it has been ramping up enforcement since November 2025, and that non-compliant messages face disruptions including temporary and permanent rejections (Google FAQ). Depending on the violation, you may get spam foldering instead.
Yahoo uses the same 0.3% ceiling, and bulk senders also need one-click unsubscribe and two-day unsubscribe handling (Yahoo). Its page says nothing about volume spikes, so that gap is yours to manage.
Microsoft wants SPF, DKIM and DMARC (at least p=none) from anyone sending 5,000 or more messages a day to Outlook.com consumer addresses. It began routing non-compliant mail to Junk on 5 May 2025 and said rejections would follow on a date to be announced (Microsoft Tech Community). The reject code is 550 5.7.515.
You can fail without ever seeing a block. Junk and spam foldering look like low engagement on a dashboard, and a team already behind on a deadline will read them that way.
The deferral zone
Gmail's 421 4.7.28 means it has detected an unusual rate of email from your IP address, netblock or domain and has temporarily rate limited it. Google's error page points you to its bulk sender guidelines and little else (Gmail SMTP errors and codes). It says nothing about ramping volume, which is a bit like a hospital sign that says "do not be sick."
Treat a 421 as a verdict. Before the next big send, check how your sending platform handles deferrals, so you know what it does with the queue when Gmail starts pushing back.
Deadline-night possession
Political and nonprofit programs spike on purpose. An end-of-quarter push, an election-eve appeal and a breaking-news ask all land on the same infrastructure that sent a few thousand messages last Tuesday. The senders most likely to be cold are often the ones told to send to everyone tonight.
The thresholds don't care why. A new domain with no history and a sudden jump looks the same whether it belongs to a PAC or a pill spammer. What you can control is who you send to first and how many complaints you collect. Keep complaints well under 0.1%, which is much easier before the spike than during it.
Composite scenario: the deadline night
Composite scenario. No real organization or person is depicted. A new 501(c)(4) registers a fresh sending domain in August. An end-of-quarter deadline is coming, and leadership wants "the whole file, tonight."
What went wrong:
- Early in the week: the domain sends about 4,000 messages a day.
- Deadline night: 700,000 messages go out in two hours.
- Hour one: Gmail returns 421 4.7.28 deferrals.
- Hour two: retries stack up and complaints on the Gmail slice reach 0.4%.
- Next morning: the team learns it is ineligible for mitigation support.
How it should have gone: decide the volume and segment plan weeks ahead, not on deadline night. Send engaged segments first. Watch Postmaster Tools while the send is running, and agree a stop rule at 0.1% complaints before anyone is tired. Have a plan for the rest of the file that does not require it all to go out at once.
Don't be this sender
- Your biggest send of the quarter is also your first big send.
- You don't know your Postmaster Tools spam rate today.
- Your sending platform retries deferrals as fast as it can.
- Leadership sets the volume the night before.
- You have no stop rule for complaints.
Plan the spike while it's still a calendar entry.
Next week: night of the living unsubscribes.
