JournalOutreachNo. 03
How to Scale Cold Email Without Burning Your Domain
Scale cold email without burning your domain: Google, Yahoo and Microsoft rules, mailbox ramp-up, sending caps, stop rules and a free planner.
Marko Raković7 min read8 sections

Contents
Published by Perpetual
To scale cold email without burning your domain, authenticate every sending domain, add volume through more mailboxes and domains rather than more email per mailbox, ramp each new mailbox gradually, and stop automatically when bounces or complaints rise. Google and Yahoo require spam complaint rates below 0.3%, and Google recommends staying below 0.1%. Volume problems are usually list problems, so fix who you send to before buying more mailboxes.
This guide summarizes what Google, Yahoo and Microsoft actually require, from their own pages, and shows the exact limits and stop rules Perpetual applies to every connected mailbox. Those are our defaults, not industry rules, and we explain the reasoning so you can set your own.
What mailbox providers require
Google and Microsoft apply their strictest rules above 5,000 messages a day, and Yahoo applies bulk-sender rules without publishing a number. Most cold outbound is far below that, but the requirements are a useful floor, and the basics apply to everyone.
| Requirement | Google (Gmail) | Yahoo | Microsoft (Outlook.com) |
|---|---|---|---|
| Applies strictly above | 5,000 messages a day to Gmail accounts | Bulk senders; no number published | 5,000 emails a day |
| Authentication | SPF or DKIM for all; SPF, DKIM and DMARC for bulk | SPF or DKIM for all; SPF, DKIM and DMARC for bulk | SPF and DKIM must pass; DMARC at least p=none |
| DMARC alignment | From domain aligned with SPF or DKIM | Relaxed alignment acceptable | Aligned with SPF or DKIM, preferably both |
| Spam complaint rate | Below 0.3%; recommended below 0.1% | Below 0.3% | No figure published |
| Unsubscribe | One-click for marketing and subscribed mail | One-click; honor within 2 days | Functional unsubscribe links |
| Other | TLS, valid forward and reverse DNS | Valid reverse DNS | Non-compliant mail goes to Junk |
Sources, read November 16, 2026: Google's email sender guidelines, Yahoo's Sender Hub and Microsoft's Outlook high-volume sender requirements. Google's requirements took effect in February 2024. Microsoft began sending non-compliant high-volume mail to Junk from May 5, 2025.
Two practical notes. Google Workspace also publishes per-user sending limits, but those are ceilings for normal use, far above what a cold sender should approach. And Gmail does not send per-message spam complaint reports back to senders, so a Gmail mailbox cannot see its own complaints directly. Google Postmaster Tools is where Gmail's view of your domain appears.
Set up the domain before the first send
- Use a separate sending domain or subdomain if you want to protect your main domain's reputation, and make sure it is a real, branded domain with a website.
- Publish SPF and DKIM for the domain, with a DKIM key of at least 1024 bits, the minimum both Google and Yahoo state. A 2048-bit key is a common choice where your provider supports it.
- Publish DMARC. A policy of p=none is enough to meet the requirements and lets you see reports before enforcing.
- Check alignment. The domain in the visible From address should match the SPF or DKIM domain.
- Verify it. Send a test to a mailbox you control and read the authentication results in the message headers.
Ramp each new mailbox gradually
A new mailbox that suddenly sends dozens of cold emails a day looks like abuse. Increase volume in steps, and advance only when bounces stay low. These are the steps Perpetual uses for a connected Google Workspace mailbox:
| Stage | Reachable after | Emails per day per mailbox |
|---|---|---|
| Stage 1 | A passing domain check | 20 |
| Stage 2 | 7 days | 40 |
| Stage 3 | 14 days | 60 |
| Established | 28 days | 80 |
A mailbox moves up only when it is old enough and its hard bounce rate over the last 7 days is under 2%. It never moves up because a plan allows more. The established cap stays at 80 because a connected mailbox is one person's account with its own reputation, and the provider's much higher ceiling is irrelevant for cold outreach.
Add capacity with mailboxes and domains, then do the math
Sending more from one mailbox concentrates risk. Spreading volume across mailboxes and domains limits the damage when one runs into trouble. Perpetual also caps each sending domain at 150 emails a day across all its connected mailboxes, because providers judge reputation by domain as well as by mailbox.
Remember that follow-ups use the same capacity as first emails. A worked example with invented inputs:
- Three established mailboxes at 80 a day give 240 sends.
- If all three share one domain, the domain cap holds them to 150. Two domains are needed to use all 240.
- With a three-email sequence in steady state, roughly one send in three is a first email, so 240 sends a day supports about 80 new contacts a day.
Download the sending capacity planner (CSV) to fill in your own mailboxes, domains, stages and sequence length. Our outbound cost breakdown prices the mailboxes and domains.
Decide your stop rules before launch
A problem caught after a day costs less than one caught after a week, so set automatic pauses in advance. Perpetual pauses a mailbox when any of these happens:
| Rule | Pauses when |
|---|---|
| Hard bounces | 5% or more of the last 50 sends, or 3 hard bounces in one day |
| Spam complaints | 0.3% over 1,000 sends in 14 days, or 2 complaints before reaching 1,000 sends |
| Policy blocks | 2 rejections for reputation, spam or authentication in a day, or 3% of the last 50 sends |
| Domain | Two mailboxes on the same domain tripping a rule within 24 hours pause every mailbox on it |
A paused mailbox resumes only by a person's decision, and not while the condition still holds. Catch-all addresses, where a domain accepts every recipient so an address cannot be proven to exist, are limited to 20% of a mailbox's daily volume. Sends are also spaced at least two minutes apart.
The complaint threshold mirrors the providers' 0.3% ceiling. The small-sample rule exists because, at low volume, waiting for a rate to become meaningful means waiting too long.
Fix the list before you add volume
Bounces and complaints come from who you write to. Verify addresses before sending, avoid guessing emails, remove anyone who opts out at once and permanently, and write only to people with a specific reason to hear from you. Sending relevant messages to fewer, verified people does more for a domain's reputation than raising volume. Our guide to building an ICP for outbound covers who should be on the list.
Where Perpetual fits
Perpetual sends from the Google Workspace mailboxes you connect, checks their domain authentication before automatic sending, applies the ramp, caps and stop rules above, and stops follow-ups when someone replies or opts out. These limits are set in the product so a campaign cannot outrun them.
It does not replace your own monitoring. Watch Google Postmaster Tools for your domain, since a Gmail mailbox receives no complaint feedback. Outlook and Microsoft 365 mailboxes cannot send from Perpetual yet. See the quickstart guide.
Frequently asked questions
How many cold emails can I send per day without hurting my domain?
There is no safe universal number. Start low on a new mailbox, ramp over several weeks, spread volume across mailboxes and domains, and let bounce and complaint rates decide whether you go higher. As a reference point, Perpetual starts a connected mailbox at 20 a day, caps it at 80 and allows 150 a day per sending domain.
Do I need DMARC for cold email?
Google and Yahoo require it for bulk senders, and a p=none policy meets that requirement. Publish it anyway; it costs nothing and gives you reports.
Should I use my main domain for cold email?
Many teams use a separate branded domain to keep their main domain's reputation apart. Whichever you choose, authenticate it fully.
Does email warm-up software prevent deliverability problems?
Gradual real volume to verified, relevant recipients is what builds reputation. No routine fixes a list with bad addresses or messages people mark as spam.













































