A naming pattern and a headcount are the entire input. Accounts, aliases, signatures and warmup enrollment come out the other side, ready to send the same day.
- 0
- Mailboxes provisionable in one job
- 0s
- Median time to create a 20-mailbox roster
- 0
- Naming pattern variants rotated automatically
The roster is the unit. Not the mailbox.
Names, aliases, signatures and warmup enrollment resolve together in a single job, whether the roster is twelve mailboxes or six hundred.
One pattern, the whole roster
Set a naming pattern and a headcount. Every account, alias and warmup enrollment is created in the same pass, with nothing left to finish by hand afterwards.
Addresses that do not look generated
Twelve pattern variants rotate across the roster automatically, so a hundred mailboxes on one domain never read as a single find-and-replace.
Signatures change fleet-wide in one edit
Photos, display names, reply-to addresses and signature blocks are set at creation, and a later change lands across every mailbox at once.
Mailboxes that behave like used mailboxes
Inbox, Sent, Drafts and Archive are provisioned over standard IMAP from minute one, so nothing about the account reads as freshly minted.
Two inputs in. A working roster out.
A naming pattern and a headcount become real accounts: usernames generated, aliases attached, signatures applied, and every mailbox enrolled in warmup before the job reports itself done.
Patterns rotate so the roster reads human
first.last, f.last, firstl and custom forms rotate across the roster instead of stamping one shape onto every address on the domain.
Aliases forward without a second account
Each mailbox carries secondary aliases that forward into the primary inbox: role addresses like sales@ or support@ without an unmonitored account sitting behind them.
Identity is set at creation, not after
Display name, title, phone and signature block apply the moment the account exists, and stay editable in bulk from that point on.
Nothing leaves the job cold
Every mailbox enrolls in warmup before the job reports complete, so no account can send at full volume on its first day.
What a single job can hold.
The real numbers a provisioning job runs against.
Mailboxes per job
- Value
- 600
- Notes
- Queue additional jobs for larger rosters
Naming pattern variants
- Value
- 12
- Notes
- Rotated automatically across the roster
Alias limit per mailbox
- Value
- 10
- Notes
- Forwards into the primary inbox
Signature block size
- Value
- 4 KB
- Notes
- Supports inline logo images
Storage per mailbox
- Value
- 50 GB
- Notes
- Standard IMAP access included
| Limit | Value | Notes |
|---|---|---|
| Mailboxes per job | 600 | Queue additional jobs for larger rosters |
| Naming pattern variants | 12 | Rotated automatically across the roster |
| Alias limit per mailbox | 10 | Forwards into the primary inbox |
| Signature block size | 4 KB | Supports inline logo images |
| Storage per mailbox | 50 GB | Standard IMAP access included |
A larger roster splits across back-to-back jobs and still shares one warmup schedule.
Pattern in, warming roster out.
Three stages between a naming pattern and mailboxes already climbing their ramp.
Step 1: Name the shape of the roster
Pick a naming pattern, a headcount, and the domain (or domains) the roster should sit on.
Step 2: The job cuts every account
Accounts, aliases and signatures are created in one pass; a 20-mailbox roster typically finishes inside two minutes.
Step 3: Warmup claims them immediately
Each mailbox enrolls the moment it exists, opening at a low daily volume rather than whatever your sequencer would have asked for.
What comes up before a first bulk run
Yes. Every batch carries its own pattern, even on a domain that already has mailboxes on it. Nothing is rewritten retroactively.
Yes. IMAP access stays live whether or not a forward is set, so a forwarded address is still a real, readable mailbox rather than a redirect.
Queue jobs back to back. Each still finishes in minutes, and every mailbox joins the same warmup schedule regardless of which job created it.
Yes. A change to a signature block or display name field applies across the whole fleet in one action, not mailbox by mailbox.
As aliases forwarding into a real mailbox, yes. We will not create them as standalone accounts, because a role address nobody reads is a deliverability liability rather than an asset.
Cut a hundred mailboxes before lunch.
Set a pattern, pick a count, and the roster builds itself, and warmup starts the minute each mailbox exists.