Inboxes for ManyReach

Past a few dozen mailboxes the hard part of cold email stops being any single mailbox and becomes the fleet: which ones are sending, which are resting, which are new and still earning trust, and how a problem on one stays on one. ManyReach is a tool people pick for that scale, and this page is about the infrastructure pattern that makes the scale survivable: rotation, matched platforms, and a cap that is the same on every mailbox.

We build the mailboxes, not the sequencer, and this is not a review of ManyReach. Every figure here is ours and checkable against the calculator, the recipes and the price list.

The pattern that keeps a large fleet alive for quarters rather than weeks has three states, and every mailbox is always in exactly one of them.

The rotation planner builds the two-batch schedule from a target volume, and the rotation article is the reasoning in full. In ManyReach the mechanism is whatever lets you pause a group of senders and activate another; the schedule is yours, and it is worth writing down.

Match the mix to the list before you buy: run it through the ESP segmenter, and build the fleet in the same proportion as the providers behind your prospects. The ESP calculator does that in one step from an uploaded list, and the infrastructure recipes are the costed plans for the common volumes above.

• Real mailboxes, your admin. Every inbox is an official Google Workspace, Microsoft 365 or Azure mailbox with you as admin, delivered with credentials in a form that shapes into a bulk import rather than two hundred manual additions.
• Authentication already published. SPF, DKIM, DMARC and forwarding are configured on every domain before handover; at fleet scale, check a sample with the authentication checker and the whole fleet’s MX with the bulk MX lookup.
• Two-factor decided. Disable 2FA on the receiving account before delivery day, or keep it on and grant restricted sub-account access to [email protected]. On a large order this is the single thing that most often adds days.
• Groups decided. Which mailboxes form the active batch, which the resting one, which campaign each group serves. Decide it before the import so the grouping happens once.

1. 1Bulk import by provider. Google mailboxes through the Google path, Microsoft 365 and Azure through the Microsoft path, OAuth where offered. Past a handful of mailboxes, adding them one at a time is an afternoon you will not get back.
2. 2If you use IMAP/SMTP on Microsoft, enable SMTP AUTH first. Off by default on recent Microsoft tenants, at the tenant and per mailbox, and it fails looking exactly like a wrong password, two hundred times.
3. 3Group the senders into the active and resting batches. During the import, so the rotation is a toggle rather than a project.
4. 4Set the cap, display name and signature across the fleet in one pass. The cap is the figure for the platform below, the same on every mailbox. A fleet where some mailboxes run 15 and some run 40 is a fleet with a burned half.
5. 5Tracking on your own domain, or off. One shared tracking domain under two hundred mailboxes joins their reputations into one. A custom domain per campaign group, or no open tracking; we turned ours off and published the result.

At fleet scale a slipping mailbox is routine, and the response is the same every time: pause it so the campaign reroutes across the batch, check its domain with the blacklist checker, read its bounces with the bounce analyzer to tell the list from the domain, and message us on WhatsApp at +1 904 736 2539. Replacement inboxes are part of the package when deliverability drops. The fleet monitoring article puts authentication, expiry and Postmaster data for a hundred domains on one screen, which is how a slipping mailbox becomes a Monday item rather than a surprise.

Prewarmed inboxes include a free prewarmed .COM or .CO domain and send from the day they land: $8.00 per inbox per month on Google and Microsoft, $7.00 on a two-month commit, $6.00 quarterly. Azure is billed per tenant, $69 monthly, $60 on two months, $50 quarterly, with up to 100 inboxes on one domain, which at capacity is $0.69, $0.60 and $0.50 per inbox. Fresh inboxes on your own branded domains, warmed for 14 to 21 days first, run $3.50 to $2.00 per inbox per month on Google by order size and cycle, $3.00 to $2.00 on Microsoft 365, and $50 flat for an Azure tenant. Big fleets are usually a prewarmed layer to launch and a fresh layer to scale; the calculator prices any volume, and every price is at /price.md.

How many mailboxes does 1,000 cold emails a day need in ManyReach?

At 15 a day per Google Workspace mailbox, about 67 active. With rotation, which is the point of running many, about 134: half sending while half rests and warms, swapped on a schedule. On Microsoft 365 at 8 a day it is 125 active, and on full Azure tenants at 2 per inbox it is 500 inboxes across five tenants, which is why high-volume fleets mix platforms.

Do you load the inboxes into ManyReach for me?

ManyReach is not one of the sequencers our portal exports into directly (those are Instantly, Smartlead, PlusVibe and EmailBison). You get full admin on every mailbox and the credentials in a form that shapes into a bulk import, and if you would rather we did the import by hand, ask on WhatsApp.

What daily limit should each mailbox have?

Fifteen a day on Google Workspace, eight on Microsoft 365, two on a full Azure tenant of 100, four at 50 per tenant, six at 25. A big fleet makes it tempting to run a bit over because the total is already large; the fleets that last are the ones where the cap is the same on the first mailbox and the two-hundredth.

Should resting mailboxes keep warming?

Yes, and ours do without you doing anything: our warmup runs at 30 emails per inbox per day underneath your campaigns for as long as you hold the inboxes, resting or active. ManyReach’s own warmup on top is more mail from the same mailbox; leave it off, or count it inside the cap.

Can I mix Google, Microsoft and Azure in one ManyReach fleet?

Yes, and at volume you should: match the fleet to the share of your list behind each provider (the ESP segmenter tells you), so Gmail-hosted prospects get Google senders and Outlook-hosted ones get Microsoft. Our placement research is the reason: the matching route reaches the primary tab more consistently in our own sending.

How fast do two hundred mailboxes arrive?

Every order is delivered within 48 to 72 hours of payment, prewarmed and fresh alike, with SPF, DKIM, DMARC and forwarding configured first. Large orders are built in the same window; what slows one down is an account with 2FA still on, which is why that is decided before delivery day.