Warming Up a New Sending Domain Without Hitting Spam
You moved the newsletter to a fresh domain on a Monday, sent 8,000 messages on Tuesday, and by Wednesday Gmail was deferring with a 421 4.7.28 and Outlook was filing the rest in junk.

You moved the newsletter to a fresh domain on a Monday, sent 8,000 messages on Tuesday, and by Wednesday Gmail was deferring with a 421 4.7.28 and Outlook was filing the rest in junk. The copy was the same copy that had worked for three years on the old domain. The only thing that changed was the name in the From line, and that was enough to undo everything.
Warming up a new sending domain means building a sending history on purpose, in small batches, with mail that people open. For a list of around 20,000 addresses it takes four to six weeks. I have watched two teams try to skip that and both spent longer climbing out of a bad reputation than a patient ramp would have cost them. What follows is the sequence I use, including the parts the vendor checklists leave out.
Why a brand new domain starts at zero
Receiving systems do not score a message on one signal. They score the sending IP, the From domain, the DKIM signing domain, the exact subdomain, the link domains inside the body, and the way your recipients have reacted to you before. A domain registered last week has no row in any of those tables, so the filter falls back to the only pattern it can read: an unfamiliar name sending bulk mail at volume. That profile matches a spam campaign almost perfectly.
The first symptoms are soft rather than hard, which is why they get missed. Messages are deferred instead of rejected, and in your sending tool that looks like a queue backing up rather than a verdict. Greylisting holds the first attempt for ten or fifteen minutes. Gmail answers with a 421 and asks you to come back later. Respond by pushing more mail and the filter treats that as persistence and tightens. Hold or reduce volume and it loosens within a day or two.
One detail that surprises people: domain age on its own does very little. A domain you registered two years ago and never sent from is still a cold sender. What counts is delivered mail that recipients opened, replied to, or at least did not report. That is why buying an aged domain off a marketplace solves nothing, and why a domain with a history of someone else's spam is worse than a new one.
Get the records right before the first message
Every message you send before authentication is finished builds reputation against you. Publish all of this, wait for the records to propagate, then send.
- A dedicated subdomain. Send campaigns from something like mail.yourdomain.com and keep staff mail on the root. If a campaign goes badly, your invoices and password resets still land.
- SPF listing only the services that genuinely send for you, kept under the ten lookup ceiling.
- DKIM with a 2048 bit key and a selector you control, signing every stream, including the quiet one your CRM uses.
- DMARC at p=none with a rua address, so reports start arriving on day one without blocking anything yet.
- Reverse DNS on the sending IP if the IP is yours, matching the name the server gives in HELO.
- A List-Unsubscribe header including the one click form. Gmail and Yahoo expect it from bulk senders now, and a visible unsubscribe keeps people away from the spam button.
If those records still read as alphabet soup, our plain walkthrough of how SPF, DKIM and DMARC fit together is the shortest way to understand what each one proves and to whom.
A ramp that actually holds
Volume is the part that is easy to plan. The shape below is where I start for a list of about 20,000, then adjust every morning based on what the reports say. Send on weekdays, at roughly the same hour, and never double a day's volume just because yesterday looked clean.
| Stage | Messages per day | Who receives them | Signal that lets you step up |
|---|---|---|---|
| Days 1 to 5 | 50 to 200 | Staff, plus anyone who replied in the last 30 days | No deferrals, no spam folder reports from colleagues |
| Days 6 to 12 | 500 to 1,500 | Opened something in the last 90 days | Bounce rate under 2 percent |
| Days 13 to 20 | 2,000 to 5,000 | Opened in the last 6 months | Spam rate under 0.1 percent in Postmaster Tools |
| Days 21 to 30 | 8,000 to 12,000 | Opened in the last 12 months | Domain reputation showing medium or high |
| After day 30 | Full active list | Everyone except 12 month non openers | Two clean weeks at the previous step |
Two rules matter more than the exact numbers. Do not increase by more than roughly three times the previous day, and when a provider starts deferring, hold at the current volume for two extra days rather than stepping up on schedule. Expect Outlook and the Microsoft consumer domains to lag Gmail by a week or more; they warm slowly and recover slowly.
Engagement beats the schedule
Most warm up guides hand you a volume calendar and stop there. That is half the answer, and it is the half people get wrong, because a calendar sent to a cold list fails exactly on schedule. The filter is not counting your messages. It is watching what happens after they arrive.
So sort your list by engagement before you sort it by anything else. The first batches should be people who will open: recent buyers, recent repliers, anyone who clicked last month. I want to see those opening above 40 percent. If your week one batch comes back at 6 percent, you have just taught Gmail that nobody wants mail from this name, and you have taught it with your cleanest audience.
This cuts against the instinct to use a new domain for a re-engagement campaign. Mailing people who went quiet two years ago is the single worst content for a domain with no history, and an old purchased list is worse still because it is full of addresses that are now spam traps. Suppress every address that has not opened anything in 12 months until the domain has a month of good behaviour behind it. You can go back for them in February with a reputation that survives the attempt.
What to read each morning
Fifteen minutes a day is enough, and it should become a habit rather than a reaction to a complaint from sales.
- Google Postmaster Tools. Spam rate is the number that matters. Under 0.1 percent is healthy, 0.3 percent is a warning, and anything above that calls for a pause. Domain reputation moves on a delay of a day or two.
- Raw SMTP responses in your logs. A 421 is a deferral and a 550 is a refusal, and they call for different reactions. The enhanced code after it, something like 5.7.1 or 4.7.28, usually names the real reason.
- Bounce classification. Separate invalid addresses from policy blocks. A hard bounce rate above 3 percent in week one means your list hygiene, not your domain, is the problem.
- DMARC aggregate reports. These catch the stream you forgot about, the helpdesk or the billing tool that is sending unsigned. Our guide on reading DMARC aggregate reports without a paid tool covers how to turn those XML files into something readable.
The mistakes that reset the clock
Four weeks of careful work can be undone in one afternoon. These are the ways I have seen it happen.
- A product launch lands in week three and someone sends the full list because the date was fixed six months ago.
- The team changes sending platform halfway through, which changes the IP pool and starts the IP half of the reputation over.
- Transactional receipts and marketing campaigns share one subdomain, so a bad campaign drags password resets down with it.
- Someone rotates the DKIM selector mid ramp without publishing the new key first, and a week of mail arrives unsigned.
- The click tracking domain stays on a cold host, so every link in a warmed message points at an unknown name.
None of these are fatal on their own. All of them cost a week. If you want the records and concepts behind each step in more depth, the rest of our writing on the subject sits in the email infrastructure section.
Frequently asked questions
How long does warming up a sending domain take?
Four to six weeks for a list in the tens of thousands, and closer to two weeks if you send only a few hundred messages a day in total. Very large senders moving a million messages a month should plan on two to three months.
Can a domain be warmed up without a mailing list?
Partly. Transactional mail such as receipts and password resets warms a domain well because recipients expect it and open it. What you cannot do is manufacture engagement with seed accounts that click on your behalf, and the services selling that are gambling your domain.
Should transactional and marketing mail share a domain?
No. Use separate subdomains under the same root so each builds its own reputation. The root domain itself is best kept for person to person mail.
What spam rate is too high during a warm up?
Anything sustained above 0.1 percent should make you hold volume, and 0.3 percent means stop and look at who you are mailing. A single bad day happens; three in a row is a pattern the filter has already noticed.
More in Email Infrastructure
Email Infrastructure
One Click Unsubscribe Headers and the Bulk Sender Rules
I send a monthly note to the people who play on the servers I run. It is not marketing.
Email Infrastructure
Why Email Forwarding Breaks SPF and What ARC Fixes
A reader wrote to me in October about invoices that reached half his list and vanished for the rest.
Email Infrastructure
BIMI Record Setup and Whether Your Brand Logo Is Worth It
You have seen the little brand logos next to sender names in Gmail and Apple Mail, and now someone on your team wants one too.