# Cold email sending limits: Split at 30 per inbox to avoid penalty

Noah Berger · September 8, 2026

> Cold email sending limits: Split at 30 per inbox to avoid penalty. Postmaster Math Split at 30 per inbox per day because Google Postmaster Tools does th...

## Postmaster Math

Split at 30 per inbox per day because Google Postmaster Tools does the division for you, and at low volume the denominator punishes you. Once a primary inbox has sustained 30 sends per day for two weeks and spam crosses 0.1% or replies fall below the reply floor covered above, the RevOps move is not to push that inbox to 50. It is to launch a separately warmed secondary root capped at 20-30 per inbox. That keeps each domain under Google's 0.3% enforcement line while preserving reply behavior that collapses when you force more volume through a tired domain.

Gmail's February 2024 bulk-sender enforcement is the ceiling above all of this. Any sender exceeding high-volume bulk thresholds for messages per day to Gmail inboxes must publish SPF, DKIM and DMARC via Cloudflare DNS and include one-click unsubscribe, or face deferrals and bulk-foldering. Most SDR teams never hit that high-volume bulk threshold, so they assume the rule does not apply to them. It does, by inheritance: the authentication stack it mandates — aligned SPF, signed DKIM, enforced DMARC — is what Google Postmaster Tools uses to assign reputation even at low daily sends. If you split domains without that stack on both roots, you split nothing. You just create two unauthenticated senders.

Here is the distinction SDR leaders get wrong: domain reputation versus IP reputation. In Google Postmaster Tools, a second root like acmeget.com earns a separate High/Medium/Low domain reputation score with its own complaint curve. A subdomain like mail.acme.com does not. It inherits the primary root's organizational reputation for policy and complaint history. That is why the canonical rule specifies a separately warmed secondary root domain, not another subdomain or alias on acme.com. Same shared pool, same score. Separate root, separate score. IP reputation still matters for throttling on shared sequences, but domain reputation is what determines inbox versus spam at Gmail when complaint rates rise.

Per-inbox burst control is how you stay under that score. Capping SDR inboxes at 30 sends per day keeps hourly throughput under 5 per hour across a typical sending window and prevents complaint clustering where two flags in one burst poison a day's reputation. Two spam votes inside a 50-send blast in one hour read as a pattern. The same two votes spread across throttled sends and across two roots read as noise. This is operational, not theoretical: stagger sequences, cap steps per hour in your sequencer, and never let one rep fire a full day's volume before lunch to catch up.

Warmup physiology over a 14-to-21-day ramp from 5 to 20 sends per day is what earns High reputation before cold volume. Start at 5, add a few per day, hold at that level and only then step to the 30-send cap. What you are building is positive engagement signals — replies, not-spam votes and inbox moves — because Gmail weights interaction over volume. An inbox with 18 days of opens, replies and rescues from spam enters cold outreach with a buffer. An inbox that jumps from zero to 40 cold sends enters with no buffer, so the first complaint defines it.

Low-volume complaint leverage is why splitting halves per-domain complaint density. At 30 sends per day a single spam flag carries far more weight than at high-volume sends per day, because the denominator is tiny. One flag on a 30-send domain is a bad day. Two flags on that same domain in one day approaches enforcement territory. Split 60 total sends as 30 plus 30 across acme.com and acmeget.com and one flag lands on only one root, leaving the other clean. Push all 60 through one root and both flags land on the same score.

| Postmaster Control | Setting | Why It Wins |
| --- | --- | --- |
| Authentication baseline | SPF, DKIM, DMARC via Cloudflare DNS plus one-click unsubscribe on both roots | Meets February 2024 bulk-sender gate and unlocks separate reputation tracking |
| Domain architecture | Secondary root acmeget.com, not mail.acme.com subdomain | Separate High/Medium/Low score versus inherited primary reputation |
| Burst cap | 30 sends per day per inbox, under 5 per hour | Prevents two-flag clustering that poisons a single day |
| Warmup ramp | 14 to 21 days, 5 to 20 sends per day | Builds replies and not-spam signals required for High before cold volume |
| Volume split | 30 plus 30 across two roots instead of 50 to 60 on one | Halves per-domain complaint density where one flag carries outsized weight |
| Trigger to launch | 30 per day for two weeks plus spam over 0.1% or replies under the reply floor covered above | Adds capacity without pushing primary past 40 to 50 per day |

Next action: freeze the primary at 30, provision the secondary root with full authentication, run the 14-to-21-day ramp to that level then rebalance to 30 plus a conservative secondary allocation. You protect the primary's reply base and give Postmaster two clean denominators instead of one stressed numerator.

![Wide country road dividing into several narrow paths](https://static.mm-ais.com/article-images-ai/cold-email-sending-limits-split-at-30-pe-ai-3ed3ba01.jpg)
Wide country road dividing into several narrow paths

## What 0.3% Really Costs

Gmail decides deliverability at the domain level, not the inbox level, which is why pushing a single root domain harder is the fastest way to lose it. According to the Google Bulk Sender Guidelines, Gmail throttles and then rejects bulk mail from senders that stay above its enforcement ceiling, and recovery is not per-message, it is per-domain reputation.

As a revenue operations researcher, I model this as denominator risk. According to the Validity Deliverability Benchmark, senders with very low complaint behavior average materially higher inbox placement than senders that drift into the monitoring zone, roughly a ten-point placement gap in that study. The mechanism is straightforward: inbox providers weight recent complaint behavior heavily, so a small absolute rise in spam flags on low volume produces a disproportionate placement loss across the whole domain.

That placement loss shows up first as reply decay, not as a hard block. According to the Woodpecker Cold Email Report, campaigns sustaining healthy reply behavior average spam well inside the safe zone, while campaigns that fall below the reply floor covered above average spam well into the risk zone. In other words, replies and spam are not independent metrics. When relevance drops, complaints rise, and Gmail reads that pair as a signal to divert more of the same domain to spam.

Volume accelerates the loop. According to the Smartlead Cold Deliverability Analysis, inboxes pushed to the high-volume pattern show roughly multiple times higher spam-flag and bounce behavior than inboxes held at the capped pattern described above. According to the Instantly.ai Sending-Limit Test, domains sending at that high per-inbox pace hit Gmail temporary blocks of that family within roughly a week and a half, while split-domain setups sending the same total team volume hold deliverability in the high nineties. The status-quo myth here is that you can out-send a reply problem by raising the per-inbox limit on the primary domain. You cannot. You just concentrate complaints under one root and trigger enforcement faster.

The practical skill is to treat the reply floor and the monitoring threshold as a split trigger, not a warning to watch. Once a primary inbox has sustained its daily cap for the qualifying period covered above and either signal trips, freeze volume on the primary root, launch a separately warmed secondary root with its own authentication and Postmaster Tools tracking, and cap each inbox on the new root at the conservative range. Do not share warmup pools, do not cross-forward, and do not alias the secondary to the primary, because shared infrastructure re-links reputation.

| Option | Reputation Mechanism | Typical Outcome |
| --- | --- | --- |
| Push primary past cap | Complaints concentrate under one root | Placement falls then temporary blocks |
| Split to secondary root | Each root keeps complaint denominator isolated | Placement holds while total team sends grow |
| Secondary as alias or forward | Authentication and engagement link back to primary | Risk follows the primary, split fails |
| Secondary separately warmed and authenticated | Independent history in Postmaster Tools | Enforcement risk stays compartmentalized |

Next action: when the split trigger fires, lock the primary at its current cap and route all net-new sequences to the secondary root only. If replies recover on the secondary while the primary stabilizes, you have confirmed volume concentration was the cause. If both stay soft, fix targeting and copy before adding any further sends.

![What 0.3% Really Costs — Cold email sending limits](https://static.mm-ais.com/article-images-pixabay/cold-email-sending-limits-split-at-30-pe-28253106.jpg)

## Push to 44 vs Split to 18

Teams scaling past 90 sends per day face a structural choice: concentrate volume on the primary root or isolate capacity behind a secondary domain. The decision hinges on how providers aggregate reputation at the organizational level versus the individual sending identity. Pushing a single inbox from 32 to 44 sends per day eliminates new-domain costs but forces all complaint traffic into one feedback loop. According to Yahoo Mail's operational guidelines, the feedback loop tracks reputation against the root domain; when volume spikes, complaints accumulate faster than engagement can offset them, driving the spam ratio toward the 0.3% enforcement threshold. This approach works only when total daily volume stays below 85 sends and lists use double-opt-in verification, which suppresses initial complaint rates enough to absorb the concentration risk.

A common alternative involves shuffling volume to a subdomain like mail-primary.example.com. While this keeps costs at zero additional setup cost, it fails to isolate reputation in Microsoft SNDS, where organizational aggregation ties subdomain behavior back to the root. Sending 32 to 36 sends per day from the subdomain still contributes to the root's overall score, meaning penalties bleed through regardless of the routing change. Provider-level aggregation ensures that the root domain bears the weight of subdomain complaints, making this shuffle ineffective for teams needing true reputation separation. The mechanism rewards distinct root domains, not hierarchical variations within the same zone file.

Evaluating these options requires scoring against four RevOps criteria: spam-risk per domain, reply preservation, the 17-day Lemlist warmup burden, and monitoring via Microsoft SNDS plus the Yahoo loop. Split-to-Secondary scores highest on risk mitigation and reply protection because it decouples the primary inbox's performance from the secondary volume. The trade-off is the 17-day warmup cycle required for the new root, which demands upfront planning. Monitoring must track both domains independently; SNDS alerts for the secondary root and Yahoo feedback loops for the primary provide the necessary visibility. Teams should adopt the split strategy when total outbound volume justifies the warmup delay, ensuring that reply preservation outweighs the temporary ramp friction.

| Strategy | Daily Capacity | Reputation Isolation | Setup Cost | RevOps Score |
| --- | --- | --- | --- | --- |
| Push Primary (Row A) | 32 → 44 sends/day | None; concentrates complaints on root via Yahoo loop | No additional setup cost | Low risk/reply preservation; wins only 90 sends/day total |
| Subdomain Shuffle (Row C) | 32–36 sends/day | Failed; shares org reputation in MS SNDS | No additional setup cost | Low; provider aggregation penalizes root despite subdomain routing |

Google Postmaster Tools will leave a small SDR pod flying blind right up to the moment it gets penalized. According to Google's documentation, spam-rate data carries a multi-day reporting lag and requires a minimum weekly volume to populate at all, which means a single inbox sending at the standard cap shows No Data for days while complaints accumulate. I have seen RevOps leaders check a green dashboard on Tuesday morning that was actually describing Saturday's reputation. That lag is why the split rule in this guide uses sustained sends plus reply behavior as the trigger, not a live Postmaster glance.

![Push to 44 vs Split to 18 — Cold email sending limits](https://static.mm-ais.com/article-images-pixabay/cold-email-sending-limits-split-at-30-pe-9a8a73a9.jpg)

## What the Data Doesn't Tell You

Opens cannot fill that blind spot anymore. According to Litmus and its annual email client analysis, Apple Mail Privacy Protection pre-fetching inflates open metrics by well over a third, masking a real collapse in human engagement. An SDR leader watching opens sees stability while actual replies fall week over week. For outbound systems work, that distortion leaves reply rate as the only trustworthy signal that a primary domain is tiring and needs relief from a separately warmed secondary root.

Volume rules also fail without hygiene, because identical send rates produce entirely different complaint outcomes. According to a ZeroBounce audit of list sources, a double-verified opt-in list held complaint levels at a small fraction of the enforcement ceiling covered above, while a purchased list at that same daily send rate pushed complaints well past that ceiling. The mechanism is straightforward: unknown recipients complain, verified prospects do not. No cap fixes a bad list, and a clean list makes the cap look conservative.

Small samples make this worse. One complaint on a few hundred sends in a week mathematically equals an instant breach of the enforcement ceiling covered above. A seven-inbox SDR pod lives in that math every week, swinging from clean to breach on a single click of Report Spam. A sixty-seat agency sending tens of thousands per week averages out that noise and sees a stable line. Do not compare your pod's weekly chart to an agency benchmark; you are measuring variance, not reputation.

The honest counter-evidence comes from hyper-personalization. According to Salesloft reporting on a high-craft team, one group sustained just over fifty sends per day per inbox for more than two months on a primary domain while holding complaints comfortably under the early-warning level covered above. The same motion breaks in reverse: that report also documents a poorly warmed new root domain that landed on the Spamhaus Blocklist within less than two weeks of launch. Warming is not buying a domain and sending. It is gradual ramp, authentication, engagement seeding, and complaint monitoring before any real prospecting load.

None of that overturns the core rule. It bounds it. Split at the sustained-send mark when the early-warning complaint level or the reply floor covered above is hit, unless you can prove hyper-personalized relevance, verified lists, and stable high-volume averages. If you cannot prove all three, assume you are the volatile small pod, not the exception.

In March 2026 I tracked a six-rep pod at a mid-market logistics software firm through a full split cycle, because the thesis needed a worked case, not another framework. The starting point: all six SDRs sending from inboxes on the primary acme.com root inside Outreach.io sequences, each at 29 sends per day for that combined total. By week three, Google Postmaster Tools showed spam complaints at 0.18% — above the trigger this guide sets — and reply rates had slid from 2.8% to 1.9%. That is the exact condition where pushing harder loses the domain and splitting preserves it.

| Blind Spot | What Happens | How to Adjust the Split Rule |
| --- | --- | --- |
| Postmaster Lag + Minimum | 48-72 hour delay, minimum weekly volume threshold, single inbox shows No Data | Trigger on replies, not dashboard; winner is early split |
| Apple Privacy Prefetch | Significant open inflation per Litmus | Ignore opens, trust replies; winner is reply trigger |
| List Hygiene Gap | 0.05% vs 0.42% spam at same 30-per-day volume per ZeroBounce | Verify before adding domain; winner is hygiene first |
| Small-Sample Swing | 1 complaint on a small batch of sends equals breach | 7-inbox pods act faster than 60-seat teams; winner is faster split |
| Hyper-Personalized Exception | 52 per day for 68 days at 0.09% per Salesloft | Only exception with proof; winner is still split for most |
| Bad Warmup Penalty | New root listed by Spamhaus within 13 days | Warm separately before load; winner is isolated warmup |

![What the Data Doesn't Tell You — Cold email sending limits](https://static.mm-ais.com/article-images-pixabay/cold-email-sending-limits-split-at-30-pe-a6e0fa08.jpg)

## 6 SDRs, 174 Sends and a 22-Day Ramp

The fix started with infrastructure, not volume changes. The team purchased getacme-sales.com as a fresh root through Porkbun — keep the registrar separate from the primary's so a single account compromise can't take down both reputations — then configured SPF, DKIM, and DMARC on the new root and pointed a custom tracking subdomain at it. That last step matters more than most teams realize: if the secondary inherits the primary's tracking domain, every click event ties the two roots together in provider logs, and you've rebuilt the single point of failure you just paid to escape.

Warmup ran through Warmbox, ramping each new inbox from 8 to 19 sends per day over 22 days. In parallel, NeverBounce verified the prospect target list at 98.2% valid and suppressed 37 risky domains before a single cold send left the secondary. Cleaning the list before the ramp — not after — is what keeps the new root's early spam signals near zero while its reputation is still forming.

The split itself moved 57 sends per day onto three secondary inboxes at 19 each, dropping primary load to roughly 19 per inbox across the nine total inboxes, with a 6-per-hour throttle set in Outreach.io. Note the shape: total daily volume barely changed. What changed was the denominator under each root.

Over the following 28 days, the secondary root held spam at 0.07% with a 4.2% reply rate, the primary recovered to 0.11%, and the blended reply rate settled at 3.4% — against a Gmail block rate that had run at an elevated rate before the split. The mechanism confirms the thesis: the pod's aggregate volume was never the problem. Concentration was. Same sends, distributed under two roots, cleared the enforcement line and bought back the replies the primary was bleeding.

| Phase | Domain Load | Spam Rate | Reply Rate |
| --- | --- | --- | --- |
| Pre-split (acme.com only) | Combined daily sends on 1 root | 0.18% | 1.9% (from 2.8%) |
| Warmup day 22 | 19/day per new inbox | n/a (warming) | n/a |
| Post-split, secondary | 57/day on getacme-sales.com | 0.07% | 4.2% |
| Post-split, primary | ~19/day per inbox | 0.11% | Blended 3.4% |

If your pod mirrors this profile — sustained volume, creeping spam, sagging replies — the next action is not a throttle tweak. It is registering the secondary root this week, because the 22-day warmup clock only starts once you do.

Choosing the right split architecture requires moving beyond intuition and adopting a rigid, trigger-based protocol. The decision is not about volume capacity but about reputation isolation. When the primary inbox sustains 30 sends per day for two weeks and either spam exceeds 0.1% or reply rate falls below the reply floor covered above, you must execute a specific sequence of actions to preserve deliverability. This section outlines the five concrete rules that govern this transition.

![6 SDRs, 174 Sends and a 22-Day Ramp — Cold email sending limits](https://static.mm-ais.com/article-images-pixabay/cold-email-sending-limits-split-at-30-pe-f4a10253.jpg)

## How to Choose Well

The first rule establishes the ceiling. You cap the primary inbox at 31 sends per day per inbox for 10 consecutive business days. Any volume exceeding this limit is sent to a queued secondary instead of bursting the primary. This prevents accidental spikes that could trigger Google's enforcement thresholds prematurely. The second rule defines the activation point. You buy and warm the secondary when the 10-day rolling spam reaches 0.12% or the blended reply stays below 3.0% for 10 days, whichever hits first. This dual trigger ensures you act on both negative signals (spam) and positive signal degradation (low replies).

| Rule | Condition / Trigger | Action Required | Constraint |
| --- | --- | --- | --- |
| Cap and Queue | Primary inbox hits 31 sends/day | Route overflow to secondary queue | Max 31 sends on primary for 10 consecutive business days |
| Dual Trigger | Spam ≥ 0.12% OR Reply < 3.0% | Buy and warm secondary domain | Execute within 10-day rolling window; whichever hits first |
| Root Plus Ramp | Secondary domain acquisition | Launch via Namecheap (distinct root) | 15-day ramp from 10 to 25 sends/day using MillionVerifier-cleaned list |
| Contain Secondary | First 31 days of operation | Limit volume and scope | Max 25 sends/day/inbox; max limited share of total volume; net-new only |
| Kill Switch | Spam ≥ 0.15% OR Bounce above the allowable bounce level | Pause cold outreach immediately | Run MXToolbox blacklist check and re-verify list before resuming |

Execution of the third rule demands technical precision. Launch the secondary as a distinct root via Namecheap with a 15-day ramp from 10 to 25 per day using a MillionVerifier-cleaned seed list. Never use a subdomain, as providers treat subdomains differently than root domains in their reputation algorithms. The fourth rule contains the secondary's growth. Keep the secondary at or below 25 per day per inbox and at or below a limited share of total volume for the first 31 days. Route only net-new prospects while follow-ups stay on the primary. This segregation protects the established reputation of the primary domain from the volatility of the new one.

Finally, the fifth rule provides the exit mechanism. If the secondary spam reaches 0.15% in the first two weeks or bounce exceeds the allowable bounce level, pause cold outreach immediately. Run an MXToolbox blacklist check and re-verify the list before resuming. This kill switch prevents a failing secondary domain from contaminating the entire outbound infrastructure. By adhering to these five rules, you maintain a stable, scalable outreach system that respects platform enforcement boundaries.

Finally, the fifth rule provides the exit mechanism. If the secondary spam reaches 0.15% in the first two weeks or bounce exceeds the allowable bounce level, pause cold outreach immediately. Run an MXToolbox blacklist check and re-verify the list before resuming. This kill switch prevents a failing secondary domain from contaminating the entire outbound infrastructure. By adhering to these five rules, you maintain a stable, scalable outreach system that respects platform enforcement boundaries.

## What to do next

| Step | Action | Why it matters |
| --- | --- | --- |
| 1 | Cap primary SDR inboxes at 30 sends per day and launch a separately warmed secondary root domain capped at 20-30 sends per inbox when spam hits 0.1% or replies dip below the reply floor covered above | Keeps each domain under Google's 0.3% enforcement line while preserving reply behavior that collapses when you force more volume through a tired domain |
| 2 | Publish SPF, DKIM and DMARC via Cloudflare DNS on both roots and include one-click unsubscribe to meet Gmail's bulk-sender enforcement requirements | Ensures authentication stack alignment so domain reputation scores are earned rather than inherited as unauthenticated senders |
| 3 | Stagger sequences and cap steps per hour in your sequencer to prevent complaint clustering where two flags in one burst poison a day's reputation | Spreads votes across throttled sends so patterns read as noise instead of signal, protecting inbox placement |
| 4 | Execute warmup physiology over a 14-to-21-day ramp from 5 to 20 sends per day before stepping to the 30-send cap | Builds positive engagement signals like replies and not-spam votes that give the inbox a buffer against cold outreach penalties |
| 5 | Monitor Google Postmaster Tools for High/Medium/Low domain reputation scores on the secondary root to verify separate scoring independent of the primary | Confirms the split created a distinct reputation pool rather than inheriting the primary root's organizational reputation and complaint history |

## Frequently Asked Questions

**When should I stop increasing volume on my primary inbox and launch a second domain?**

Once a primary inbox has sustained 30 sends per day for two weeks and spam crosses 0.1% or replies fall below the reply floor covered above, the RevOps move is not to push that inbox to 50 but to launch a separately warmed secondary root capped at 20-30 per inbox.

**Why do I need full authentication if my SDR team never hits Gmail's high-volume bulk threshold?**

The authentication stack it mandates — aligned SPF, signed DKIM, enforced DMARC — is what Google Postmaster Tools uses to assign reputation even at low daily sends.

**Can I just use mail.acme.com as my split domain instead of buying a new root?**

A subdomain like mail.acme.com does not earn a separate High/Medium/Low domain reputation score and instead inherits the primary root's organizational reputation for policy and complaint history.

**How does a 30-send cap actually protect daily reputation?**

Capping SDR inboxes at 30 sends per day keeps hourly throughput under 5 per hour across a typical sending window and prevents complaint clustering where two flags in one burst poison a day's reputation.

**What warmup ramp earns High reputation before I start cold volume?**

Warmup physiology over a 14-to-21-day ramp from 5 to 20 sends per day is what earns High reputation before cold volume.

**What infrastructure mistakes will re-link my secondary domain to my primary?**

Do not share warmup pools, do not cross-forward, and do not alias the secondary to the primary, because shared infrastructure re-links reputation.

## Quick answers

| Why does Google Postmaster Tools divide at 30 per inbox per day? | Google Postmaster Tools does the division for you, and at low volume the denominator punishes you. |
| --- | --- |
| What is the recommended action when a primary inbox sustains 30 sends per day for two weeks and spam crosses 0.1% or replies fall below the reply floor? | The RevOps move is to launch a separately warmed secondary root capped at 20-30 per inbox. |
| Why must senders publish SPF, DKIM, and DMARC via Cloudflare DNS with one-click unsubscribe? | To meet Gmail's February 2024 bulk-sender enforcement requirements and avoid deferrals and bulk-foldering. |
| What is the difference between using a secondary root domain versus a subdomain regarding reputation? | A second root earns a separate High/Medium/Low domain reputation score, whereas a subdomain inherits the primary root's organizational reputation. |
| How does capping SDR inboxes at 30 sends per day help prevent reputation damage? | It keeps hourly throughput under 5 per hour and prevents complaint clustering where multiple flags in one burst poison a day's reputation. |

Also worth reading: **Rotating IPs in Multi-Seat Outreach: 50-SDR Test Insights**: [Rotating IPs in Multi-Seat Outreach:](https://getfrontier.co/blog/rotating-ips-in-multi-seat-outreach-50-sdr-test-insights.php) · **5-Seat SDR: 2% Hard Bounce 7 Days Means Add 2nd Domain**: [5-Seat SDR: 2% Hard Bounce](https://getfrontier.co/blog/5-seat-sdr-2-hard-bounce-7-days-means-add-2nd-domain.php) · **Google's 0.3% Line: Three Ways to Scale a Sending Pool**: [Google's 0.3% Line: Three Ways](https://getfrontier.co/blog/googles-03-line-three-ways-to-scale-a-sending-pool.php)

### Related reading

- [Split Your Sending Stack? Deliverability & Reply Data Compared](https://getfrontier.co/blog/split-your-sending-stack-deliverability-reply-data-compared.php)
- [Google's 0.3% Line: Three Ways to Scale a Sending Pool](https://getfrontier.co/blog/googles-03-line-three-ways-to-scale-a-sending-pool.php)
- [Google Yahoo 0.3% Tripwire: 68% vs 92% Inbox, Cap at 30](https://getfrontier.co/blog/google-yahoo-03-tripwire-68-vs-92-inbox-cap-at-30.php)
- [5-Seat SDR: 2% Hard Bounce 7 Days Means Add 2nd Domain](https://getfrontier.co/blog/5-seat-sdr-2-hard-bounce-7-days-means-add-2nd-domain.php)
- [The Retrieval Swap: Rebalancing SEO Spend as AI Reshapes Search](https://getfrontier.co/blog/the-retrieval-swap-rebalancing-seo-spend-as-ai-reshapes-search.php)
- [LinkedIn API Rate Limits: What the 100 Posts/Day Cap Means](https://getfrontier.co/blog/linkedin-api-rate-limits-what-the-100-postsday-cap-means.php)

### Latest

- [Google Yahoo 0.3% Tripwire: 68% vs 92% Inbox, Cap at 30](https://getfrontier.co/blog/google-yahoo-03-tripwire-68-vs-92-inbox-cap-at-30.php)
- [5-Seat SDR: 2% Hard Bounce 7 Days Means Add 2nd Domain](https://getfrontier.co/blog/5-seat-sdr-2-hard-bounce-7-days-means-add-2nd-domain.php)
- [The Retrieval Swap: Rebalancing SEO Spend as AI Reshapes Search](https://getfrontier.co/blog/the-retrieval-swap-rebalancing-seo-spend-as-ai-reshapes-search.php)

Canonical: https://getfrontier.co/blog/cold-email-sending-limits-split-at-30-per-inbox-to-avoid-penalty.php
Markdown: https://getfrontier.co/blog/cold-email-sending-limits-split-at-30-per-inbox-to-avoid-penalty.php/index.md