Mailbox Rotation for Cold Email Infrastructure

Is: A send policy that assigns outbound messages across a pool of mailboxes so daily load per seat stays inside a human looking range.

Is not: A way to hide a bad list. Is not: A reason to ignore authentication. Is not: A substitute for domain isolation from your primary brand domain.

If ten mailboxes all sit on one overloaded domain with failing DMARC, rotation only helps you fail more evenly.

Two layers matter:

1. Mailbox layer. Cap each seat (common practice: roughly 20 to 40 cold sends per day once warmed, including follow ups; lower while new).
2. Domain layer. Prefer two or three mailboxes per domain, and spread campaign volume across several domains so one domain's reputation event does not halt the whole day.

A pool of twelve mailboxes on four domains is healthier than twelve mailboxes on one domain with the same total volume. See How Many Mailboxes Per Domain for Cold Email.

Instantly, Smartlead, and similar tools let you connect many Google accounts and set per mailbox daily limits. Campaigns then draw from the pool. Instantly and Smartlead both document automatic rotation across the accounts assigned to a campaign, and both treat a mailbox's daily limit as shared across every campaign that uses it. Check each tool's help center for current settings. Exact UI labels differ; the ideas that matter are:

Per mailbox daily send limits you control. The ability to pull one account out of a campaign without stopping it. In Instantly, for example, removing an account from the campaign lets the other assigned accounts take over, while an account that is only disconnected can leave the campaign waiting for it. Consistent naming so you can see which domain a seat belongs to. Connect methods those tools document: signing in with Google (OAuth) or IMAP and SMTP with app passwords.

Mailboxes should arrive ready to connect using those methods. If a provider mentions a direct integration, ask how it works and check the sequencer's own docs.

1. Size the pool from the daily target: Daily cold sends divided by your per mailbox cap equals mailbox count. Mailbox count divided by two or three equals domain count. Add headroom for seats still in warmup. Google's published per user ceiling stays out of this math except as a remote maximum you never plan to touch. See Google Workspace Sending Limits for Cold Email.

2. Name for humans and for ops: Use a pattern that encodes domain and seat, so a health alert maps to a DNS zone and an Admin console in seconds.

3. Equal caps first, then bias: Start with equal daily caps across warmed seats. If one mailbox shows rising bounces or falling replies, lower its cap or pause it; shift load to healthy peers instead of raising everyone else to compensate in one jump.

4. Keep follow ups in the same identity when you can: When a prospect already received mail from alex at domainA, follow ups from that same address usually read more naturally than a random jump to another brand domain mid thread. Let the sequencer's threading rules do that work; use pool rotation mainly for new conversations and for balancing first touches.

5. Warm new seats before they join full rotation: New mailboxes should finish an initial warmup period before they take a full share of campaign volume. Dropping cold seats straight into equal rotation is how you burn the new ones first. See Warmup Myths That Waste Cold Email Teams.

6. Watch the right signals: Per mailbox and per domain: human replies, bounce rate, spam complaints, provider health, and (if configured) Postmaster views. Open rate is a weak steering signal. See Tracking Pixels and Cold Email Placement Tradeoffs.

If you run outbound for several clients, each client needs a separated pool. Rotating one client's prospects across another client's domains creates brand and compliance messes, and it couples reputation. Prefer separate organizations or clearly separated pools on plans that include them. Pause and rotation stay inside one client's infrastructure.

One domain, many seats, high total volume. You rotated mailboxes and still hammered one domain reputation.

Caps set near Google's 2,000 limit. The account may send; Gmail placement will not thank you.

Ignoring a weak seat. Leaving a burned inbox in the pool lets it keep training filters while healthier seats try to recover the campaign. See Why Cold Email Inboxes Get Burned.

Shared SMTP pool sold as rotation ready. You may be rotating across seats that still share sending infrastructure with strangers. Know the platform. See Dedicated Google Workspace vs Shared Cold Email Infra.

Primary domain in the pool. A rotation win is worthless if the brand domain is in the blast radius. See Primary Domain Isolation for Cold Email.

Copy paste lists into every seat without verification. Rotation spreads a bad list faster.

1. Sort mailboxes by reply rate and bounce rate.
2. Pause or cut caps on the bottom tier.
3. Confirm auth still passes on every active domain.
4. Add warmed capacity only if the healthy pool is truly at its caps.
5. Record what changed so the next burn is easier to diagnose.

ColdMail provides the mailbox layer rotation needs: official Google Workspace on dedicated domains, automated SPF, DKIM, DMARC, and MX, admin panels with 2FA, and provider health indicators so you can see which domain or inbox to pull from the pool. AI warmup is available as an optional add on; see coldmail.app for current add on pricing. Multiple organizations are available on supporting plans for agencies that must keep client pools apart.

ColdMail is not a sequencer. Mailboxes are ready to connect in Instantly and Smartlead using the methods those tools support, and they work with n8n and other tools. You set rotation and daily limits in the tool that sends.

Get Started with a pool sized for your daily target at coldmail.app, or Book a Strategy Call to map domains, seats, and caps.