Domain Warm-Up vs Mailbox Warm-Up: What You Are Actually Warming

You are usually warming three reputations at once: the domain, each mailbox, and sometimes the sending IP. For a new cold-email domain, plan on 2–3 weeks before serious outbound. If you ignore the difference, one layer can look healthy while another still sends mail to spam. This guide shows which signals move each layer and what to fix first.

If you need the DNS side first, use the SPF, DKIM and DMARC cold email checklist before you change volume. Authentication does not create reputation by itself, but missing authentication prevents reputation from being measured cleanly.

What is domain warm up?

Domain warm-up is the process of building a normal sending history for your domain, such as example.com.

Mailbox providers look at the domain in your From address, the domain used in DKIM signing, and the domain that passes DMARC alignment. They compare those signals with recipient behaviour.

A domain with no history is not automatically bad. It is unknown. Your job is to make it look like a real sender over time: authenticated, consistent, low-bounce, low-complaint, and wanted by recipients.

For cold email, this matters because you often use a new domain or subdomain. That domain has no prior sending pattern. If it suddenly sends hundreds of similar messages, filters have little reason to trust it.

A domain can build reputation through:

• SPF, DKIM and DMARC passing consistently.
• Low spam placement across receiving mailboxes.
• Low user complaints.
• Low hard bounces.
• Replies and normal conversations.
• Gradual sending volume.
• Consistent From identity.

Google’s sender guidance says senders should keep spam complaint rates below 0.1%, and avoid ever reaching 0.3%. Yahoo’s sender best practices state a spam rate threshold under 0.3%. Treat those as ceilings, not targets.

Domain warm-up does not mean sending more every day regardless of results. It means increasing volume only while the domain earns neutral or positive handling.

If your domain is new, use a dedicated warm-up period. If the domain is old but has never sent outbound, treat it as new for sending purposes.

What is mailbox warm up?

Mailbox warm-up builds trust for one mailbox, such as alex@example.com.

That mailbox has its own login history, sending rhythm, conversation graph and complaint pattern. A domain can look acceptable while one mailbox performs badly.

This is common in cold outreach. One person sends careful, relevant messages and gets replies. Another sends too fast, uses stale lists and receives complaints. Same domain, different mailbox-level signals.

Mailbox warm-up usually creates normal-looking activity:

• Outbound messages spread through the day.
• Replies from real receiving mailboxes.
• Threads that look like office conversations.
• Spam-folder rescues for warm-up messages.
• Sending caps that rise gradually.
• No sudden jump from zero to campaign volume.

Manual warm-up can work at tiny scale, but it rarely stays consistent. Someone must send, reply, move messages out of spam, and avoid obvious patterns. If you want the trade-off, read manual email warm-up vs automation.

A mailbox is not warmed because it exists inside Google Workspace, Zoho or iCloud. It needs history of its own.

This is why adding more mailboxes is safer than forcing one mailbox to carry all volume. Ten mailboxes sending 30 cold emails each is usually safer than one mailbox sending 300.

Mailbox reputation can also fail for simple access reasons. A locked account, expired app password, disabled IMAP setting or revoked OAuth permission stops warm-up immediately. That is not a reputation problem. It is an access problem.

Where does IP reputation fit?

IP reputation belongs to the server that sends the mail.

With Gmail, Google Workspace, Yahoo, iCloud, Zoho Mail and many hosted mailboxes, you usually send through the provider’s shared infrastructure. You do not control the exact IP. Your main work is domain and mailbox reputation.

With Amazon SES, SendGrid, Mailgun, self-hosted SMTP or a dedicated IP, IP reputation becomes more visible. The receiving provider sees the sending IP and asks whether that IP has a safe history.

A new dedicated IP is like a new domain: unknown. If it sends too much too soon, it can be throttled, bulked or blocked. IP warm-up is the gradual process of proving that the IP sends wanted mail.

Shared IPs are different. You inherit some history from other senders, good or bad. You still need clean domain authentication and good recipient behaviour. A poor domain can perform badly even on a healthy shared IP.

Dedicated IPs make sense when you have stable, permission-based volume. They are not a shortcut for cold email. Low volume on a dedicated IP can be harder to judge because there is not enough signal.

For cold outreach, use this order:

1. Fix domain authentication.
2. Warm the mailboxes.
3. Keep sending volume low.
4. Watch spam placement and bounces.
5. Consider IP reputation only if you control the sending infrastructure.

If you use a platform such as SES, SendGrid or Mailgun, combine provider warm-up rules with mailbox monitoring. See the separate guides for Amazon SES warm-up, SendGrid warm-up, and Mailgun warm-up.

Which signals move each layer?

The layers overlap, but they are not the same. One signal can affect more than one reputation.

A complaint from a recipient can hurt the mailbox, the domain and sometimes the IP. A failed DKIM record mainly affects the domain’s authentication. A sudden SMTP block may be an IP or provider issue.

Use this table when diagnosing a problem.

Google and Yahoo require stronger controls for bulk senders, including authentication and unsubscribe handling. Microsoft also requires SPF, DKIM and DMARC alignment for Outlook.com domains sending over 5,000 messages per day.

Cold email teams should meet these standards even below bulk thresholds. Filters judge behaviour before a sender reaches a formal bulk category.

The most common mistake is fixing only DNS. Passing SPF, DKIM and DMARC is necessary, not sufficient. A perfectly authenticated message can still land in spam if the content, list or sender history is poor.

The second mistake is warming one mailbox, then cloning the campaign to ten new mailboxes. Each mailbox needs its own ramp.

The third mistake is changing everything at once. If you replace the domain, mailbox, sending tool, copy and list on the same day, you cannot identify the cause.

Primary references for the standards above: Google’s Email sender guidelines, Yahoo’s Sender best practices, Microsoft’s Outlook.com sender requirements, and the SPF specification in RFC 7208.

When does each matter?

Domain reputation matters whenever the visible From domain is involved. That is every real campaign.

Mailbox reputation matters whenever a human-looking inbox sends the message. That is most cold outreach, recruiting, founder-led sales and agency outreach.

IP reputation matters when you control or depend on a specific sending IP. That is common with SMTP relays, transactional platforms and dedicated infrastructure.

Here are the usual cases.

A new domain needs domain warm-up first. Do not connect five mailboxes and start campaigns the same day. Publish SPF, DKIM and DMARC. Send small volumes. Build normal activity before prospecting.

A new mailbox on an old domain still needs mailbox warm-up. The domain has history, but that inbox does not. Start low and build sending rhythm.

An old mailbox with a new domain needs both. The mailbox account may have normal login history, but the domain is still unknown.

A new dedicated IP needs IP warm-up. This applies even if the domain is old. Receiving providers judge the IP as a sending source.

A shared SMTP account has mixed risk. You may not control the IP, but your domain and mailbox behaviour still matter. If the shared pool has a poor reputation, authentication will not fully save you.

An account sending newsletters and cold email from the same domain needs caution. Permission-based subscribers and cold prospects behave differently. Complaints from cold outreach can affect broader domain reputation.

For cold email, separate risky outreach from core business email. Many teams use a secondary domain or subdomain. Keep the main company domain for employees, customers and operational mail.

Use this safe warm-up plan

This plan assumes a new domain or a domain with no outbound history. If you already have a healthy sending pattern, you can shorten the timeline, but do not skip the checks.

BobWork Email Warm-up uses a shared warm-up network by default, or a private pool per account if you prefer. The free pool does the repeated mailbox work automatically: it starts at 3 emails per day, adds 2 per day, caps at 30 per day by default, and spreads sends across 09:00–18:00 in the mailbox’s time zone.

That does not replace good campaign practice. Keep real outreach low while the mailbox proves itself. For cold email, a practical ceiling is usually 30–50 real outbound emails per mailbox per day. If you need more, add mailboxes instead of pushing one harder.

New domains deserve more patience. Use a 21-day ramp if the domain has no history. The new domain warm-up guide gives a day-by-day version.

Existing domains can move faster, but only if they already send normal mail and have clean authentication. Seven days is a reasonable minimum before low-volume outbound.

Do not warm up with the exact same copy you will use in campaigns. Warm-up conversations should look like short office mail, not sales templates. Your campaign copy still needs relevance, plain language and a clear reason for contact.

How do you fix the weak layer?

When deliverability drops, do not guess. Work from the lowest layer upward.

Start with DNS. If SPF, DKIM or DMARC fails, fix that before changing copy. A failed authentication layer makes every other diagnosis noisy.

Then check mailbox access. If IMAP, SMTP, OAuth or app passwords fail, warm-up is not running. A mailbox with a blocked login state is not collecting positive signals.

Then check warm-up spam placement. BobWork’s ready gate uses three conditions: at least 7 days warming, a 7-day warm-up spam rate of 10% or less, and at least 30 warm-up emails received. That is a practical signal, not a guarantee.

Then check campaign quality. High bounces usually mean a list problem. High complaints usually mean relevance, targeting, frequency or consent is wrong. Spam placement with low bounces can point to content, domain history or reputation.

Use this checklist before increasing volume.

If a domain is already damaged, volume cuts help more than extra warm-up. Pause risky mailboxes, remove bad lists and let the domain return to a low-noise pattern.

If only one mailbox is failing, isolate it. Pause that mailbox for a few days, keep others stable, and inspect its campaign history. Do not punish the whole domain unless domain-level signals are also poor.

If a dedicated SMTP IP is failing, check provider logs for throttling, blocks and bounces. Also confirm PTR/rDNS and sending domain alignment. For Postmark specifically, note that its terms require permission-based lists and prohibit purchased or rented lists, so it is not a cold-email route.

Should warm-up continue while sending?

Warm-up is not only a pre-launch task. It is a background signal that keeps the mailbox active between campaigns and helps reveal placement changes early.

Once campaigns start, reduce warm-up to a steady level. For most cold-email mailboxes, 10–15 warm-up emails per day is enough while sending. More is not automatically better.

Keep real outbound inside working hours. Spread messages. Avoid blasting a full daily quota in one block. If your provider or tool has stricter limits, follow the provider’s current limits.

Separate warm-up metrics from campaign metrics. Warm-up spam placement tells you how controlled office-style messages are handled. Campaign performance tells you how actual prospects react. You need both.

A mailbox can pass warm-up and still fail with bad copy. A campaign with misleading subjects, heavy links, poor targeting or no unsubscribe can create complaints quickly.

Use warm-up to answer one question: can this sender deliver normal mail at a controlled volume? Use campaign data to answer a different question: do these recipients want this message?

For sending practice after warm-up, read how many cold emails per day is safe and how to warm up while sending cold emails. If you manage many inboxes, the multiple mailbox warm-up guide explains why more mailboxes usually beat more volume.

Warm the domain by authenticating it and earning safe domain-level history. Warm the mailbox by creating normal, low-risk inbox activity. Warm the IP only when you control the sending IP. If you want the mailbox layer handled without a card or time limit, start with the free warm-up tool and keep the domain checks visible while you ramp.

Frequently asked questions