Email warm-up

How email warm-up works

Mailbox providers expect new senders to look new. A domain with no history that suddenly emits thousands of cold messages trips rate limits and spam filters. Google's sender guidelines tell operators to increase sending volume gradually and to monitor delivery in Postmaster Tools while they do it 1. The same page warns that suddenly doubling prior volumes can cause rate limiting or reputation drops 1.

Warm-up is that gradual increase written into an operating plan. Day one might be dozens of messages to engaged recipients. Later days step up while spam rate, bounces, and authentications stay clean 1. There is no single universal calendar that every ESP agrees on. The principle is consistent: earn trust with positive signals before asking filters to accept a blast.

Authentication belongs on the warm-up checklist on day zero. Google requires SPF or DKIM for all senders to personal Gmail accounts, and bulk senders need SPF, DKIM, and DMARC 1. Warm-up without authentication is a volume ramp on a domain that still looks unverified.

List quality decides whether the ramp helps or whether it hurts. Early hard bounce events teach providers the wrong lesson about the new identity 2. That is why warm-up lists should be the cleanest segment available, not the leftover scrap pile. Running email verification before each volume step removes mxFound false and disposable rows that would otherwise bounce in public 3.

Warm-up also interacts with domain reputation and sender reputation. Postmaster Tools charts for spam rate and domain reputation are the feedback loop during the ramp 1. Google asks senders to keep spam rates below 0.3 percent, and ideally under 0.10 percent 1. If those charts worsen mid-ramp, the correct move is to pause growth, not to push harder.

Shared versus dedicated IP choices change the warm-up shape for the identity. On a shared pool, neighbors affect the same reputation 1. On a dedicated IP, the new identity owns every signal, which makes a careful ramp even more important.

Why email warm-up matters before outbound scale

Outbound calendars create pressure to skip warm-up. A team buys a domain on Monday and wants hundreds of sends on Tuesday. Filters read that pattern as abuse more often than as ambition. The cost shows up as silent spam folder placement that the ESP still labels accepted.

Warm-up also protects the brand domain strategy. Many teams buy a cousin domain for cold email so the product domain stays clean. That cousin still needs a ramp. It does not inherit trust just because the logo matches. Google’s guidance about gradual volume applies to the sending domain that appears in From and authentication alignment 1.

Agencies should put warm-up milestones in the launch plan next to copy approvals. Define daily caps. Define the engaged seed list. Define the Postmaster owner. Define the verification step before each increase. RichAPI Email verifier at 2 credits per verdict is a cheap gate on those waves 3. Misses bill zero 3. New accounts get 100 free credits to rehearse the flow 3.

Warm-up is not a substitute for permission and relevance. A perfectly ramped domain still suffers when recipients mark mail as spam 1. Keep early content closer to expected conversations. Save the coldest experiments for after the domain has a stable baseline.

If warm-up stalls because spam rate climbs, stop the increase 1. Clean the list again. Check authentication. Send only to recent engagers until charts recover. The point of warm-up is controlled learning for the filters. Uncontrolled spikes erase the lesson.

Operators who skip these checks usually discover the damage in reply rate, not in the ESP accept log. The accept log only says the receiving server took the message. It does not say the message reached a person. Closing that gap is the point of the work before the next wave leaves the queue.

Example of warming a new outreach domain before full cadence

A sales team registers getexample.com for outbound and leaves example.com for product mail. On day zero they publish SPF, DKIM, and DMARC at p=none, then enroll the domain in Google Postmaster Tools 1.

Days 1 to 3 send a few dozen messages daily to employees and active customers who already expect mail 1. They watch spam rate and domain reputation after each day 1. In parallel they verify the first wave of cold contacts with RichAPI Email verifier and drop mxFound false plus disposable rows 3.

Days 4 to 10 raise volume in steps while spam rate stays well under 0.3 percent 1. They never jump straight to double the prior day’s volume in one move 1. Only after Postmaster Tools looks stable do full sequences enroll the wider verified list.

Verifier cost is 2 credits per verdict through the cleanup 3. Misses cost zero 3. The 100 free credits on a new RichAPI account cover an early rehearsal of the same warm-up gates 3. The domain reaches working volume without a week-one spam collapse.

Email warm-up vs sender reputation

Warm-up is the ramp process used to earn trust. Sender reputation is the trust score that ramp is trying to build and protect.