A mailbox is the actual email account that sends and receives messages.
If a domain is the street address, the mailbox is the person living there.
Example
Domain: brand.com
Mailbox: john@brand.com
In cold email, you do not rely on one mailbox. You use multiple mailboxes across multiple domains to spread volume and protect reputation. If one mailbox has an issue, the campaign can keep running.
Mailbox vs Domain (Infrastructure Hierarchy)
Understanding the structure makes everything else easier.
Domain
The foundation
Example: trybrand.com
Mailbox
The individual sender inside the domain
Example: sales@trybrand.com
ESP (Email Service Provider)
The system hosting the mailbox
Examples: Google Workspace, Microsoft 365, Azure
Simple rule
Domains own reputation
Mailboxes do the sending
The Traditional Cold Email Setup (Old Model)
For years, the usual approach was:
Buy 100 or more domains
Create 1 to 2 mailboxes per domain
Send small volumes from each mailbox
Why it worked
Google and Outlook were more likely to flag domains that had too many cold sending mailboxes, so teams spread risk by using lots of domains.
The problems with the old model
Expensive
Domains plus mailboxes add up fast
High maintenance
Lots of DNS records
Lots of inbox logins
Lots of credentials to manage
Fragile
A small number of complaints can damage a domain and take multiple mailboxes down with it
The New Model: Azure Based Infrastructure
Modern setups are moving away from only using traditional Google and Outlook inboxes and toward infrastructure built on Azure.
Platforms like sending.ac can support:
Dozens to hundreds of mailboxes per domain
Without automatically destroying deliverability
This works because the setup is designed for better isolation at the infrastructure level.
You no longer need 100 domains to send 5,000 emails. You need mailboxes that are properly isolated and managed.
Why Isolation and Tenants Matter
This is the most important concept in modern deliverability.
What is a tenant
A tenant is a private container that holds your email setup.
Standard providers (Google and Outlook)
Many users share the same environment
Risk is shared
One bad sender can affect others
Isolated infrastructure (sending.ac style)
One domain can be placed in its own private tenant
No noisy neighbors
Reputation is more controllable
What isolation gives you
Tenant specific DKIM
Unique sending infrastructure signals
Separate mailbox connections for replies and access
The practical result
Your performance depends more on your own behavior, not other senders around you.
Sending Limits and Mailbox Hygiene
Isolation does not mean unlimited sending. Cold email still needs to look human.
Best practices
Daily sending limit
30 to 50 emails per mailbox
Warm up
Increase volume gradually over about 14 days
Rotation
Use a sequencer like Smartlead or Instantly to spread sends evenly across mailboxes
If one mailbox works too hard, inbox providers notice.
Cost Comparison: Old vs New
Traditional setup
100 domains
Dozens of inboxes
Often $1,500 or more per month
High maintenance
Azure based infrastructure
Fewer domains
More mailboxes per domain
Often much lower cost per mailbox
Less overhead
In Summary
Mailboxes are the engines of your cold email system.
Old systems scaled by adding more domains. Modern systems scale by isolating reputation properly and managing mailboxes well.
When mailboxes are isolated, warmed up, and rotated correctly:
You can send more
You land in inboxes more often
You control risk better
Powered by