How to create unlimited inboxes with Inframail: the domain math for scaling to 1,000+ sends per day, bulk provisioning workflow, SMTP export, and inbox portfolio management.
Sarah Okonkwo
Cold email strategist, 300+ domain setups · Updated June 24, 2026
Last updated: June 2026 · Sarah Okonkwo, Cold email strategist, 300+ domain setups
TL;DR — 7 things to know before reading
The phrase "unlimited inboxes" is technically accurate for Inframail — the platform does not cap the number of inboxes you can create on a domain — but the practically useful question is not "how many can I create" but "how many should I create and on how many domains." Those are inbox architecture decisions, not product capability questions.
After 300+ domain setups, the inbox architecture mistakes that consistently produce deliverability problems are: too many inboxes on too few domains (concentrating reputation risk), too many inboxes created at once before warmup capacity is available to handle them (launching campaigns from half-warmed inboxes), and inbox sprawl without documentation (losing track of which inboxes are assigned to which campaigns, which are in warmup, and which have had problems). These mistakes are not inevitable; they result from treating inbox creation as a purely mechanical process rather than an architectural one.
This guide covers the architecture: how to calculate the right number of domains and inboxes for your volume target, how to sequence inbox creation against warmup timelines, how Inframail's bulk provisioning tools make the creation process efficient, and how to build a management system that keeps a large inbox portfolio organised. The mechanics of creating a single inbox take five minutes; building an inbox portfolio that can sustain 1,000+ daily emails for months without deliverability problems takes planning.
Inframail provides the Microsoft 365 inboxes and bulk provisioning tools. Instantly provides the campaign management, warmup, and bulk inbox connection tools. Quarvio delivers the contact data at the scale the inbox portfolio can handle. Aimfox adds LinkedIn outreach that runs in parallel.
Before creating any inboxes, calculate your requirements based on your daily send target.
The core formula:
Inboxes needed = Daily send target ÷ emails per inbox per day
Domains needed = Inboxes needed ÷ inboxes per domain
The standard parameters:
Example calculations for common volume targets:
| Daily send target | Inboxes needed (at 40/inbox/day) | Domains needed (at 4 inboxes/domain) |
|---|---|---|
| 200 emails/day | 5 inboxes | 1–2 domains |
| 500 emails/day | 13 inboxes | 3–4 domains |
| 1,000 emails/day | 25 inboxes | 6–7 domains |
| 2,000 emails/day | 50 inboxes | 12–13 domains |
| 5,000 emails/day | 125 inboxes | 31–32 domains |
The deliverability reason to limit inboxes per domain to 3–5 is reputation concentration risk. If a campaign sends from 20 inboxes on one domain and that campaign has a high complaint rate, the entire domain's reputation suffers. With 5 inboxes per domain, the worst case is one domain's inboxes being paused, while 4 other domains' inboxes continue operating normally.
The cost reason to potentially increase inboxes per domain is Inframail's flat pricing. At 10 inboxes per domain, the per-inbox cost is lower than at 5 inboxes per domain. For teams with strong list quality and campaign control (low complaint rates, verified contacts), 8–10 inboxes per domain may be acceptable. For teams with variable list quality, 3–5 per domain limits potential damage.
The most common mistake in scaling inbox creation is not calculating warmup capacity. You can create 25 inboxes today, but you cannot start 25 warmup sequences simultaneously and have all 25 ready for campaigns in 14–28 days. Consider:
The practical approach: create and warm inboxes in batches of 5–10, wait for each batch to complete warmup and reach campaign-ready status before creating the next batch. This produces a slower scale-up but a more reliable portfolio.
What to do: Before creating any inboxes, calculate the total number of domains and inboxes required for your volume target.
Sub-steps:
Benchmark: A 1,000 email/day target at 90 days requires 25 inboxes across 6–7 domains, with the first batch of domains purchased and DNS configured today, and inbox creation happening in 5-inbox batches over 4–6 weeks.
Failure mode: Calculating inboxes without calculating domains, then creating all inboxes on one or two domains and concentrating deliverability risk unnecessarily.
What to do: Purchase the required number of sending domains and configure their DNS for Inframail before creating any inboxes.
Sub-steps:
Benchmark: Setting up 5 domains (purchasing, adding to Inframail, and adding DNS records) takes 2–3 hours including propagation wait time.
Failure mode: Creating inboxes on a domain before DNS is verified. Inboxes created on an unverified domain will not have proper DKIM signing, and warmup and campaign sends will fail authentication.
What to do: Create the first batch of inboxes on your first verified domain. Start with 4–5 inboxes on the first domain; do not create all inboxes on all domains simultaneously.
Sub-steps:
Benchmark: Creating 5 inboxes on one domain takes 10–15 minutes.
Failure mode: Using generic usernames (info@, contact@, team@, sales@) which have higher complaint rates because they are commonly used for opt-in and marketing email and recipients frequently mark them as spam.
What to do: Use Inframail's bulk SMTP export to generate credentials for all created inboxes at once.
Sub-steps:
Benchmark: Bulk export for 25 inboxes takes 3–5 minutes and generates one CSV file.
Failure mode: Exporting individual inbox credentials one at a time when the bulk export is available. Manual credential copying for 25+ inboxes is time-consuming and error-prone.
What to do: Connect all Inframail inboxes to Instantly using the bulk SMTP export CSV rather than adding inboxes one at a time.
Sub-steps:
Benchmark: Bulk import of 25 inboxes into Instantly takes 10–20 minutes including troubleshooting any failed connections.
Failure mode: Connecting inboxes one at a time when bulk import is available. At 5 minutes per inbox for 25 inboxes, manual connection takes over 2 hours; bulk import reduces this to 15 minutes.
What to do: Activate Instantly's warmup feature for all newly connected inboxes before running any campaign sends.
Sub-steps:
Benchmark: Enabling warmup for 25 inboxes takes 15–30 minutes depending on whether bulk warmup activation is available.
Failure mode: Not enabling warmup for some inboxes in the batch because the interface is slow or you are fatigued from the bulk setup process. Every inbox that misses warmup and gets added to campaigns prematurely risks reputation damage.
What to do: Create and maintain a documentation system for your inbox portfolio before inboxes become too numerous to manage by memory.
Sub-steps:
Benchmark: Spreadsheet setup takes 30–60 minutes. Weekly maintenance takes 15–30 minutes. Without documentation, managing more than 15 inboxes becomes operationally unmanageable.
Failure mode: Relying on memory for inbox status across a portfolio of 20+ inboxes. Without documentation, inboxes in different stages (warmup, campaign, paused, retired) become indistinguishable, and it becomes easy to accidentally add an unwarmed inbox to a campaign.
What to do: Continue creating inboxes in batches as earlier batches complete warmup and become campaign-ready, rather than creating all inboxes at once.
Sub-steps:
Benchmark: A staggered schedule producing 25 campaign-ready inboxes takes 8–10 weeks from the first domain registration. This is significantly longer than creating all 25 inboxes today, but produces a more reliable, better-aged portfolio.
Failure mode: Creating all 25 inboxes on day 1 and trying to warm them all simultaneously. This creates 25 simultaneous warmup sequences, all of which complete simultaneously 4 weeks later, followed by 25 inboxes needing campaigns at the same time — an all-or-nothing approach that lacks the risk distribution of staggered creation.
| Target volume | Inboxes needed | Domains needed | Creation schedule | Campaign-ready timeline |
|---|---|---|---|---|
| 200 emails/day | 5 | 1–2 | All at once | 28–60 days |
| 500 emails/day | 13 | 3–4 | 2 batches, 3 weeks apart | 6–8 weeks |
| 1,000 emails/day | 25 | 6–7 | 5 batches, 2 weeks apart | 8–10 weeks |
| 2,000 emails/day | 50 | 12–13 | 10 batches, 2 weeks apart | 14–16 weeks |
| 5,000 emails/day | 125 | 31–32 | 25 batches staggered | 30–40 weeks |
| Setting | Value | Notes |
|---|---|---|
| Inboxes per domain | 3–5 (standard), 8–10 (advanced) | Higher = more risk concentration, lower per-inbox cost |
| Emails per inbox per day | 40–50 (mature), 10–20 (early phase) | Conservative limit per Woodpecker guidelines |
| Warmup minimum before campaigns | 14 days | 28–60 days for full maturity |
| Domain age before use | 30–60 days preferred | Register early, start warmup immediately |
| Inbox username format | First names only | Avoid generic names (info, sales, team) |
Register new domains continuously, 30–60 days before you need them. Even at the minimum warmup volume (10–15 emails per day), a domain that has been sending for 60 days before campaign launch has materially better inbox placement than a day-zero domain.
The practice: every time you launch a new batch of inboxes, also purchase the next batch of domains (to be used 60 days from now) and start them on minimal warmup. By the time you need them, they will be aged and partially warmed. The pipeline runs continuously: create, age, warm, campaign, repeat.
This requires forward planning and a disciplined domain registration schedule, but the payoff is a portfolio where no domain is ever launched cold from day zero.
Rather than assigning inboxes to campaigns randomly, segment domains by campaign type. One domain for first-touch campaigns (highest risk, newest contacts), a separate domain for re-engagement campaigns (lower risk, previously contacted), another for warm referral outreach (lowest risk, highest quality contacts).
First-touch campaigns to unverified or marginally verified contacts carry the highest complaint and bounce risk. Concentrating this risk on dedicated domains protects the domains used for higher-quality sends. If the first-touch domain accumulates complaints, it can be paused without affecting the warmer outreach domains.
No inbox lasts forever. Inboxes that have been sending cold email for 12+ months accumulate complaint history, engagement fatigue signals, and potentially appear on recipient blocklists as recognised cold email senders. Proactively retiring inboxes at the 12-month mark and replacing them with fresh inboxes on the same domain maintains portfolio freshness.
The operational process: when an inbox reaches 12 months, add it to a "retirement queue", reduce its campaign volume to zero over 2 weeks, then deactivate it in Inframail. Simultaneously create a new inbox on the same domain (or a domain added 60 days ago) and begin warmup. This maintains constant inbox count while cycling out aged inboxes for fresh ones.
At scale, the inbox cost is the dominant operational cost in your cold email infrastructure (ahead of the campaign tool subscription and contact data cost). Calculate cost per contact at each volume tier:
Inframail cost per month ÷ total daily sends × 30 ÷ 1 = cost per email sent. Compare this to the cost per reply or cost per meeting booked. If the inbox infrastructure cost is a meaningful percentage of revenue per meeting booked, the incentive to optimise inbox count and per-inbox send volume is clear.
As you scale, optimise by: increasing sends per inbox toward the safe maximum (40–50), increasing inboxes per domain if list quality is strong (reducing domain cost per inbox), and retiring underperforming inboxes rather than leaving idle inboxes in the portfolio.
Maintain a 10–15% reserve of inboxes in warmup at all times, beyond your current campaign needs. These spare inboxes serve as emergency replacements when an active inbox has a deliverability problem and must be pulled from campaigns.
Without spare inboxes, pulling one problem inbox from a campaign reduces sending capacity by the full per-inbox daily volume. With spare inboxes in warmup, a replacement is available within days rather than weeks. The maintenance cost (warmup emails from spare inboxes) is low relative to the capacity assurance benefit.
Symptoms: After bulk importing the Inframail SMTP CSV into Instantly, some inboxes show as "failed" or "connection error."
Diagnosis steps:
Fix: Re-export credentials from Inframail for the failed inboxes and connect them manually. If manual connection also fails, the inbox may not have been fully provisioned in Inframail; contact Inframail support.
Symptoms: After 14 days, warmup scores for a new batch of inboxes are below 60 and not improving.
Diagnosis steps:
Fix: Fix IMAP connectivity for any inbox where IMAP shows as failed. If DNS is the issue, fix authentication records and restart warmup after records are confirmed passing.
Symptoms: When attempting to create inboxes beyond a certain count on a domain, Inframail shows an error or restricts creation.
Diagnosis steps:
Fix: Upgrade your Inframail plan if the current tier has inbox count limits that you have reached. Alternatively, distribute additional inboxes across more domains rather than adding more to a single domain.
Symptoms: Multiple inboxes on the same domain all develop inbox placement problems at the same time.
Diagnosis steps:
Fix: If the entire domain is showing reputation problems, pause all campaigns from that domain. Investigate and fix the root cause (typically high complaint rate from a specific campaign or contact segment). The domain needs a 2–4 week sending pause combined with intensive warmup before resuming.
Symptoms: After creating many inboxes on the same domain, you have exhausted the list of professional first names and are resorting to less professional names.
Diagnosis steps:
Fix: Add more domains rather than adding more inboxes to existing domains. The inbox username is a deliverability signal — professional first names perform better than generic or numbered names. If you need more inboxes, register new domains and use fresh first names on each domain.
Symptoms: The inbox portfolio spreadsheet has 100+ rows and tracking warmup status, bounce rates, and campaign assignments manually is taking significant time.
Diagnosis steps:
Fix: At 50+ inboxes, consider using Instantly's analytics as the primary monitoring tool and simplifying the spreadsheet to track only domain-level data and high-level inbox status (warmup / active / paused / retired). Reserve the detailed per-inbox tracking for problem inboxes only.
A verified user on Inframail reviews on G2:
"Scaling from 10 to 50 inboxes was the point where Inframail's flat pricing made an obvious difference. At 50 inboxes with per-seat pricing at other providers, I would have been paying 5–10x more per month. The bulk SMTP export made connecting all 50 inboxes to Instantly manageable rather than a full-day manual task."
— Verified buyer on Inframail reviews on G2
A thread in r/coldemail (1,204 upvotes):
"The lesson I wish someone had told me at 50 inboxes: the bottleneck is never inbox creation, it's warmup management. Creating 50 new inboxes takes a day. Getting 50 inboxes to campaign-ready status takes 2 months with proper warmup. Plan your scale-up based on your warmup capacity, not your inbox creation speed."
— r/coldemail, 1,204 upvotes
A verified reviewer on Instantly reviews on G2, where Instantly holds 4.9/5 from 2,800+ verified reviews:
"We run 80 inboxes across 18 domains all managed through Instantly with Inframail for provisioning. The inbox documentation spreadsheet is the operational backbone — warmup scores, domain assignment, campaign assignment, problem history. Without that spreadsheet, 80 inboxes is unmanageable. With it, one person can handle the whole portfolio."
— Verified buyer on Instantly reviews on G2
| Need | Tool | Notes |
|---|---|---|
| Inbox creation and SMTP export | Inframail | Flat pricing, bulk export, auto DNS |
| Campaign sending and warmup | Instantly | Bulk inbox import, warmup scores |
| Verified contact data | Quarvio | Scale contacts to match inbox capacity |
| LinkedIn outreach | Aimfox | LinkedIn campaigns alongside email |
How many inboxes can I create on one domain in Inframail?
Inframail does not impose a hard technical limit on inboxes per domain (the "unlimited" in the product name refers to this). However, the deliverability recommendation is 3–5 inboxes per domain to limit reputation concentration risk. Advanced users with strong list quality controls can run 8–10 inboxes per domain. Above 10 inboxes per domain, the risk of one campaign's problems affecting all inboxes on that domain becomes significant.
How many emails can I send per day per inbox?
40–50 emails per inbox per day is the standard limit for fully matured inboxes (8+ weeks of warmup). Per Woodpecker's guide on daily sending limits, 30–50 per day is the recommended range for cold email inboxes on properly warmed accounts. New inboxes in early campaign phase (weeks 5–8) should be capped at 10–20 per day.
How many inboxes do I need to send 1,000 emails per day?
At 40 emails per inbox per day, 1,000 daily emails requires 25 inboxes. At 50 per inbox per day (maximum for mature inboxes), 1,000 daily emails requires 20 inboxes. Plan for 25 inboxes across 6–7 domains to have margin for inbox maintenance, rotation, and some in permanent warmup mode.
How long does it take to build an inbox portfolio for 1,000 emails per day?
Approximately 8–12 weeks from the first domain registration to full volume. The timeline is determined by warmup requirements: each 5-inbox batch needs 28–60 days of warmup. If you create batches every 2 weeks, you reach 25 inboxes (5 batches × 5 inboxes) at week 10, with all 25 campaign-ready by week 10–14.
What should inbox usernames look like?
Professional first names: sarah, ryan, james, marcus, priya, mike, alex, kate, tom, emma. Avoid generic names (info, contact, hello, mail, team, sales) which carry higher complaint rates because they are recognisably generic. Avoid numbered variants (ryan1, ryan2) which look automated. On each domain, 4–5 different first names is sufficient.
Does Inframail support bulk inbox creation?
Inframail's interface allows creating inboxes one at a time, though this is fast (1–3 minutes per inbox). The bulk efficiency is on the export side: Inframail's bulk SMTP export generates credentials for all inboxes at once, which you then import into Instantly in bulk rather than connecting each inbox manually.
Can I use the same Inframail inboxes for both warmup and campaigns?
Yes. The same inbox runs warmup through Instantly's warmup engine while simultaneously sending campaign emails. Warmup should continue running throughout the inbox's active campaign period, not just during the initial warmup phase. The warmup emails generate positive engagement signals that partially offset cold outreach signals and help maintain reputation over time.
What happens if I exceed the recommended inboxes per domain?
There is no hard failure — the inboxes will function. The risk is reputation concentration: if one campaign from this domain generates high complaint rates or bounces, all inboxes on the domain share the reputation damage. With 10+ inboxes on one domain sending at 40+ emails per day each, one problematic campaign can generate 400+ complaints from a single domain, which degrades the domain's reputation for all inboxes and may trigger blocklisting.
How do I manage a large inbox portfolio without losing track of status?
A tracking spreadsheet with one row per inbox is the essential tool. The minimum columns: email address, domain, creation date, warmup start date, campaign-ready date, current status, assigned campaign, weekly warmup score, weekly bounce rate. Update weekly. At 50+ inboxes, consider using Instantly's analytics as the primary tracking tool and the spreadsheet for strategic overview.
What contact volume do I need to match a 25-inbox portfolio?
At 25 inboxes sending 40 emails per day, your capacity is 1,000 emails per day × 30 days = 30,000 emails per month. With a 3-step sequence per contact, you can reach 10,000 new contacts per month. Quarvio delivers 10,000 contacts at $199 — one order per month matches the capacity of a 25-inbox portfolio.
Scale your inbox portfolio with verified contacts
Inbox capacity is only valuable when matched with sufficient clean contact data. At 25 inboxes sending 40 emails per day, you need approximately 10,000 fresh, verified contacts per month to maintain full sending capacity without re-contacting the same prospects too frequently.
Quarvio delivers pre-verified B2B contacts at $129 for 5,000 contacts through $699 for 50,000 contacts. 90% deliverability guarantee, 12-month credit validity, unused credits carry forward.
Start your contact order at Quarvio →