Mailbox warm-up ramp schedules

Treat a mailbox warm-up schedule as a control loop with explicit gates. Start with a small, receiver-aware load, raise it only while delivery and complaint signals hold, and pause when they worsen. Gmail, Yahoo, and Microsoft do not publish a universal 28-day mailbox schedule or certify warm-up networks,¹ so use any calendar as a baseline that must answer to the mailbox's behavior.

Set the starting conditions

Start by defining what you are warming and where the mail will go. The schedule works per sender identity, while the receiver mix tells you where a change may appear first.

Warm-up means gradually establishing sending history from a new or inactive setup.² The first move is to examine who will receive the mail and how much you plan to send.³ Break the total down by receiver wherever possible, including Gmail, Yahoo, AOL, Microsoft domains, and other recipient providers.⁴ That breakdown gives you a way to see whether one provider reacts differently from the rest.

Authenticate before you start. For mail sent to personal Gmail accounts, all senders need SPF or DKIM.⁵ Activate sender identities separately. Warming each identity carefully is recommended, while activating the whole team on the same day creates a sudden change in sending behavior.⁶

Build the ramp

Pick a schedule that gives reputation and delivery time to respond. A two to four week gradual increase with close delivery monitoring is one defensible starting range.⁷ The gradual change gives sender reputation time to settle while preserving delivery reliability.⁸

A detailed Microsoft 365 baseline starts at 10 to 20 daily sends with warm-up traffic only, moves to 20 to 40, then 40 to 60 with 10 to 15 cold sends, then 60 to 80 with 20 to 30 cold sends, and settles at 30 to 50 cold sends per day while keeping each inbox at or below 50 cold sends.⁹ Use that as a path you can slow down or hold, not as permission to increase volume on schedule.

For a slower account-level plan, start at 5 to 10 sends per day, increase by roughly 30% to 50% per week, and allow 4 to 6 weeks for most accounts.¹⁰ Choose the slower path when the target volume is high, the old setup has a longer runway, sending happens infrequently, or engagement is low. A low-volume program with strong engagement may support a quicker ramp.¹¹

Keep the daily pattern steady. Providers reward senders that increase volume gradually and behave consistently.¹² The point of the schedule is to make each increase small enough that you can identify what changed when delivery shifts.

Gate each increase

A ramp should tell you when to move, when to hold, and when to step back. Read the signals before releasing the next increase, not after the mailbox has already absorbed it.

Use reply rate as a directional signal, keep spam complaints below 0.10%, and keep bounces below 2%.¹³ Those measures determine whether the ramp is working. Review bounces, deferrals, complaints, and reputation as part of the same check, then reduce volume when those signals worsen.¹⁴

Advance only when the current level has stayed stable across the receivers you are watching. If Gmail performance weakens while other receivers look healthy, hold the increase and inspect that receiver's portion of the list. The receiver breakdown from the starting step gives you the comparison you need.

During the ramp, keep warm-up sends ahead of cold sends.¹⁵ When you add cold traffic, make sure it remains a smaller part of the day's total until the mailbox has earned the next increase through stable signals.

Adjust the schedule to the mailbox

The same calendar will behave differently across mailboxes. Let the target workload, sending rhythm, and engagement decide how much room each step needs.

Slow the ramp when the mailbox is moving toward a high target volume, sends happen only a few times a month, engagement is low, or an older setup gives you a longer runway. A low-volume or highly engaging email program may support a faster increase.¹¹ Keep the rate consistent once you choose a pace, since gradual and consistent behavior is rewarded by providers.¹²

Treat the schedule as one part of sender reputation. Authentication, recipient expectations, complaint rates, content, infrastructure, and sending history also affect how providers handle mail.¹⁶ A clean ramp cannot compensate for poor recipient selection or unwanted messages.

What not to do

Avoid shortcuts that make the schedule look complete while hiding the signals that should control it.

• Do not create spikes in sending volume during the ramp, even when you have planned percentage increases.¹⁷
• Do not rely on synthetic reply loops as proof that the mailbox is ready. Google and Microsoft have become better at discounting obviously synthetic reply loops.¹⁸ Use automated warm-up networks as a supplement to the main sending plan.¹⁹
• Do not treat a warm-up tool as a substitute for permission, list hygiene, authentication, or provider compliance.²⁰
• Do not change a sending domain without rechecking the schedule. Domain changes influence email, and an incorrect change can send messages to the spam folder.^{21, 22}

Set a baseline for each sender identity, write the signals that control the next increase beside it, and inspect delivery by receiver before you move on. When the signals weaken, use the hold rule and correct the sending conditions before raising volume again.