Why Warm-Up Exists
Mailbox providers — Gmail, Outlook, Yahoo — use sender reputation as the primary input to their spam filter. Reputation is a running score built from authentication results, recipient engagement (opens, replies, moves-from-spam), complaint rate, and send-volume history. A brand-new domain has none of these data points. Faced with an unknown sender that arrives at scale, providers default to the most conservative bucket: junk, or outright rejection at SMTP.
Warm-up solves this by giving the provider time to observe engaged, authenticated traffic before the full production volume lands. When the volume ramp is done correctly, the provider has already built a reputation score — and a positive one — by the time the domain sends at scale. When it is skipped, the sender arrives with no reputation and the provider applies its unknown-sender heuristics, which almost always produce spam-folder placement at Gmail and yellow-band classification at Microsoft SNDS.
The same logic applies to re-activating a dormant domain. A domain that was sending at 2,000 per day eighteen months ago and has been idle since is treated as a new warm-up by most providers — the reputation data from prior sends has decayed out of their scoring window and the current sending identity is effectively unknown again.
Pre-Flight Authentication Checklist
No warm-up strategy can compensate for a missing or broken authentication stack. Gmail and Yahoo have required SPF, DKIM, and DMARC for bulk senders since February 2024, and both providers state explicitly that a new domain without all three legs cannot graduate past the lowest reputation band regardless of engagement. Complete all four of the following before sending any warm-up volume:
- SPF. Publish a
v=spf1TXT record at your sending domain listing every IP authorised to send on its behalf. Stay under the 10-DNS-lookup limit. Validate SPF → - DKIM. Configure your mail server or ESP to sign every outgoing message with a 2048-bit key. The public key lives at
selector._domainkey.yourdomain.com. Confirm the signature passes at your receiving hop before ramping. - DMARC. Publish a DMARC record at
_dmarc.yourdomain.comwithp=noneand arua=address to receive aggregate reports. Validate DMARC → - MX record. Publish an MX record so receiving servers can deliver replies. A domain with no MX record looks send-only and is treated as higher-risk by several ISPs.
Run the free warm-up checker to confirm your auth posture before the first ramp step — it resolves SPF, DKIM, DMARC, and MX in one pass and returns a 0–100 warm-up readiness score.
Volume-Ramp Cadence
The ramp below targets a steady-state of 500+ per day for a new domain reaching a moderate cold-email or transactional volume. Adjust proportionally for higher targets — a 10,000-per-day target extends each phase by roughly 2x. See the full day-by-day schedule for the granular daily volumes.
| Week | Daily volume | Audience mix |
|---|---|---|
| Week 1 | ≤20/day | Known contacts only, plain text |
| Week 2 | 20–50/day | Known contacts, small warm list |
| Week 3 | 50–100/day | Warm list + small cold slice |
| Week 4 | 100–150/day | 30–40% cold mix |
| Week 5 | 150–300/day | Increasing cold, monitor bounces closely |
| Week 6+ | 300–500+/day | Normal production mix |
Hold the ramp flat — do not accelerate — whenever any of these signals appear: hard bounce rate above 2%, spam complaint rate above 0.1% in Postmaster Tools, or Gmail Postmaster domain reputation dropping to “Low”. Hold flat for 5–7 days, diagnose the signal, fix the cause, then resume at the last stable volume.
Audit your domain before the first ramp step
Paste your sending domain into the free warm-up checker — it resolves SPF, DKIM, DMARC, and MX and returns a 0–100 warm-up readiness score plus 3–5 plain-English findings.
Run the free warm-up checker →Seed-List Sourcing
A seed list is a curated set of real mailboxes — typically 10–30 — spread across the providers you care about most. Before any production send, you send your actual template to the seed list and read the folder the message lands in: Primary, Promotions, or Junk. That folder verdict is the sharpest pre-send inbox signal available because it uses real recipient inboxes, not synthetic probe accounts that providers route differently.
Provider coverage to aim for
- Gmail personal — the largest single inbox pool; Primary vs Promotions split here is your benchmark.
- Google Workspace — enterprise Gmail; often stricter than consumer Gmail on unknown senders.
- Outlook.com / Live.com — consumer Microsoft; SNDS colour is the matching reputation signal.
- Microsoft 365 — enterprise Microsoft; PTR and DKIM alignment matter most here.
- Yahoo — consumer Yahoo; complaint rate at Yahoo is a leading indicator of Postmaster decline at Gmail.
Build the list from real accounts you control or from colleagues willing to participate — do not use synthetic probe accounts that providers treat differently. Run your actual template (including links, HTML, and images) to the seed list, not a stripped-down version — the verdict for a different template is not the verdict for your production send.
Engagement Signals
Provider reputation algorithms weight engagement signals differently, but the hierarchy is consistent enough across Gmail and Outlook to guide a warm-up plan. See how Gmail and Outlook score the signals in depth.
Strongest positive: replies and inbox moves
A reply is the highest-quality positive signal at both providers — it signals that the recipient expected the message and wanted to engage. Moving a message from Junk to Inbox is the single most powerful positive signal; it is a direct vote that the recipient trusts the sender. During weeks 1–2, prioritise contacts who you are confident will reply or move messages out of spam, not contacts you are hoping will open.
Strong positive: opens
Opens are the second-strongest positive signal and the easiest to track via Postmaster Tools' domain reputation curve. A domain whose warm-up volume is driving consistent opens — even at 30–50 per day — accumulates reputation faster than a domain sending 500 per day with low open rates.
Strongest negative: spam complaints
A spam complaint rate above 0.1% in Gmail Postmaster Tools triggers throttling almost immediately during warm-up. A domain with a complaint rate above 0.3% can see its Postmaster reputation drop from Medium to Low within the same reporting window. Complaints are irreversible in the short term — a complaint logged at Gmail stays in the scoring window for weeks.
ISP-Specific Quirks
Generic warm-up guides treat all providers as identical. In practice, Gmail and Outlook score different signals at different weights, and a plan optimised for one can produce sub-par results at the other if these quirks are ignored.
Gmail
Gmail weighs domain reputation more heavily than IP reputation during early warm-up. A new domain starts at a “Low” or “Medium” reputation band in Postmaster Tools and moves toward “High” as engagement accumulates on that domain — not on the IP. The 0.1% complaint threshold is treated as a hard ceiling: crossing it during warm-up can reset the domain to “Low” and require the ramp to restart from lower volumes. Gmail also requires DMARC at any policy level before the domain reputation data begins populating in Postmaster Tools — a domain without DMARC is sending blind. Check your DMARC record →
Outlook
Outlook weighs IP reputation (tracked in SNDS) alongside DKIM alignment at the receiving hop and PTR presence. A new IP without a PTR record is immediately yellow-banded in SNDS regardless of domain reputation or authentication. A PTR that resolves but has no forward-confirmed A record (FCrDNS) is treated the same as no PTR. JMRP (Junk Mail Reporting Program) complaint data feeds heavily into the SNDS colour band during warm-up — a complaint rate spike at Outlook.com during week 2 can yellow-band an IP that was green the week before. Validate your SPF and auth chain before ramping at Outlook: check SPF →
Validate the auth chain before ramping
Missing SPF or DMARC prevents Gmail from populating Postmaster data and triggers yellow-band classification at Outlook. Run the free validators before any volume send.
When to Pause
Pausing at the right time is the difference between a temporary signal correction and a full reputation reset. Pause whenever any of four signals breach their threshold:
- Hard bounce rate above 2%. A list quality problem. Stop sending to the segment that produced the bounces, clean the list, and validate remaining addresses before resuming.
- Spam complaint rate above 0.1%. A content or audience problem, visible in Gmail Postmaster Tools. Pull back immediately — the scoring window for complaints is rolling, not daily, and the damage compounds with every additional send at that rate.
- Gmail Postmaster domain reputation dropping to “Low”. A systemic signal that the engagement ratio on recent sends has crossed a negative threshold. A single day of Low is a warning; two or more consecutive days requires a pause and audit.
- Sudden undelivered spike from a single provider. An ISP-specific block or rate limit. Stop volume to that provider, check your SNDS or Postmaster data for the specific signal, diagnose before resuming.
After a pause, hold volume flat for 5–7 days and confirm the triggering signal has returned to a safe range before resuming. Resume at the last stable volume — not from the weekly target that produced the breach.
Blocklist Exposure During Warm-Up
A warm-up plan that focuses only on volume and engagement can miss a blocklist listing until it shows up as a bounce wave. Several major DNSBLs — particularly Spamhaus XBL and Barracuda BRBL — list based on observed send patterns, and a new IP on a shared ESP pool can arrive pre-listed because a previous tenant on that pool had poor reputation.
Run a free blocklist check before the first warm-up send and at the start of each new ramp week. If a listing appears during the warm-up window, pause immediately, diagnose the listing reason, and follow the per-list delist workflow before resuming. A listing that arrives during week 2 warm-up and is left unaddressed will compound into a Postmaster domain reputation problem by week 3. The blocklist removal guide covers the per-list delist workflow in full.
Related Guides and Tools
- Blocklist Removal Guide → — The per-list delist workflow for every major DNSBL.
- Email Warm-Up Schedule → — Day-by-day granular volumes for the full ramp.
- Sender Reputation Guide → — How Gmail, Outlook, and Yahoo score your sending domain.
- Free warm-up checker → — SPF, DKIM, DMARC, MX, and a 0–100 readiness score.
- DMARC checker →
- SPF record checker →