Resend’s new product launch plan ran from February 11 to March 24: six weeks to introduce three sending domains before a launch targeting thousands of emails a day. That timeline shows the value of planning around real message types and audiences. This email domain warm up guide gives you a sample ramp with actual volumes, plus distinct operating guidance for campaigns and transactional mail.

Email domain warm up is a gradual increase in legitimate sending from a domain with little or no sending history. Authenticate first, start with wanted messages to engaged recipients, and expand in measured steps while monitoring provider responses, bounces, and complaints. The schedule should reflect your traffic and audience; transactional messages should still go out when users need them.

What email domain warm up is—and what it is not

Warmup is the controlled introduction or growth of legitimate email from a sending identity. Inbox providers such as Gmail and Yahoo evaluate sending patterns and recipient responses over time. A steady flow of expected mail gives them a real record to assess; artificial opens and replies do not create the same evidence as mail recipients actually want.

Three kinds of reputation are often confused:

  • Domain reputation relates to the domain or subdomain used in sending and the mail associated with it. A new sending domain begins without an established history of its own.
  • Mailbox reputation concerns an individual address or mailbox. It is especially relevant to one-to-one outreach sent from personal-looking inboxes.
  • IP reputation relates to the IP address connecting to receiving providers. A new IP can have little history even when the domain has sent mail before.

These assets can have different histories. For example, a company can keep its established domain while moving to a new sending IP, or use a new subdomain through an IP with a longer track record. Plan for the domain, mailbox, and IP changes separately rather than treating “warmup” as one switch.

Warmup is not simply waiting for a domain to age. A domain that sits unused does not accumulate a record of wanted email. Resend’s launch team, for example, gradually sent to engaged early users as it prepared its new.email product; the value came from controlled, real sending rather than elapsed time alone.

When a domain needs warmup

A measured ramp is useful when you introduce a new sending domain, resume a dormant stream, increase volume substantially, or change sending infrastructure. It is also useful when a migration changes the visible From domain, authentication alignment, IP, traffic mix, or expected daily volume. First identify which of those things is changing; an established sender does not need to restart from zero just because it is making a small operational change.

A newly purchased domain does not inherit a reliable sending record from a similar brand name or an older registration date. Treat a new sending identity as a new asset. By contrast, an established domain sending consistent mail to people who expect it can usually maintain its pattern while a migration is assessed and monitored.

Before choosing a schedule, record the current and planned state:

  1. Which From domain or subdomain will recipients see?
  2. What is the normal daily volume, and what is the target peak?
  3. Which messages are transactional, campaign, or one-to-one outreach?
  4. Are the domain, IP, provider, or recipient mix changing?
  5. Which recipient providers account for the largest share of your messages?

Resend’s launch example is useful because the team planned backward from a real date and a real product. It wanted capacity for thousands of messages a day, had three message types, and began the ramp on February 11 for a March 24 launch. Its six-week plan was connected to those launch conditions, not a template every sender should copy.

Set up authentication and sending infrastructure first

Set up authentication and monitoring before raising volume. SPF identifies authorized sending services, DKIM adds a domain-linked signature to messages, and DMARC lets domain owners set a policy and receive reports about authentication alignment. Confirm the records against actual received messages and make sure the visible From address matches the identity you intend to build.

Use this preflight before the first meaningful send:

  • SPF: authorize the service that sends your mail and keep the record for each hostname correctly configured.
  • DKIM: enable signing for the sending identity and confirm that a received message passes the signature check.
  • DMARC: publish a record for the relevant domain and review alignment between the visible From domain and SPF or DKIM.
  • Sending identity: verify the sending domain with your provider and use a recognizable From name and address.
  • Bounce and complaint handling: capture failures, suppress hard bounces and complaints, and preserve suppression data during migrations.
  • Campaign unsubscribe: make it easy for recipients to stop campaign mail, and ensure the unsubscribe action is processed by your sending system.
  • Monitoring: confirm you can see provider responses, delivery errors, bounces, and complaints before you expand.

For campaigns, list quality and recipient expectations belong in the preflight too. Resend used double opt-in for early access: a signup first received a confirmation request, and only confirmed addresses joined the list. That reduced mistyped or unwanted addresses in the early batches. Our guide to automatic email opt-in and deliverability risks explains why signup design affects list quality.

With Amazon SES, identify whether you send through shared or dedicated IP infrastructure. IP warmup concerns the IP’s sending history; domain warmup concerns the sending identity. At Volanea, mail is sent through shared Amazon SES infrastructure, and we do not offer dedicated IPs. Our guided domain setup covers SPF, DKIM, and DMARC and checks the setup automatically.

A practical email domain warm up schedule

The schedule below is a worked example for a new campaign subdomain and a confirmed, opted-in audience of 1,000 people. It illustrates how to expand in increments while keeping the first sends focused on engaged recipients. The quantities are a planning example, not a quota to apply to every list or provider.

PeriodExample campaign volumeAudience and decision
Days 1–250 totalSend to the most recently confirmed and engaged recipients. Review bounces, complaints, and provider responses before the next batch.
Days 3–475 per dayThis is a 50% increase over the initial 50-recipient batch. Continue only if the first batch produced healthy signals.
Days 5–7110 per dayThis is about 47% above 75. Add the next most engaged segment, not an older or unverified list.
Week 2160 per dayIncrease by about 45% after reviewing the first week’s results. Keep message type and audience characteristics consistent.
Week 3230 per dayIncrease by about 44% if provider feedback, bounces, and complaints remain healthy. Keep the remaining audience for later batches.
Week 4Up to 330 per dayThis is about 43% above 230. At this point, compare actual outcomes with the volume you need and continue in measured steps.

The schedule leaves part of the 1,000-person list untouched during the first week. That is deliberate: early batches go to people most likely to recognize the sender and want the message. If a batch produces rising hard bounces, complaints, or repeated deferrals, hold at the last stable level or reduce volume while investigating. Do not advance simply because a day or week has passed.

For a smaller audience, reduce the batch sizes while keeping the same sequence of review and controlled expansion. For a larger target, extend the plan and add intermediate steps. Keep a change log with the date, domain, audience segment, volume, and provider response; that makes it easier to identify which change preceded a delivery problem.

Transactional traffic follows a different schedule. Do not delay a password reset or receipt to fit the table. Send the messages that real user activity triggers, then monitor their normal pattern. The table is for controllable campaign volume, where you can select a smaller first audience and decide when to send the next batch.

How to warm transactional email differently from campaigns

Transactional email is initiated by a user or product event. Password resets, receipts, account confirmations, and security notifications should arrive when they are needed. Do not manufacture these messages or hold them back to create a gradual ramp; instead, make sure the product sends only legitimate events and that your system handles expected traffic reliably.

Campaigns are scheduled, so the sending team can control volume and recipient selection. Begin with recent, confirmed subscribers or people who have recently engaged. Expand to the next most relevant segment after reviewing the first sends. An old contact export is not equivalent to a current, permissioned audience, even if the file is large and easy to upload.

Separating traffic by subdomain can make operations clearer. For example, notify.example.com might identify product notifications while news.example.com is used for campaigns. This lets teams observe each stream and manage its audiences and suppression rules distinctly. It does not replace consent or monitoring, and it does not make campaign complaints irrelevant to the sender.

Volanea brings transactional sending, campaigns, and automations together through one API. Its sending pipeline handles suppression checks, contact upserts, template rendering, tracking, and delivery, while the platform also supports segments for audience selection. A team can, for example, target a confirmed campaign segment in controlled batches while keeping password-reset events on their normal product trigger. Our behavior-based welcome email sequence guide covers using real user actions to shape follow-up messages.

One implementation detail matters when testing: Volanea sk_test_ keys render and log messages but never deliver them. Use them to exercise template and application behavior; use a live project key and a verified domain when you need to observe actual sending to real recipients. Volanea lets users send to real recipients after verifying the domain without requesting Amazon SES production access. The REST API documentation describes 92 endpoints across sending, contacts, templates, campaigns, segments, webhooks, and suppressions, which gives teams API-level control over the parts of a ramp they need to automate.

What to monitor—and when to pause the ramp

Review outcomes after every meaningful increase, not just at the end of a month. Focus on hard bounces, spam complaints, temporary deferrals, delivery errors, and provider feedback. Inbox placement can also be useful when you have a reliable way to measure it, but open rates alone are a weak basis for deciding whether to expand.

Google Postmaster Tools can provide domain-level reputation and spam-rate information for eligible Gmail traffic. Use provider-specific dashboards alongside your own sending logs: a trend in complaints or blocks is more useful than an isolated open-rate change. Yahoo is another major recipient provider, so keep its response patterns in view if it accounts for a meaningful part of your audience.

Use a clear operating response:

  • Pause expansion when complaints rise, hard bounces increase sharply, or a provider begins deferring or rejecting messages.
  • Investigate the affected stream by checking response codes, authentication, recent audience changes, message content, and the source of the addresses.
  • Correct the cause by suppressing invalid or complaining recipients, repairing configuration, or narrowing the campaign segment.
  • Resume at a controlled level after the underlying issue is addressed and the affected signals have improved.

A reputation guard can add a useful control in this workflow. Volanea’s reputation guard slows sending before a bad list hurts a domain, helping prevent a campaign from continuing at full pace when list quality is deteriorating. Automated controls work best when teams still review the audience and provider feedback that prompted the slowdown.

Common warmup mistakes and misleading shortcuts

The first mistake is treating activity as the goal. A warmup tool that fabricates opens, clicks, or replies does not establish that real recipients want your messages. Use actual product-triggered traffic and permissioned campaign audiences; engagement should come from the people the email is meant to reach.

Other avoidable errors include:

  • Jumping from a small trickle to a large blast. A sharp change makes delivery outcomes harder to predict and troubleshoot. Use a staged ramp and keep reviewing each step.
  • Starting with stale or unverified addresses. Aged lists can contain invalid addresses and people who no longer expect mail. Start with the strongest, most recent audience.
  • Ignoring complaints or unsubscribes. Suppress those recipients and examine the signup source, targeting, and message expectations.
  • Combining unrelated traffic without visibility. A campaign and a password reset have different triggers and audiences. Track them as distinct streams even when they share a platform.
  • Following a fixed day count instead of recipient signals. Hold or reduce sending when provider responses deteriorate, even if the calendar says the next step is due.

The “60/40 rule” is commonly used to describe a suggested ratio of text to images in an email. It is not a universal deliverability rule, and meeting a ratio does not replace sound authentication, relevant content, or a wanted audience. Likewise, a “pre-warmed email” may refer to an aged domain, an aged mailbox, or an identity with sending history; ask which asset was used and whether that history belongs to the exact identity and infrastructure you plan to send from.

How long warmup takes, and what happens after it

How long does email warmup take? Resend’s example lasted six weeks, from February 11 to a March 24 product launch, and involved three domains and several message types. That is a concrete reference for a planned launch, not a duration to copy automatically. Your ramp length follows the volume you need, the condition of the audience, and the results of each sending step.

A practical completion point is when you can send the intended volume consistently, authentication passes, and provider feedback and recipient responses remain healthy. After the initial ramp, maintain a steady cadence, keep lists clean, carry suppressions forward, and make later volume changes in steps. Warmup is an operating practice, not a one-time configuration task.

For teams considering Volanea, every feature ships on every plan; plans differ by monthly volume and domain count. Sending pauses at the monthly limit, with no overage billing. The free plan includes 1,000 emails or credits each month; Starter is $5/month for 7,500 emails, and Growth is $20/month for 50,000 emails. Those volumes can help a team test a real application workflow or start a small campaign before choosing a larger monthly allowance.

FAQ

What is the 60/40 rule in email?

It is a content-mix suggestion, usually describing the proportion of text and images in an email. Treat it as a creative guideline rather than a provider requirement. For a warmup, recipient expectation, authentication, list quality, and actual delivery feedback are more useful decision signals than a text-to-image ratio.

What is a pre-warmed email?

The phrase can describe an aged domain, a mailbox with sending history, or an account that has sent mail before. Ask what exactly was warmed and whether it is the same domain, mailbox, and IP you will use. An old mailbox does not give a separate new sending domain an established record.

How is domain warmup different from IP warmup?

Domain warmup builds sending history associated with a domain or subdomain; IP warmup builds history associated with the sending IP. One can be new while the other is established. With Amazon SES, identify whether your traffic uses shared or dedicated IP infrastructure so you know which IP history applies to your setup.

What should I do if a campaign performs badly during the ramp?

Stop expanding that campaign and inspect its hard bounces, complaints, provider responses, and audience source. Suppress invalid addresses and recipients who complained, then retry with a smaller, recently confirmed segment after correcting the likely cause. Keep transactional messages tied to real user events flowing normally rather than using them to compensate for the campaign result.

Start free with 1,000 emails a month. Volanea includes campaigns, automations, and transactional email in one API, with sending paused at the monthly limit rather than billed as an overage. Create a free account.