Sending limits

Email sending limits are not your daily target

Email sending limits are hard ceilings, not quotas. A mailbox should send well below the published limit until it has built a stable history and shown that recipients respond without a spike in complaints or delivery failures.

The mistake I see most often is simple: a team finds the provider's daily allowance, multiplies it by the number of mailboxes, and calls that outbound capacity.

It isn't.

Say a 12-person software company adds six new mailboxes for a launch aimed at operations leaders. The provider says each account can send 100 messages a day. The team schedules 600 messages on Monday, adds follow-ups on Tuesday, and assumes the system will spread everything out safely.

Then the replies start. A few people ask to be removed. Several addresses bounce. The new mailboxes have no useful history, and the follow-ups stack behind the next batch of first-touch messages. The team technically stayed inside the provider limit. The domain still took the hit.

A provider limit answers a narrow technical question: how much mail the service may accept under its policies. It doesn't tell you how much a particular mailbox can send without changing its reputation.

That number depends on the mailbox, its history, the audience, and what recipients do with the messages.

The mailbox earns its volume

Ramp is per mailbox. It isn't a campaign-level setting, and adding more senders doesn't make a new sender trustworthy.

Each mailbox builds a separate record through its sending behavior. The provider can see volume, timing, delivery failures, complaints, replies, and other signals tied to that sender. Two mailboxes on the same domain can have different safe operating ranges because one has been sending normally for nine months while the other was created last week.

This is where mailbox rotation gets misunderstood. Rotation distributes load. It doesn't transfer reputation. If a team creates ten fresh mailboxes and pushes each one toward the published ceiling, it hasn't solved the ramp problem. It has created ten versions of the same problem.

A better question is: what can this mailbox sustain without causing a meaningful change in recipient behavior or delivery?

That answer can move up over time, but only when the evidence supports it. A mailbox that has been sending steadily, getting real replies, and producing few bounces may be ready for more activity. A mailbox with rising complaints or poor delivery isn't. Don't increase its volume because the campaign has more prospects waiting.

The provider's limit is a boundary. The mailbox's history is the operating constraint.

Volume only makes sense in context

Raw send count doesn't tell you much by itself.

A sequence sending 30 new messages and 30 follow-ups behaves differently from one sending 60 new messages. A follow-up that stays in the original thread is at least a coherent continuation of a conversation. Five separate messages to the same person look careless, even if the total count is identical.

That doesn't make threaded follow-ups automatically safe. If the first message is poorly targeted, the follow-ups just extend the problem. Personalization won't rescue a message sent to the wrong person either. A detailed opener aimed at someone who doesn't own the problem can still produce a complaint or an unsubscribe.

Message composition matters, but teams tend to overestimate it. A templated message with a relevant written opener can work better than a supposedly custom email assembled from weak data. What matters is whether the audience is a fit and whether the sending pattern makes sense.

Testing has the same limitation. An A/B test can show that one version gets better replies than another. It cannot give a mailbox permission to send twice as much. A winning subject line doesn't erase a new mailbox's lack of history, and a high reply rate doesn't excuse sending to a bad list.

The useful signals are the combined pattern: steady volume, appropriate recipients, real replies, low failure rates, sensible follow-ups, and prompt suppression when someone replies or opts out. No single metric gets to decide this on its own.

Put the controls in before launch

The safest time to control volume is before the first message goes out.

Start with suppression. Previously contacted prospects, excluded accounts, opt-outs, and people already in an active conversation should stay out of the send path. Duplicate contact isn't just annoying. It creates avoidable complaints and makes the campaign look disconnected from what the recipient already told you.

A 30-day send projection is useful because the first day hides the real load. Imagine a campaign that adds 25 new prospects per mailbox each weekday and sends three follow-ups. By the third week, those follow-ups are arriving alongside new messages. The mailbox may look quiet on day one and overloaded by day 18. Project the whole sequence, not just the initial send.

The eight-category pre-flight should be a launch gate, not a box-ticking exercise. Check the audience, sequence logic, sending plan, channels, suppression, reply handling, and anything else that can cause a prospect to receive the wrong next step. If the setup is wrong, pause and fix it. Raising the sending limit only makes the bad setup run faster.

Tiered campaigns can help when different audiences need different sequences. A small agency selling payroll software might separate 50-person companies from 500-person companies because the trigger, buyer, and follow-up timing aren't the same. Keeping those groups in separate tiers makes uneven volume easier to spot. A single flat sequence is simpler, but it can hide the fact that one audience is producing most of the follow-ups and complaints.

Reply handling is another basic control that gets skipped. Each prospect should have a clear position in the pipeline, and a reply should stop further automated messages unless there is a deliberate reason not to. Continuing to send after someone has answered is bad outreach. It's also an unnecessary reputation signal.

What to use as the operating rule

Set the provider's published limit as a ceiling you don't plan to touch. Set the actual mailbox volume below it based on ramp, history, recipient fit, and observed response. Review that decision when the campaign changes, not only when delivery has already deteriorated.

If a 20-person SaaS company gets a sudden spike in bounces after importing a new list, the answer isn't to spread the list across more mailboxes. Stop the campaign, inspect the data, and let the affected senders stabilize. More accounts won't fix bad targeting or weak suppression.

Ask whether the mailbox has earned more volume, and whether the campaign can stop the wrong prospect from receiving the next message. Those two answers matter more than the number printed in the provider settings.