Warm-up is a controlled production ramp governed by receiver feedback. It is not a calendar date, a dashboard score, or a permanent certificate.
The word warm is used too loosely in outbound email.
It can refer to the age of a mailbox, the reputation of a sending domain, the history of an IP address, a gradual increase in production volume, or automated messages exchanged inside a warm-up network. Those are different things. Treating them as one score creates false confidence.
Current guidance from Google, Yahoo, Microsoft, Amazon SES, and Azure Communication Services still supports gradual, consistent introduction of legitimate mail. The same guidance focuses on authentication, recipient quality, complaints, bounces, volume patterns, and receiver responses. It does not provide a public rule saying that an idle mailbox becomes trusted with age or that automated opens and replies transfer reputation to a real campaign.
"Inbox warm-up" is convenient shorthand, but the receiver evaluates a message connected to several identities and behaviors: the authenticated domain, the sending IP or shared pool, traffic patterns, message content, URLs, recipient feedback, and the mailbox provider's own history with the sender.
Google documents separate domain and IP reputation signals. Yahoo says it considers IP, URL, domain, sender, ASN, DKIM, and DMARC information. Microsoft's Dynamics 365 Customer Insights - Journeys warm-up guidance separately discusses domain and sending-IP reputation alongside complaints, bounces, authentication, blocklists, spam traps, and engagement. Google Yahoo Microsoft
The exact models and weights are not public and they differ by receiver. The documented point is that reputation attaches to several identities and behaviors, not to one mailbox.
Architecture matters here. A sender with a dedicated IP can introduce traffic on that IP. A sender on a shared or rotating pool does not control the whole IP history; the provider manages that part of the system. The domain, authentication, list, content, and recipient response still belong to the campaign.
Google tells senders to start with low volume, increase gradually, avoid bursts and sudden spikes, and watch SMTP responses, spam rates, and domain reputation. Azure Communication Services recommends increasing volume gradually while monitoring delivery status, and its quota guidance specifically refers to legitimate production workloads. Amazon SES defines warming up as gradually increasing the amount of email sent from a new dedicated IP address before using it at full capacity. Google Azure service limits Azure quota guidance Amazon SES
Yahoo and Google both warn about sudden changes from an established sending pattern. Amazon SES makes the same point for new dedicated IPs. Yahoo Google Amazon SES
None of those receiver sources publishes a universal low-volume B2B schedule. The sending platforms cited here do publish their own ramp schedules and time ranges, but those are platform recommendations for their own IPs, not receiver rules. A chart that says every inbox should send a fixed number on day three, seven, or fourteen is a vendor's operating recommendation, not a receiver standard.
A two-week schedule may be useful internally, but none of the receiver guidance cited here publishes a rule saying a mailbox becomes trusted after two weeks.
For dedicated IPs, Amazon SES says that after warm-up a sender should keep sending roughly 1,000 messages a day to each provider where it wants to maintain reputation, and SendGrid says an IP that has been idle for more than 30 days should be warmed again. Amazon SES SendGrid
Those are IP-level recommendations, not universal mailbox-aging rules. A one-time warm-up does not establish permanent reputation.
Instantly says its warm-up pool exchanges messages among participating accounts, automatically opens the messages, replies to a percentage of them, and moves warm-up messages out of spam. Smartlead describes automated sending, opening, spam-folder recovery, and replies inside its pool. Instantly, accessed September 3, 2026 Smartlead, accessed September 3, 2026
Those vendor pages describe the activity. The Google, Yahoo, Azure Communication Services, and Amazon SES guidance cited here instead recommends authentication, expected or engaged recipients, controlled production volume, complaint control, and attention to SMTP feedback. Those pages do not present reciprocal automated engagement as a substitute for production traffic. Google Yahoo Azure Communication Services Amazon SES
Ask a warm-up vendor for controlled production-campaign outcomes, not the open and reply rates inside its own network. The relevant evidence is what happens to replies, complaints, deferrals, and placement after production traffic begins.
Google and Yahoo tell marketing and bulk senders to send to recipients who asked for the mail or opted in. Microsoft's Dynamics 365 Customer Insights - Journeys guidance similarly says opt-ins are the most important factor and recommends warming with engaged subscribers. Automated warm-up traffic does not change the production list or how recipients react to the campaign. Google Yahoo Microsoft
Gradual sending does not correct SPF, DKIM, DMARC, or DNS errors.
Google requires SPF or DKIM for all senders to personal Gmail and adds SPF, DKIM, DMARC, and alignment requirements for higher-volume senders. Yahoo has parallel authentication requirements. Microsoft's Outlook.com guidance says senders of 5,000 or more messages to Microsoft consumer email services from the same 5322.From domain must pass SPF and DKIM, publish a DMARC record, and pass DMARC alignment. Microsoft's April 2025 announcement describes the threshold as more than 5,000 emails per day. Google Yahoo Microsoft requirements Microsoft announcement
The published thresholds trigger specific enforcement. Authentication still matters below them. A campaign should have correct SPF, DKIM, DMARC, alignment, forward and reverse DNS where applicable, and a working reply path before production traffic begins.
Authentication proves particular technical facts about the message. It does not guarantee inbox placement.
Google says it began ramping enforcement against noncompliant traffic in November 2025, including temporary and permanent rejection. Its error documentation lists low IP reputation, low domain reputation, likely unsolicited mail, rate limits, and authentication problems as reasons mail can be restricted or blocked. Google sender FAQ Google SMTP errors
Microsoft documents authentication requirements for high-volume senders to Outlook.com consumer services. Separately, for organizations sending from Microsoft 365, it documents outbound controls that restrict accounts for suspicious sending patterns, spam, and excessive volume. Microsoft Outlook requirements Microsoft outbound protection
Those systems are working against unwanted, unauthenticated, suspicious, and noncompliant traffic. The cited guidance continues to support controlled ramping. A warm-up score cannot compensate for the real campaign's authentication, list, volume, complaints, or content.
Use SMTP responses and receiver-specific delivery data to decide whether to increase volume.
Before traffic begins:
During the ramp:
Google and Amazon SES both tell senders to reduce volume when bounces, deferrals, or blocking notices rise. Yahoo tells senders to monitor hard and soft bounces and remove invalid recipients. Google Amazon SES Yahoo
Do not begin production traffic until authentication, bounce handling, replies, complaint processing, and unsubscribe processing work end to end. Start with restrained, representative campaign traffic. Stop on clustered authentication or policy failures. Reduce the affected receiver stream when deferrals rise. Suppress addresses when SMTP evidence confirms an invalid recipient, and enforce unsubscribe and complaint suppression independently. Increase volume only after receiver signals remain stable across consecutive send windows.
Warm-up cannot fix:
Use warm-up to introduce production traffic gradually and monitor receiver feedback. It cannot protect a campaign from broken authentication, poor data, unwanted messages, or abrupt volume changes.
Size domains and density to your sending target and see the capacity that holds.
Book a Call