A cold email warm-up schedule helps a new domain build a sending history before you expand email outreach. Use the four weeks below as review stages. Choose a target for your setup, increase gradually and let delivery results decide when to move on. Mailbox capacity depends on your setup and delivery results.

Before you start, make sure authentication is right with the free Rhycon email deliverability checker. No amount of warm-up fixes broken SPF, DKIM or DMARC.

What warm-up is

Email warm-up means gradually increasing how much mail a new setup sends. Use genuine conversations to build a sending history before you start sending outreach campaigns.

Domain and IP reputation are related but different. A new mailbox can use a provider’s established shared IP while its domain has little history. Authentication proves who sent a message; sender reputation also depends on recipient feedback and sending behaviour.

Before you warm up anything

  1. Choose your sending domain deliberately. A separate, clearly branded outreach domain can help separate operations. It does not guarantee protection for your main domain. Avoid names or identities that mislead recipients.

  2. Set up authentication. SPF, DKIM and DMARC, plus a working MX record. See our guides to SPF, DKIM and DMARC.

  3. Check readiness before day one. Confirm that DNS records resolve, messages pass authentication and replies reach your inbox. Waiting a fixed number of days alone does not establish a sending reputation.

  4. Plan mailbox and domain volume together. Count every sender on the domain. Choose the number of mailboxes your team can manage. Adding accounts does not remove provider restrictions or reputation problems.

A four-week cold email warm-up schedule

This example works toward a planning target of 100 outreach emails per mailbox per sending day. The target is illustrative, not a guaranteed safe volume or a maximum. Repeat any stage if delivery is not stable.

Use five sending days each week, spread messages through your working hours and avoid a catch-up burst after a break. Count first emails and follow-ups in the outreach totals. Allow room for normal replies and warm-up traffic within your provider’s total allowance.

  • Week 1: Establish the setup. Send 5 to 10 genuine, expected emails per day to contacts who know you. Check replies and message headers. Leave new cold outreach off while you confirm that the setup works.

  • Week 2: Introduce outreach to a small, relevant audience. Example daily counts: 10, 15, 20, 25 and 30. Verify addresses before sending, include an easy opt-out and remove bounced or unsubscribed contacts from later steps.

  • Week 3: Expand only after reviewing delivery. Example daily counts: 35, 40, 45, 50 and 55. Inspect bounces, deferrals, complaints and human replies. Keep follow-ups inside each day’s outreach budget rather than adding them on top.

  • Week 4: Work toward your chosen target. Example daily counts: 60, 70, 80, 90 and 100. Each increase depends on stable delivery and your provider’s rules. Hold or step back when problems appear; reaching day 28 does not automatically make a domain ready.

  • After that: Review the volume your setup can support. Rhycon often sends up to 100 emails per day from fully warmed-up mailboxes with high warm-up scores. Use that as an example from our operations, rather than a fixed ceiling. Before increasing further, review account quotas, provider policy, domain-wide volume, recipient feedback and reply capacity. Confirm real campaign delivery alongside any warm-up score.

What to do in each week

Week 1: prove that the setup works

Use the first five sending days to check the complete route: outgoing mail, delivery, incoming replies and account access. Ask existing contacts for a real conversation about a current topic. Do not send empty messages or ask people to perform fake engagement simply to raise a score. Keep the subject and sender name clear.

Save a received message with its authentication results. Then reply to that message and confirm the response reaches the correct mailbox.

If a reply goes to the wrong account, fix routing before you launch a campaign. Add a short note to your log about the provider, domain, mailbox and test result. This creates a useful baseline for later comparison.

At the end of the week, the decision is straightforward: either the setup works and you can try the next stage, or a specific issue still needs attention. A DNS problem does not disappear because you have waited seven days. Keep the volume steady while you resolve it.

Week 2: test one small audience

Choose a small group that fits one clear reason for contact. Start with a single offer and a short email that explains why it is relevant to that person. Keep the audience source and campaign version in your log. This helps you distinguish a list problem from a problem affecting the entire sending domain.

The example daily counts are 10, 15, 20, 25 and 30. A follow-up uses one place in that daily total. If yesterday’s contacts are due a follow-up, reduce today’s new introductions accordingly. Review responses before scheduling the next day. Remove people who opt out and suppress invalid addresses across the relevant campaign steps.

Use this stage to learn whether your workflow can handle real replies. A mailbox can deliver an email correctly while your team misses the response. Assign an owner for replies and check that conversations appear where the team expects to work. Sending more mail will not fix a broken handoff.

Week 3: expand with a consistent setup

Keep the sending identity, working hours and campaign purpose consistent while you test 35, 40, 45, 50 and 55 daily messages. You can repeat a daily count for several days when the evidence is unclear. These numbers are an example sequence, not a requirement to increase every morning.

Compare this week with the first outreach week. Look for changes by recipient provider and audience segment, rather than relying on one combined average.

For example, if delivery to one provider starts deferring while other providers remain stable, record the affected responses and investigate that route. Avoid making a domain-wide increase while you are still diagnosing the pattern.

Make one meaningful change at a time. If you replace the list, rewrite the email and double the volume on the same day, you lose a useful comparison.

Keep a copy of the previous campaign and record the date of each change. That makes it easier to connect a result with the decision that preceded it.

Week 4: review readiness for your target

The final example sequence is 60, 70, 80, 90 and 100. Before each increase, review actual campaign delivery and the work waiting in the inbox. A high warm-up score is one signal from that service. It does not replace the results from the real recipients you are contacting.

By this stage, your log should show what the mailbox sent, how delivery behaved and what the team did with replies. Use that record to choose the next operating volume.

Rhycon often sends up to 100 emails with fully warmed-up, high-scoring mailboxes. Some teams may choose a different target, or stay at a lower volume while they investigate a problem.

A new domain may need more than four weeks. If week 3 did not produce stable results, repeat the review stage instead of treating week 4 as permission to send 100. The useful outcome is a setup you understand and can operate consistently. The calendar is a planning aid, not proof of reputation.

A worked example: planning a 100-email outreach day

Suppose you have chosen 100 campaign emails for an established mailbox. You have 35 follow-ups due today. That leaves 65 places for new introductions: 35 follow-ups plus 65 first emails equals 100 campaign messages. Do not schedule 100 new emails and add the 35 follow-ups afterwards.

Now account for the activity outside the campaign. If you expect 15 manual replies and 10 warm-up messages, the example total becomes 125 outgoing messages.

Check that the account’s actual allowance and your operating plan accommodate the total. These example figures explain the arithmetic; they do not set a sending limit or promise a particular delivery result.

Review the domain total as well. Three mailboxes running the same example produce 300 campaign messages and 375 outgoing messages across the domain. Keep both views visible: a mailbox budget helps scheduling, while the domain view reveals the combined activity. Assign someone to review the aggregate before adding more accounts.

What to do after a break or a delivery problem

After a weekend or planned pause, resume without a catch-up burst. If the setup stayed stable, review the last completed stage and choose a measured restart. After a long pause, a provider change or an account incident, check routing and authentication again before increasing outreach.

When a delivery problem appears, note the last stable volume and the first affected campaign. Keep the relevant message headers and error responses.

Resolve the cause, then use a small controlled send to check the result. If that evidence is still unclear, hold the increase. A missed daily target does not create a debt you need to repay tomorrow.

Rules that matter more than the schedule

  • Watch delivery errors. Track hard bounces and temporary deferrals separately. Suppress invalid addresses immediately. A low average bounce rate can hide a poor list segment, so inspect the affected recipients and SMTP responses.

  • Keep spam complaints well under 0.1 percent. Google recommends keeping the spam rate reported in Postmaster Tools below 0.1 percent and avoiding 0.3 percent or higher. Low-volume data can be incomplete; no reported complaints is not proof that every message reached the inbox.

  • Send to people who might actually care. Check recipient expectations and the sending provider’s policy before outreach. Relevant copy and a verified address do not by themselves mean that a person has agreed to receive email. Honour opt-outs promptly.

  • Count all outgoing activity. Campaigns, follow-ups, replies and automated warm-up all contribute to sending volume. Keep their counts visible so the total does not exceed the account’s actual allowance.

  • Raise volume slowly. Avoid abrupt spikes and send at a consistent pace. A fixed weekly percentage cannot establish that an increase is safe. Use delivery evidence to decide how long to stay at each stage.

  • Pause if things go wrong. Hold increases or reduce sending when red flags appear: rising deferrals, blocks or complaints. Diagnose authentication, list quality, content and the sending path. Resume gradually once you understand and resolve the cause.

Keep a daily warm-up log

Record messages attempted, accepted, deferred and bounced for each of your email accounts. Log first emails, follow-ups, warm-up activity and replies separately. Compare daily totals with your planned email sends before adding the next step.

Check where messages arrive. With permission from a few genuine contacts, ask whether a message appeared in the inbox or spam folder. Check Gmail, Outlook and the other services your audience uses. One test does not represent every recipient, but repeated messages landing in spam call for a closer review.

Investigate patterns rather than assuming volume is the cause. Note whether deliverability issues cluster by recipient provider, address source or campaign. Review the affected message headers and delivery responses. Spam filtering differs across services. A successful test at one provider does not settle the question for another.

Keep a record of what changed. If you suspect a change is triggering spam filters, compare delivery before and after it. Avoid changing the sending volume, list and content at the same time. That makes the cause harder to identify. Do not keep sending emails at a higher volume while the problem remains unresolved.

Does automated warm-up work?

A warmup tool exchanges messages between connected mailboxes. Its score describes activity inside that service; it does not prove that your campaign reaches real recipients.

Check whether your provider permits the tool and how it uses account access. Genuine conversations and delivery monitoring remain useful throughout the plan. Review whether automated warm-up is still useful as normal sending grows.

See how Rhycon fits your outreach

Managing several sending domains takes time. Rhycon’s managed infrastructure uses Rhycon-owned domains and mailboxes for your outreach, so you do not have to buy and set up your own. You can also verify any setup at any time with the checker.

Cold email warm-up FAQs

How long should I warm up a new email domain?

Four weeks is a useful planning window for this example. Some setups need longer. Advance when authentication, delivery and recipient feedback support the next step, rather than treating time alone as proof of readiness.

Can a mailbox send 100 emails per day?

Rhycon often sends up to 100 emails per day from fully warmed-up mailboxes with high warm-up scores. A new mailbox should build toward its agreed target gradually.

This article does not impose a fixed daily ceiling. Check real campaign delivery as well as the score, and count follow-ups and other outgoing mail when planning the total.

Can I warm up my main domain?

You can establish genuine sending activity on your main domain. For outreach, assess the effect on important business mail and whether a separate, clearly branded domain fits your operations. Separate domains do not guarantee that reputational effects stay contained.

Do I need to keep warm-up on forever?

No. Review the tool’s purpose, provider policy and real delivery evidence. Keep useful monitoring and genuine correspondence in place; do not rely on a warm-up score as a permanent requirement.

For provider requirements and gradual sending guidance, read Google’s email sender guidelines. This schedule is an illustrative operating plan, not a provider-approved benchmark.

See how Rhycon works and complete the homepage onboarding to explore how research, outreach and replies fit your workflow.