Domain warm-up: how to ramp sending volume week by week
A concrete four-week schedule, what to watch at each step, and the rule for when to hold rather than double — which is the only decision in the whole process that actually matters.
Warming a domain is teaching mailbox providers what normal looks like for you. They are watching volume, consistency, and how recipients react. A sender that appears with 40,000 messages on day one looks exactly like a compromised account, because that is what compromised accounts do.
The schedule below is a starting point for a shop with a list in the tens of thousands. The hold rule matters more than the numbers.
Before day one
- SPF, DKIM and DMARC published and verified with real test sends, headers read.
- Bounce and complaint handling wired up and confirmed working. Warming without these is warming a problem.
- Your list sorted by engagement, most recent first. This ordering is the warm-up's main tool.
- Transactional mail on a separate subdomain, so it is not caught up in any of this.
A four-week schedule
- Week 1: 500–1,000 a day, only people who engaged in the last 30 days. Same time each day.
- Week 2: 2,500 then 5,000 a day, extending to 90-day engagement.
- Week 3: 10,000 then 15,000, extending to 180 days.
- Week 4: full volume within your engagement gate. Anybody dormant beyond 12 months stays out permanently, not just during the warm-up.
Send on weekdays at a consistent hour. Do not skip days — a gap followed by a doubled send undoes part of the progress.
The hold rule
Before each increase, check three numbers against the previous step. Any one of these means hold at the current volume for three more days rather than increasing:
- Complaint rate at or above 0.1 %. Google enforces at 0.3 % and recommends below 0.1 %, so 0.1 is the number to act on, not the number to tolerate.
- Hard bounces above 2 %. Stop entirely and verify the list rather than holding.
- Click rate falling materially versus the previous step on a comparable audience. This is the earliest sign of mail moving to the spam folder, and it appears before anything else does.
If two consecutive holds do not clear the numbers, the problem is the list or the content, not the ramp, and increasing volume will make it worse.
Watch providers separately
Reputation is per provider, and an aggregate figure hides the problem. Split delivery, bounce and click rates by recipient domain, at minimum Gmail, Outlook and your largest local provider.
It is entirely normal to be fine everywhere and struggling at one. That is a specific, fixable situation — often authentication alignment or a single provider's sensitivity — and it is invisible in a blended number.
After the ramp
- Keep volume consistent. A sender that does 15,000 a day for a month and then 100,000 for Black Friday will have trouble on the day it matters most. Ramp up ahead of a peak, deliberately, a fortnight early.
- Keep the engagement gate. It is not a warm-up measure, it is permanent hygiene.
- Re-warm after a long gap. A domain silent for two months is not quite a new domain but it is not a known one either.
- Move DMARC to quarantine, then reject, once aggregate reports are clean.
Sources and further reading (4)
- Google — Email sender guidelines
- Yahoo — Sender best practices
- M3AAWG — Sender best common practices
- RFC 7489 — DMARC
Checked on 23 September 2026. Provider prices, mailbox rules and legal guidance change — verify anything you plan to act on.
A ramp that knows who engaged last month
Auralata orders a warm-up by real engagement from your own orders and clicks, so week one reaches the customers most likely to be pleased to hear from you rather than whoever is alphabetically first.
