TL;DR
- At fifty or more mailboxes, choose infrastructure by ownership, client isolation, DNS visibility, provider diversity, replacement workflow and exportability before unit price.
- Mailforge and Infraforge are specialised infrastructure candidates; Maildoso and InboxKit deserve evaluation for packaged mailbox operations. Google Workspace and Microsoft 365 offer direct tenant ownership but require more administration.
- No infrastructure vendor guarantees inbox placement. Authentication, targeting, copy, complaint control and sending behaviour remain part of the system.
- Use client-owned domains where practical, keep a mailbox registry and prove offboarding before scaling.
Contents
- Quick comparison
- What changes after fifty mailboxes
- Specialised infrastructure vendors
- Direct Google Workspace or Microsoft 365
- DNS, authentication and monitoring
- Replacement and incident workflow
- Procurement checklist
- FAQ
Quick comparison
| Option | Strong operating fit | Verify before purchase |
|---|---|---|
| Mailforge | Packaged cold-email domain and mailbox infrastructure | Domain ownership, DNS access, provider mix, replacement and export |
| Infraforge | Private infrastructure and mailbox management for teams seeking more control | Tenant isolation, setup responsibility, monitoring and recovery |
| Maildoso | Bulk domain and mailbox provisioning for outbound operations | Account ownership, provider allocation, replacements and support |
| InboxKit | Managed email infrastructure tied to outbound workflows | Provisioning model, controls, handoff and current plan limits |
| Direct Google or Microsoft tenants | Client ownership and familiar administration | Admin effort, licensing, acceptable-use rules and tenant health |
Do not assume mailboxes from different storefronts are operationally diverse. Ask which underlying providers and tenants carry the accounts.
What changes after fifty mailboxes
A spreadsheet with address, password and campaign name stops being sufficient. The agency needs an inventory of client, domain, mailbox, provider, tenant, DNS state, authentication, owner, campaign assignment and health state.
One change can affect many senders. A DNS mistake, tenant restriction or shared-provider incident can pause a client’s whole programme. Design blast-radius boundaries before choosing a vendor.
Assign every mailbox to one client and purpose. Avoid moving identities casually between unrelated campaigns because reply history, reputation and ownership become hard to explain.
Specialised infrastructure vendors
Mailforge and Maildoso market domain and mailbox infrastructure for cold-email operations. They can reduce provisioning work for agencies that would otherwise create and configure many accounts individually.
Infraforge emphasises private infrastructure and operational control. It can be relevant when the buyer wants stronger isolation or a clearer dedicated environment rather than pooled convenience.
InboxKit is another managed-infrastructure candidate to inspect alongside the sending workflow. For every provider, ask who owns domains and tenants, which DNS records remain accessible, how credentials are transferred and what happens when the contract ends.
Direct Google Workspace or Microsoft 365
Buying standard business mailboxes directly can give the client clear tenant and domain ownership, established administration and familiar security controls. It may suit a smaller number of valuable sender identities where continuity matters more than rapid provisioning.
It also shifts setup, licensing, policy compliance, user administration and incident response to the operator. Review each provider’s current acceptable-use rules and do not treat an ordinary workplace mailbox as unlimited campaign infrastructure.
Keep outbound domains separate from the primary corporate domain while preserving transparent ownership and brand controls.
DNS, authentication and monitoring
Track SPF, DKIM and DMARC state for every sending domain. Confirm that the selected provider gives the access or support needed to configure them correctly. Avoid creating an SPF record with too many indirect lookups through careless vendor additions.
Monitor bounces, complaints, blocks and unusual login or authentication failures. Provider dashboards and Google Postmaster Tools or Microsoft reporting can offer useful evidence where applicable, but coverage varies.
A seed placement test is diagnostic, not a promise of production inboxing. Real results depend on recipient, content, engagement and sender history.
Replacement and incident workflow
Define thresholds for pausing a mailbox and investigate before replacing it. Rapid replacement can hide bad targeting or messaging and spread the same problem to new assets.
When a mailbox fails, preserve replies and suppression state, disable new sends, record the provider reason and decide whether recovery is possible. Do not automatically move active prospects to a new sender without checking sequence state.
Test credential rotation, a disabled mailbox and a provider outage during the pilot. The operating team should know how to stop all campaigns that use the affected asset.
Procurement checklist
Price the full configuration: domains, mailboxes, setup, renewals, monitoring, replacements, support, minimum term and any sending product. Ask whether quoted capacity is a technical maximum or a recommended operating level.
Review ownership, data location, subprocessors, security, acceptable use, export and termination. Keep the signed client-authorisation and offboarding process beside the infrastructure record.
Start with a small group across the planned providers. Scale only after DNS, reply routing, campaign stops and inventory reconciliation work reliably.
FAQ
How many domains are needed for fifty mailboxes?
There is no universal ratio. It depends on provider rules, mailbox design and the team’s conservative operating policy.
Does managed infrastructure guarantee deliverability?
No. It simplifies parts of provisioning; inbox placement still depends on the wider programme.
Should the agency own client domains?
Client ownership is usually clearer for continuity. Document access and transfer whichever model is used.
Is provider diversity always better?
It can reduce one failure domain, but it also adds administration. Verify actual underlying diversity.
What must be tested before scaling?
DNS, authentication, reply routing, suppression, pausing, credential recovery and full offboarding.
Sending software is one part of the operating setup. Our guide to cold email deliverability tools covers the adjacent options.
Sources and comparison method
The recommendations are editorial assessments of workflow fit, not results from a comparative product test. Supporting product references are linked below; prices and plan entitlements should be confirmed for the configuration being purchased.
- Mailforge official site
- Infraforge official site
- Maildoso official site
- InboxKit official site
- Google email sender guidelines
- Microsoft email authentication guidance
Work with Forma Nôrden
Forma Nôrden designs agency email infrastructure around client ownership, inventory, failure boundaries and clean handoff. We help teams turn mailbox capacity into an operation they can govern. Explore how we work.
For enquiries about this article: partnerships@formanorden.com
