Domains/inboxes per volume, warmup timeline, and compliance
At roughly 30 sends per mailbox per day once fully warmed, and 3 mailboxes per domain: 100 emails/day needs about 4 mailboxes across 2 domains; 500/day needs about 17 mailboxes across 6 domains; 2,000/day needs about 67 mailboxes across 23 domains — use the calculator below for any other target. Warmup ramps over roughly 3-4 weeks, from a handful of emails per day in week one to 25-40/day by week four, but your first send happens on day one of that ramp, not after it finishes. CAN-SPAM compliance is enforced structurally: a physical postal address and verified sender identity injected into every footer, plus a suppression list and a List-Unsubscribe header honored on every applicable message, server-side (full RFC 8058 one-click ships with the hosted unsubscribe endpoint, on the roadmap). GDPR is not automated the same way — establishing a lawful basis to contact EU-based recipients remains your own responsibility, the same sender-of-record model used for CAN-SPAM.
How many domains and inboxes do you need per volume?
A target daily send volume translates into a mailbox count and a domain count using two planning assumptions, stated plainly rather than hidden in a formula: 30 sends per mailbox per day once fully warmed (a conservative figure within the 25-40/day range in the deliverability guide), and 3 mailboxes per domain (the top of the independently-reported "2-3 mailboxes per domain" figure found during research into how agents plan this).
Worked examples at that same 30/mailbox and 3/domain ratio:
| Target emails/day | Mailboxes needed | Domains needed |
|---|---|---|
| 100 | 4 | 2 |
| 500 | 17 | 6 |
| 2,000 | 67 | 23 |
With agent-cold-email, one setup_infrastructure call provisions the domain and mailbox counts you specify directly — see the setup guide.
What's the warmup timeline before your first send?
Your first send happens on day one of warmup, not after it finishes — warmup is a volume ramp, not a gate you wait behind. A new mailbox typically starts at a handful of messages per day in week one and reaches roughly 25-40/day by week four, over a full ramp of about 3-4 weeks, while a pool of other inboxes opens and replies to build genuine sending reputation. See the full mechanics, including what warmup can't do.
With agent-cold-email, setup_infrastructure starts this ramp automatically as part of provisioning, and infrastructure_status reports per-mailbox warmup progress on demand — no need to track which day of warmup each mailbox is on across sessions, which is exactly the state a self-assembled stack requires you to re-derive every time; see the DIY cost of holding that state yourself.
Is CAN-SPAM and GDPR compliance enforced automatically?
CAN-SPAM: yes, structurally. A required physical postal address and verified sender identity are injected into every message footer, a suppression list is enforced server-side, and a List-Unsubscribe header is honored on every applicable message — not something your agent has to remember to implement. Full RFC 8058 one-click unsubscribe ships with the hosted unsubscribe endpoint (on the roadmap). Full detail: the compliance FAQ and the Terms of Service.
GDPR: honestly, not the same way, today. agent-cold-email does not ship GDPR-specific automated tooling (lawful-basis verification, EU data-residency controls, data-subject-request automation). If you're contacting EU-based recipients, establishing a lawful basis to do so under GDPR and applicable ePrivacy rules remains your own responsibility — the same sender-of-record model already used for CAN-SPAM: you are the "sender" and "initiator" of the outreach; this platform provisions and operates the infrastructure on your instructions. We'd rather say this plainly than imply automated GDPR coverage that doesn't exist yet.