What a mailbox calculator is, and how to size your sending infrastructure

A mailbox calculator (sometimes called a sending-capacity calculator) answers a specific planning question: given a target daily or monthly email volume, how many sending mailboxes do you actually need, accounting for the fact that each one has a safe per-day cap that depends on its warm-up stage.

The core formula

Required mailboxes = Target daily volume / Safe per-mailbox daily cap

The complication is that "safe per-mailbox daily cap" isn't a fixed number - it depends on how long a mailbox has been warming up, which provider it's on, and the domain's overall reputation.

Typical safe caps by warm-up stage (illustrative, not a hard rule)

These ranges vary meaningfully by provider (Gmail and Outlook both apply their own limits independent of your warm-up schedule) and by use case (cold outreach caps are generally lower than caps for mail to an engaged, opted-in list).

A worked example

A team wants to send 2,000 cold outreach emails/day and is starting from zero warmed mailboxes.

• At a week-4-6 safe cap of ~120/mailbox/day, that's roughly 17 mailboxes needed at full target volume.
• But none of those mailboxes can start at 120/day - each needs its own 4-6 week ramp, so the *effective* available volume during the ramp period is much lower than 2,000/day.
• A realistic plan: stand up mailboxes in batches (say, 4-5 at a time, staggered a week apart) rather than all 17 at once, so the team isn't waiting 6 weeks with zero sending capacity before the first batch is productive.

Why this matters beyond simple arithmetic

Treating "mailboxes needed" as a single division problem undercounts the real requirement, because it ignores that newly added mailboxes contribute far less than their eventual full capacity during the weeks they're still warming. A calculator that only divides target volume by the *final* safe cap will understaff the sending infrastructure for the first month or two, which either means missing volume targets or - worse - pushing new mailboxes past their safe cap to compensate, risking the exact reputation damage the warm-up period exists to prevent.

A more realistic planning approach

1. Calculate the final steady-state mailbox count using the fully-warmed cap.
2. Add a buffer (commonly 15-25%) for mailboxes that underperform, get flagged, or need to be rotated out.
3. Stagger onboarding so mailboxes reach full capacity in waves rather than all finishing warm-up simultaneously - this also means a reputation problem on one wave doesn't stall your entire sending capacity at once.

What not to do

• Don't divide target volume by a single "safe daily cap" number without accounting for warm-up stage - this consistently understates how many mailboxes and how much lead time you actually need.
• Don't stand up all required mailboxes simultaneously and start warming them on the same schedule - staggering reduces the blast radius if one batch runs into a problem.
• Don't push a mailbox past its current-stage cap to hit a volume target early - the short-term gain is reliably outweighed by the reputation cost if it trips a rate limit or spam flag.
• Don't forget provider-specific limits (Gmail and Outlook both apply their own daily sending caps independent of your own warm-up math) - the calculator's output is a planning estimate, not a guarantee against provider-side limits.

Extending the calculator: a staggered-wave plan in full

Continuing the 2,000/day cold-outreach example above, here's what the full staggered rollout actually looks like week by week, rather than just the end-state mailbox count:

The practical takeaway from laying it out this way: a team that needs 2,000/day in week 1 and only plans for 17 mailboxes at their *final* cap will spend the first six to seven weeks well short of target no matter what they do - the only way to close that gap faster is starting the mailbox rollout earlier, not warming any individual mailbox faster, since pushing warm-up speed is exactly the shortcut that risks the reputation damage the calculator is designed to help you avoid.

Sizing for list-based sending versus cold outreach

The calculator's logic changes slightly depending on what's being sent. Cold outreach to unfamiliar recipients needs the conservative caps in the table above throughout, since there's no engagement history to offset the risk. Sending to an engaged, opted-in list can run meaningfully higher once a mailbox is fully warmed, because positive engagement (opens, clicks, replies) signals legitimacy back to the receiving provider in a way cold outreach never does - which is why the same "fully warmed" mailbox might safely carry 500+/day to an engaged list but should still stay closer to 150-250/day if a meaningful share of its volume is cold.

MailPilot manages the warm-up curve this calculator is built around directly - ramping each mailbox's volume automatically based on its actual stage and reputation, across OAuth and SMTP/IMAP connections, so the capacity-planning math above is backed by a real, managed ramp rather than a manual spreadsheet.