Why warm up a domain at all?

A brand-new domain has no sending history, and mail filters treat "no history" as something close to "bad history." Until mailbox providers have watched a domain send real mail — steadily, and without complaints — they have no reason to trust it and several reasons to block it. Warming up is the fix: deliberately starting at low volume and increasing on a controlled curve, so filters observe a legitimate pattern before the domain carries mail that matters.

Unknown is not neutral

The clearest statement of the cold-start problem comes from M3AAWG, the cross-industry body where senders and mailbox providers write joint best practices: reputation usually starts as unknown, which "makes it similar to bad," because there is no positive history to weigh. A domain with history lets a filter judge behaviour over time. A domain without history gets extra scrutiny by default.

That default is rational, not spiteful. Spam filters are asymmetric-cost systems: letting one spam message into an inbox is cheap, while putting wanted mail in the spam folder is expensive — but largely invisible to the provider. Faced with zero information about your domain, caution is the correct bet, and every major filter makes it.

What happens to campaign #1 from a cold domain

Sending a real campaign from a domain with no history triggers several distinct failure modes, roughly from worst to mildest:

Outright rejection, if the domain is very new. Spamhaus operates a Zero Reputation Domain list that catches newly registered domains, and deliverability practitioner Al Iverson puts it bluntly: providers subscribing to the full Spamhaus suite will reject mail from a domain less than 24 hours old, and he recommends aging a domain at least 30 days before commercial sending. Spamhaus itself says most threat-intelligence companies flag a newly registered domain for roughly its first 30 days. We cover the mechanics in why new domains get blocklisted, and you can check your domain against the major blocklists before you start.

Volume anomaly detection. Google's sender guidelines tell senders to start with low volume to engaged users and to avoid sudden spikes without a history of large sends. A domain whose entire observed history is zero emails per day, suddenly emitting hundreds in an hour, is statistically indistinguishable from a compromised domain — because that is exactly what a compromised domain looks like.

Less benefit of the doubt, not more. Google's bulk-sender FAQ notes that enforcement for new domains runs on an accelerated timetable. A cold domain gets fewer chances than an established one, not a grace period.

Nothing on the positive side of the ledger. Modern reputation systems are engagement models more than volume models. With no opens, replies, or spam-to-inbox rescues on record, there is nothing to offset the negative prior — every judgment call goes against you.

None of this means a single early trip to the spam folder is fatal. Iverson also notes that some spam placement during warming is normal and not by itself a failure signal. The point of warming is to keep those early judgments low-stakes: better that a filter's first opinions form over a handful of quiet, well-behaved messages than over your launch announcement.

What a warmed sending history changes

M3AAWG splits reputation-building into two phases: a warm-up phase that takes a domain from unknown to noticed, then a ramp-up phase that grows it toward planned long-term volume. After a domain has been through that, three things are different:

• Filters have a prior, and it is positive. There is now observable history — consistent volume, authenticated mail, no complaint spikes — so a new campaign is judged against a track record instead of against nothing.
• The pattern itself vouches for you. The same Google guidelines instruct: "Send email at a consistent rate. Avoid sending email in bursts." A smooth, gradually rising curve is precisely what legitimate new senders look like, and precisely what compromised domains do not.
• The reputation is portable. Mailgun (updated March 2026) makes the durability argument: senders change IPs many times but rarely change domains, so domain reputation follows you across providers and infrastructure. Resend makes the same point — domain reputation reflects you, not your infrastructure. This is also why warming applies even on shared IPs, which is where almost every Resend, Postmark, or SendGrid customer sits: the IP is already warm; your domain is not.

Two honest limits. First, warming is a pacing mechanism, not a laundering mechanism. Laura Atkins of Word to the Wise is unambiguous that you can only warm a sending identity to the reputation of the mail it actually sends — if the mail is unwanted, no schedule saves it. Second, "warmed" is not permanent: SendGrid's guidance is that most reputation systems only store about 30 days of data, so a domain that goes quiet for a month slides back toward unknown.

How long this takes

Published guidance clusters tightly. M3AAWG suggests six weeks of warm-up as an average; Postmark says most senders reach dependable full-volume deliverability in three to six weeks; SendGrid reports 30 days as typical with some senders taking up to 60; and Iverson has seen five to eight weeks in practice. The dominant variable is target volume — reaching a modest daily volume takes far less time than ramping to hundreds of thousands per day. How long to warm up an email domain works through the schedule-by-schedule evidence.

WarmEnvelopes automates the mechanical half of this: steady daily sends from your domain, through your own Resend account, to inboxes you control, on a ramp you choose — with every send logged. It does not fake opens or replies, and no warmup service, ours included, can guarantee inbox placement. What it builds is the thing filters check first: a sending history. How the daily volumes are calculated is covered in the ramp-up schedule.