What is Email Throttling and How to Avoid It in 2026? (Email Senders Guide)

Your cold emails show “delivered” in your sending tool. But open rates are dropping, replies have dried up, and you can’t figure out why.

The problem isn’t your copy. It’s email throttling. And for cold emailers, it works differently than most guides tell you.

I run TrulyInbox, an email warm-up tool. I’ve seen thousands of inboxes get throttled and thousands avoid it.

This guide is based on what I’ve observed firsthand, not recycled ESP documentation.

Here’s what we’ll cover:

• what throttling is
• what it looks like in your bounce logs
• why cold emailers face a different escalation path than marketers
• and how proper warm-up prevents it.

TL;DR: What Cold Emailers Need to Know About Throttling

Email throttling is when mailbox providers like Gmail, Outlook, Yahoo, etc., limit the number of emails you send.

For marketers, throttling is volume-driven. ISPs limit how many emails per hour from a given IP.

It’s loud: you get 421 deferral codes immediately. And it’s recoverable. Swap the IP, warm a new one, move on.

For cold emailers, throttling is behavior-driven.

ISPs evaluate engagement patterns, complaint rates, and content at the domain level, not the IP level. It starts silently. Emails land in spam with no error codes.

Your sending tool still says “delivered.” By the time you notice, your domain reputation is already damaged.

Here’s what you need to know upfront:

• The safe cold email limit is 50 emails/day per inbox on shared infrastructure (Google Workspace, Microsoft 365). Up to 100/day on private infrastructure with dedicated IPs.
• Proper warm-up over 4 weeks builds the domain reputation that prevents throttling entirely.
• Even one spam complaint out of 50 cold emails puts you at a 2% complaint rate. That’s 6x over Gmail’s 0.3% threshold.
• If your domain gets burned, you can’t recover it. You need new domains, new DNS, new inboxes, and another 4 weeks of warm-up.

Below, you’ll find the actual SMTP error codes that indicate throttling from Gmail, Outlook, and Yahoo, plus a full breakdown of how each ISP throttles differently and what to do about it.

What Is Email Throttling?

Email throttling is when ISPs or email service providers intentionally limit the rate at which emails are accepted or sent.

Think of it as a speed limit for email delivery.

But throttling has two faces, and understanding both matters if you’re doing cold outreach.

Receiver-side throttling (the punishment): ISPs like Gmail, Outlook, and Yahoo temporarily defer or reject incoming emails when they detect suspicious sending patterns.

This results in 4xx SMTP response codes. Your emails aren’t permanently rejected. They’re delayed.

The receiving server is telling your sending server: “Slow down. Try again later.”

Sender-side throttling (the strategy): This is when you or your sending tool deliberately limit outgoing volume to avoid triggering ISP filters.

You’re imposing the speed limit on yourself before ISPs impose it on you. This is proactive, and it’s what smart cold emailers do.

From running a warm-up tool that processes thousands of inboxes, I see both sides of this daily.

The senders who throttle themselves rarely get throttled by ISPs.

The ones who don’t are the ones filling up support tickets asking why their emails stopped landing.

Throttling vs Deferral vs Bounce: What’s the Actual Difference?

Most cold emailers confuse these three terms.

They’re fundamentally different problems with different fixes.

The key distinction: throttling and deferrals are temporary. Bounces are permanent.

• If you’re seeing 4xx codes, your emails are being slowed down but not killed.
• If you’re seeing 5xx codes, something is fundamentally broken.

Bad address, failed authentication, or your domain is already burned.

Most cold emailers see deferrals and panic, thinking their emails bounced. They didn’t.

But if you ignore the deferrals and keep sending at the same rate, they will escalate to bounces.

How to Tell If Your Emails Are Being Throttled (Real SMTP Error Codes)

Here’s the problem most cold emailers face: they never check SMTP logs.

Their sending tool says “delivered,” so they assume everything is fine. But “delivered” doesn’t mean “landed in inbox.”

It means the receiving server accepted the email, which could mean it went straight to spam.

Throttling often starts silently. But when it gets loud enough to generate error codes, here’s exactly what to look for in your delivery logs.

These are the actual error strings you’ll find in your SMTP logs. I’ve seen every one of these across our warm-up network.

Gmail Throttling Codes

Gmail uses the 421-4.7.28 code family for most throttling actions, but the message string tells you exactly why:

• 421-4.7.28(IP-based rate limit): Your IP is sending too much unsolicited mail. Gmail has temporarily rate-limited delivery from your IP address. Common on shared infrastructure where multiple senders share the same IP.
• 421-4.7.28(URL-based): Gmail detected a high rate of unsolicited mail containing a URL domain you’re linking to. If you’re including the same link in every cold email, this is the code you’ll see.
• 421-4.7.28(SPF domain-based): Gmail is throttling based on the domain in your SPF record. This is domain-level throttling, the kind cold emailers should fear most because it follows your domain, not your IP.
• 421-4.7.28(DKIM domain-based): Same pattern, but Gmail is keying off your DKIM signing domain. Again, domain-level.
• 421-4.7.26(Unauthenticated mail): Your emails are missing SPF or DKIM authentication. Since Gmail’s February 2024 enforcement, unauthenticated mail gets deferred or rejected outright.

Important: As of November 2025, Gmail escalated from temporary deferrals (421) to permanent rejections (550) for non-compliant senders. What used to be a warning is now a wall.

Microsoft/Outlook Throttling Codes

Microsoft’s throttling codes are more straightforward, but the behavior is different. Outlook watches concurrent connections more than volume per hour.

• 421 RP-001: Your sending IP has exceeded the rate limit. The reason is tied to IP or domain reputation. This is the most common Outlook throttling code.
• 421 RP-002: Rate limit exceeded on this specific connection. Reputation-based. You’re sending too fast on a single connection.
• 421 RP-003: Connection limit exceeded. You’ve opened too many simultaneous connections to Outlook’s servers. This one hits cold emailers running multiple inboxes that send at the same time.
• 550 5.7.15: Authentication failure. Since Microsoft’s May 2025 enforcement, emails without proper SPF, DKIM, and DMARC get permanently rejected, not deferred.

Microsoft is more binary than Gmail. Gmail gradually increases friction. Outlook tends to either accept or reject, with less middle ground.

Once you’re flagged, recovery is harder.

Yahoo Throttling Codes

Yahoo is the most aggressive throttler of the big three for cold emailers. Their TS-code system tells a clear escalation story:

• 421 4.7.0 [TS01]: New or cold IP throttle. This fires fast on un-warmed senders, often before you’ve sent enough volume to even test your campaign. Yahoo sees an unfamiliar IP and immediately slows you down.
• 421 4.16.56 [TS02]: Temporarily deferred due to excessive user complaints. People are marking your emails as spam, and Yahoo is responding.
• 421 4.7.1 [TS03]: Permanently deferred. Reputation hold. This is the severe one. Your sending is effectively frozen until reputation improves, which can take weeks.
• 421 4.7.0 [TSS04]: Unexpected volume or user complaints. A catch-all for suspicious patterns.

[TS06]: Escalation after repeated TS02/TS03 warnings. At this point, recovery becomes very difficult and may require contacting Yahoo’s postmaster team directly.

Yahoo recommends waiting approximately 4 hours before retrying after a TS-code deferral.

But the real fix is proper warm-up before you ever trigger TS01.

What Causes Email Throttling?

Every cause below is explained through the lens of cold email, not marketing email.

The triggers are the same in name, but the math and impact are completely different at cold email scale.

Sending From an Un-Warmed Domain or Inbox

A brand-new domain has zero sending history. ISPs have nothing to evaluate you against, so they treat you as suspicious by default.

A new domain sending even 40–50 cold emails per day without warm-up commonly triggers Gmail deferrals. The ISP doesn’t know if you’re a legitimate salesperson or a spammer.

Without positive engagement signals to prove you’re the former, it assumes the latter.

Sudden Volume Spikes

ISPs build a “fingerprint” of your normal sending pattern.

If you usually send 10 emails a day and suddenly fire off 200, it looks like a compromised account or a spam operation ramping up.

The safe ramp-up rate is a 20% increase per day, or roughly 2–3 additional emails per day.

Anything faster triggers suspicion, even if the total volume is still low by marketing email standards.

Spam Complaints (The Cold Email Math Problem)

This is where the math gets brutal for cold emailers.

Gmail’s complaint rate threshold is 0.3%. They enforce at that level and recommend staying below 0.1%.

For a marketing emailer sending 10,000 emails, 0.3% is 30 complaints. That’s absorbable across a large list.

For a cold emailer sending 50 emails per day, a single “Report Spam” click equals a 2% complaint rate.

That’s more than 6x over Gmail’s threshold, from one person.

Cold emailers have almost zero margin for complaints. One bad prospect having a bad day can trigger throttling on your inbox.

Poor List Quality and High Bounce Rates

ISPs interpret high bounce rates as a signal of bad email list hygiene, which in their experience correlates strongly with spam.

Keep your bounce rate below 2%.

Sending to invalid addresses, catch-all domains, or role-based addresses (info@, sales@, support@) inflates your bounce rate and tells ISPs you don’t know who you’re emailing.

Missing or Broken Authentication (SPF, DKIM, DMARC)

This is no longer optional. Gmail and Yahoo started enforcing SPF and DKIM authentication in February 2024. Microsoft followed in May 2025.

Gmail now issues 421-4.7.26 for unauthenticated mail. Microsoft rejects outright with 550 5.7.15.

If your authentication records are missing, misconfigured, or misaligned, you’ll get throttled or blocked before ISPs even evaluate your content or reputation.

Also Read: How to Set Up Your SPF, DKIM, and DMARC Authentication Records in 2026

Non-Human Sending Patterns

ISPs use machine learning to detect automated sending behavior. Sending at perfect intervals (every 3 minutes, same time every day, identical gaps between emails) gets flagged as bot behavior even at low volumes.

Cold emailers need irregular, human-like sending gaps. Randomize your delays between emails. Vary your sending times. If your sending pattern looks like a machine wrote it, ISPs will treat it like one.

Why Throttling Hits Cold Emailers Differently Than Email Marketers

This is the section most throttling guides don’t have, because most throttling guides aren’t written for cold emailers.

Every competitor guide in the search results explains throttling from the marketing email perspective: volume limits, IP warming, rate limiting from ESPs. That advice is accurate for marketers. It’s misleading for cold emailers.

The fundamental difference comes down to five things.

1. No opt-in means a higher complaint rate per email.

Marketing emails go to opted-in subscribers who chose to receive them. Cold emails go to people who never asked. Even one complaint out of 50 emails gives you a 2% complaint rate, more than 6x over Gmail’s 0.3% enforcement threshold. Cold emailers have zero margin.

2. Damage hits the domain, not an IP you can swap.

Marketing emailers use ESPs with dedicated IPs. When an IP gets burned, they switch to a new one. Cold emailers use Google Workspace or Microsoft 365, shared infrastructure where you don’t control the IP. Your reputation lives on your domain. You can’t swap your domain the way you swap an IP.

3. Silent escalation: no error codes at Stage 1.

When a marketing emailer gets throttled, they see 421 deferral codes immediately. It’s loud. They know it’s happening.

Cold email throttling often starts silently. Gmail routes your emails to spam. No bounce. No error code. Your sending tool still shows “delivered.” By the time you notice open rates dropping, your domain reputation has already taken damage.

4. ISPs track sending patterns, not just volume.

Gmail’s machine learning doesn’t just count emails. It evaluates how they’re sent. Cold emailers sending at perfect intervals get flagged for non-human behavior even at low volumes. Marketing emailers send in bulk blasts that ISPs expect and are designed to handle.

5. Recovery is slower and more expensive.

Marketing emailers recover by warming a new IP on the same domain, a 2–4 week process. Cold emailers whose domain gets burned need entirely new domains, new DNS records, new inboxes, and 4+ weeks of warm-up. The old domain is abandoned permanently.

Here’s the comparison side by side:

Running a warm-up tool that serves cold emailers, I see this pattern constantly. Someone’s domain gets burned, they come to us asking to warm new inboxes, but by then the domain is already gone. The damage happened weeks before they noticed.

The Cold Email Throttling Escalation Path (And Why It’s Harder to Recover From)

Cold email throttling doesn’t happen all at once. It follows a 4-stage escalation path, and the first stage is invisible.

For marketing emailers, the escalation is loud at every step: 421 deferral → IP block → IP blacklist. You know where you stand.

For cold emailers, the path looks like this:

Stage 1: Silent Spam Folder Placement

Emails show “delivered” in your sending tool. But they’re landing in spam or the promotions tab.

No error codes. No bounces. Open rates drop gradually. Replies slow down and then stop.

You don’t know it’s happening unless you run inbox placement tests. Most cold emailers don’t.

This is where most cold emailers are when they first notice something is wrong, but the damage started days or weeks ago. They blame their subject lines, rewrite their copy, swap their CTAs. The real problem is underneath all of that.

Stage 2: Domain Reputation Drop

Google Postmaster Tools shows your domain reputation declining from “High” to “Medium” or “Low.”

Inbox placement falls from roughly 90% to 60–70%. The emails that do land in inbox get less engagement because your best prospects already got the spam-folder version.

Warm-up engagement signals start weakening because fewer warm-up emails reach the inbox. You start seeing occasional 421 deferrals in your SMTP logs.

This is when most cold emailers first realize something is wrong, because the deferrals are the first visible symptom. But the reputation damage has been building since Stage 1.

Stage 3: Account-Level Restriction

The individual inbox gets flagged by the ISP.

Gmail may lock the account or require CAPTCHA verification. Outlook may suspend sending privileges. The inbox becomes difficult or impossible to send from.

Worse, other inboxes on the same domain start getting affected. Reputation bleeds across the domain. If you have three inboxes on yourcompany.com and one gets flagged, the other two start seeing reduced deliverability.

At this stage, the flagged inbox may be unrecoverable. The move is to switch to a different inbox on the same domain and re-warm, but only if the domain itself isn’t compromised yet.

Stage 4: Domain-Level Blacklist

The entire domain is burned. Every inbox on that domain lands in spam: existing inboxes, new inboxes, all of them. Even a freshly created inbox on the domain inherits the bad reputation.

The domain is effectively dead for cold outreach.

Recovery at this stage means starting over entirely. New domains. Fresh DNS configuration (SPF, DKIM, DMARC). New inboxes. Four weeks of warm-up before any cold outreach. The old domain gets retired from outreach permanently.

The key insight across all four stages: most cold emailers only notice at Stage 2 or 3 because Stage 1 is silent. By then, recovery requires weeks of re-warming at best, or abandoning the domain entirely at worst.

How Email Warm-Up Prevents Throttling (With Real Timeline Data)

I built TrulyInbox, so I’ll be transparent: warm-up is our core product.

But this timeline reflects what I’ve seen work across thousands of inboxes, not a sales pitch.

Here’s how warm-up actually works and why it prevents throttling.

Warm-up tools generate positive engagement signals (opens, replies, spam rescues) from a network of real inboxes.

These signals tell ISPs: “This domain sends emails that real people want to read.”

Here’s the warm-up timeline we’ve validated across our network:

How Gmail, Outlook, and Yahoo Throttle Differently

Not all ISPs throttle the same way.

From our warm-up network, we consistently see Yahoo throttle the fastest on cold inboxes, Gmail give the most nuanced gradual treatment, and Outlook be the hardest to recover once flagged.

Here’s how they compare:

What this means practically for cold emailers:

Gmail is the most forgiving initially.

• It gives you a gradual warning through increasing deferrals before escalating.
• But as of November 2025, it now permanently rejects (550) non-compliant senders instead of just deferring.
• Monitor your domain reputation via Google Postmaster Tools and keep your spam rate below 0.1%.

Outlook watches concurrent connections more than volume.

• If you’re running multiple inboxes sending simultaneously from the same domain, you can hit connection limits before volume limits.
• Authentication (SPF, DKIM, DMARC) is strictly enforced since May 2025.

Yahoo is the toughest for cold emailers.

• TS01 fires on cold or new IPs very quickly, often before you’ve sent enough volume to even test your campaign.
• ahoo requires the longest warm-up period of the three.
• If you hit TS03 (permanent deferral), recovery is difficult and slow.

How to Fix Throttling When It’s Already Happening

If you’re reading this section, you’re probably already experiencing throttling.

Here’s the recovery path, written for cold emailers. Not “contact your ESP support” advice that only applies to marketers.

Step 1: Check Your SMTP Logs for Error Codes

Look for the specific 421 codes listed earlier in this guide. They tell you which ISP is throttling you and why.

If you’re seeing 421-4.7.28 variants, Gmail is throttling you. 421 RP-001/002/003 means Outlook. TS01 through TS06 means Yahoo.

If you don’t see error codes but open rates are dropping and replies have stopped, you’re likely at Stage 1 (silent spam folder placement). Run an inbox placement test to confirm. Your sending tool won’t tell you this is happening.

Step 2: Pause Cold Outreach Immediately

Stop all cold sending from the affected inbox and domain. This is non-negotiable.

Continuing to send cold emails into active throttling makes it worse. Every email that lands in spam, gets ignored, or triggers a complaint deepens the reputation damage. You’re digging a deeper hole.

Keep warm-up running, or increase warm-up volume slightly. Warm-up generates the positive engagement signals (opens, replies, spam rescues) that help rebuild your reputation. Pausing cold outreach while maintaining warm-up shifts your engagement ratio back in the right direction.

Step 3: Check Your Domain Reputation

Use the ISP-specific monitoring tools to assess how bad the damage is:

Gmail: Google Postmaster Tools. Check domain reputation (High/Medium/Low/Bad), spam rate, and authentication status. If domain reputation shows “Low” or “Bad,” you have significant damage.

Outlook: SNDS (Smart Network Data Services). Check IP reputation and complaint data. Look for red or yellow indicators.

Yahoo: Sender Hub (senders.yahooinc.com). Check for TS-code patterns and complaint trends.

These tools tell you whether you’re at Stage 2 (reputation drop, recoverable) or Stage 4 (domain burned, time to move on).

Step 4: Fix the Root Cause

Before you resume any sending, fix whatever caused the throttling:

Authentication: Verify SPF, DKIM, and DMARC are properly configured and aligned. Use a tool like MXToolbox or mail-tester.com to check. A single misconfigured record can cause ongoing rejections.

List quality: Clean your email list. Remove invalid addresses, catch-all domains, and role-based addresses (info@, support@, sales@). Target a bounce rate below 2%.

Content: Review your email content for spam triggers. Excessive links, spammy words, image-heavy emails, and identical content across every message all raise flags.

Sending patterns: Are you sending at perfect intervals? Add randomized delays between emails. Vary your sending times. Break any patterns that look automated.

Step 5: Re-Warm and Resume Slowly

Treat the affected inbox like a brand-new one. Follow the Phase 1–4 warm-up timeline again: seed phase, early ramp, stabilization, then outreach.

If you’re at Stage 3 (account-level restriction), the specific inbox may be unrecoverable. Create a new inbox on the same domain, warm it for 4 weeks, and resume outreach from the fresh inbox.

If you’re at Stage 4 (domain-level blacklist), the domain is burned. Every inbox on it will land in spam. The path forward is new domains entirely. Set up fresh DNS (SPF, DKIM, DMARC), create new inboxes, warm for 4 weeks, and only then begin cold outreach. The old domain should be retired from outreach permanently.

The hard truth: there’s no shortcut for recovery. The same 4-week warm-up process that prevents throttling is the same process that fixes it. The difference is that prevention costs you 4 weeks of patience upfront. Recovery costs you 4 weeks plus all the pipeline you lost while your domain was burned.

FAQs About Email Throttling

1. What is email throttling?

Email throttling is when ISPs like Gmail, Outlook, or Yahoo temporarily limit or delay emails from a sender. It’s triggered by suspicious sending patterns, poor reputation, or authentication failures. For cold emailers, it often starts silently: emails land in spam without any error codes.

2. Is email throttling the same as getting blocked?

No. Throttling is a temporary rate limit (4xx codes). Your server can retry and emails eventually get through. Blocking is a permanent rejection (5xx codes). But if you ignore throttling, it escalates to blocking over time.

3. How many cold emails can I send per day without getting throttled?

On shared infrastructure (Google Workspace, Microsoft 365), the safe limit is 50 cold emails per day per inbox. On private infrastructure with dedicated IPs, you can go up to 100/day. The official sending limits are higher, but cold emails face stricter scrutiny than marketing or transactional email.

4. How long does email warm-up take before I can send cold emails?

A proper warm-up takes about 4 weeks.

• Weeks 1–2 are seed phase (5–20 warm-up emails/day).
• Weeks 2–3 you ramp to 50/day.
• Weeks 3–4 you hold at 50/day to stabilize reputation.

Cold outreach begins in week 5, with warm-up continuing at 15–20 emails/day alongside outreach.

5. What’s the difference between email throttling for cold email vs. marketing email?

Marketing email throttling is volume-driven. ISPs limit how many emails per hour from a given IP. Cold email throttling is behavior-driven. ISPs evaluate engagement patterns, complaint rates, and content at the domain level. Cold email throttling is harder to detect (often silent) and harder to recover from (domain burns vs. IP swaps).

6. How do I know if my emails are being throttled?

Check your SMTP delivery logs for 421 error codes. Gmail uses 421-4.7.28, Outlook uses 421 RP-001/002/003, Yahoo uses TS01/TS02/TS03 codes. If you don’t see error codes but open rates are dropping and replies have stopped, your emails may be silently landing in spam. Run an inbox placement test.

7. Can email warm-up tools prevent throttling?

Yes. Warm-up tools generate positive engagement signals (opens, replies, spam rescues) that build domain reputation before you send cold emails. This gives ISPs evidence that your domain is legitimate, reducing the chance of throttling when you start outreach. Warm-up should continue at 15–20 emails/day even after cold outreach begins.

8. What should I do if my domain is already burned from throttling?

If your domain reputation has dropped to the point where every inbox on it lands in spam, recovery on that domain is very difficult. The practical path is to set up new domains, configure fresh DNS (SPF, DKIM, DMARC), create new inboxes, and warm them for 4 weeks before any cold outreach. The old domain should be retired from outreach.