Unlimited email inbox setup guide: from domain to sending

This workflow suits agencies running 50 to 200 cold email domains that want to cut manual DNS work, which takes 12+ hours across 50 domains, to minutes with aut

Unlimited email inbox setup guide: from domain to sending

TL;DR: This workflow suits agencies running 50 to 200 cold email domains that want to cut manual DNS work, which takes 12+ hours across 50 domains, to minutes with automated configuration. Inframail charges $147/month flat for unlimited inboxes on a dedicated IP, breaking even against Google Workspace ($8.40 per seat, Flexible Plan) at roughly 18 inboxes and saving $273/month at 50 inboxes before domain and warmup costs. Inframail does not include warmup, so budget $15-50 per inbox monthly for an external tool and 2 to 6 weeks of warmup before full sending volume. Domain costs run $5-16 per year.

Setting up 50 cold email domains manually takes 12+ hours, and Google Workspace charges $8.40 per seat on the Flexible Plan, so 50 inboxes cost $420/month before domains or warmup tools. Inframail reports the same batch takes minutes instead of hours with automated DNS configuration, at a flat $147/month (domain and warmup costs are additional).

This guide walks through the full domain-to-sending workflow with specific numbers, costs, and export formats.

Prerequisites for setting up your cold email inboxes

This section lists the infrastructure you need, the costs to plan for, and the five-step workflow from domain to first send.

Essential infrastructure for cold email

Your cold email infrastructure requires four building blocks:

  1. Domains: Secondary domains separate from your primary business domain. These carry your cold email sends and protect your main domain's reputation.
  2. Email infrastructure platform: The service that provisions inboxes, configures DNS records, and manages IP reputation. This is where Inframail operates.
  3. Warmup tool: An external service that builds sending reputation on new inboxes. Inframail does not include built-in warmup, so budget for a tool like Lemwarm. Warmup tools typically run $15 to $50 per inbox per month.
  4. Sending platform: The campaign tool that connects to your inboxes via IMAP/SMTP and manages sequences. Instantly.ai and Smartlead are the two most common agency choices. Inframail covers the domain and infrastructure platform components, which include domain purchase or migration, SPF/DKIM/DMARC setup, dedicated IPs, and inbox provisioning with IMAP/SMTP credentials. Warmup and the sending platform are external line items.

Understanding your total cost of ownership

Total cost of ownership includes four cost line items: platform fee, domain costs, warmup tools, and sending platform. These line items fund five core infrastructure components: domains, inboxes, SPF/DKIM/DMARC records, sending IPs, and warmup. Per-seat pricing (Google Workspace, Microsoft 365) scales linearly with inbox count, but flat-rate pricing (Inframail) does not. Inframail's detailed cost savings calculation guide walks through the full TCO model.

Workflow: from domain to first send

The full setup follows five steps:

  1. Set up and link your sender domains.
  2. Deploy SPF, DKIM, and DMARC records.
  3. Provision unlimited email inboxes in batches.
  4. Export IMAP/SMTP credentials to CSV.
  5. Connect inboxes to your sending platform.

This step covers choosing a registrar, sizing the number of domains per client, and adding domains to Inframail.

Best domain registrars for cold email

Common registrars for secondary domains include Namecheap and GoDaddy. Inframail also lets you purchase domains directly at $5 to $16 per year, removing a separate registrar login, or migrate existing domains without losing access at your current registrar.

Determining ideal domains per client

Domains per client depends on daily sending volume. Operators commonly recommend 30 to 50 cold emails per inbox per day. Keep new mailboxes well below that range during their first weeks.

A client sending 300 cold emails daily needs at least 10 inboxes. At 3 inboxes per domain, that's 4 domains per client. For 15 active clients at similar volume, you need 60 domains and 150 inboxes. The Inframail sending capacity calculator models this before you commit to a plan.

Adding domains to Inframail

In the Inframail dashboard, enter a domain name and select "purchase" or "migrate." The platform registers the domain or links your existing domain without requiring registrar DNS panel access. Domain turnaround is instant, so you can provision inboxes right after adding a domain.

Step 2: Rapidly deploy SPF, DKIM, and DMARC

This step is where most of the 12+ hours of manual setup disappears. DNS setup involves three authentication records per domain, each requiring precise syntax.

How Inframail handles SPF configuration

SPF (Sender Policy Framework) tells receiving mail servers which IP addresses can send email on behalf of your domain. A typical Microsoft-hosted SPF record:

v=spf1 include:spf.protection.outlook.com ~all

When you add a domain, Inframail generates and publishes the SPF record automatically. Automated record creation eliminates the manual copy-paste step that introduces syntax errors across 50 domains. Without automation, you'd log into your registrar, create a TXT record, paste the syntax, save it, and repeat per domain.

Streamlining DKIM for email deliverability

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing messages so receiving servers can verify the message wasn't altered in transit. The record publishes as a TXT entry in your DNS zone.

Inframail generates the DKIM key pair and publishes the public key without manual panel work. Customers report 10 inboxes configured in 2 minutes, including all three authentication records.

Configuring DMARC for domain security

DMARC tells receiving servers how to handle messages that fail SPF or DKIM checks. The rua parameter specifies where aggregate reports are sent. The address you@domain.com in the table is an example only, so replace it with your actual monitoring address before you apply or publish any of these records. DMARC enforcement follows a progression from monitoring to full rejection:

Policy level Record syntax What it does
Monitoring (p=none) v=DMARC1; p=none; rua=mailto:you@domain.com Collects reports, takes no action on failures
Quarantine (p=quarantine) v=DMARC1; p=quarantine; rua=mailto:you@domain.com Sends failing messages to spam or junk
Reject (p=reject) v=DMARC1; p=reject; rua=mailto:you@domain.com Blocks failing messages outright

Start at p=none for 2 to 4 weeks to monitor results, then move to p=quarantine, then p=reject once legitimate mail passes consistently. Inframail sets the initial DMARC record automatically when a domain is added.

Expected propagation and wait times

DNS changes typically take up to 24 to 48 hours to propagate. ISP caching is the variable, so some changes take longer.

Inframail's automated verification checks that DNS records are live, so you don't have to poll each registrar manually. The platform creates and verifies the records, but propagation still depends on your registrar and TTL settings, so a record can take longer to show as live. Inframail's SPF, DKIM, and DMARC setup video shows the records being configured in real time.

Step 3: Provision unlimited email inboxes instantly

This step covers creating inboxes in batches, naming them consistently, and assigning dedicated IPs.

Speed up inbox setup with batching

Batch provisioning creates dozens of inboxes in a single action. In the Inframail dashboard, select the domains, specify inboxes per domain, and confirm. The platform provisions all inboxes simultaneously and generates credentials.

Customer testimonials report spinning up 10 inboxes in 2 minutes. By comparison, 50 individual Google Workspace accounts each require user setup, password creation, and license assignment.

Naming systems for simple inbox management

Consistent naming prevents confusion at export and import. A reliable pattern is firstname.lastname@clientdomain.com or role01@clientdomain.com, and names should look like real people because generic role-based addresses like info@ or support@ rarely convert in cold outreach.

For example, provisioning 3 inboxes on apexoutreach.com for client Apex Consulting:

Keep a spreadsheet mapping inbox names to clients so credential export and campaign assignment stay organized.

Assigning IPs to boost inbox performance

Inframail provisions inboxes on dedicated US-based IPs, not shared pools. Shared IP pools work like carpool lanes where other drivers affect you, so one bad sender gets the whole block flagged. Dedicated IPs are private lanes where your sending behavior alone determines reputation.

The Unlimited Plan includes 1 dedicated US-based IP. The Agency Pack includes 3, letting you segment clients across separate addresses. Inframail's technical architecture guide covers the IP architecture in detail.

Step 4: Retrieve IMAP and SMTP access keys

This step covers exporting IMAP and SMTP credentials in bulk, what the CSV contains, and how to store it safely.

Batch exporting IMAP and SMTP details

After provisioning, the Inframail dashboard exports all credentials to a CSV file in one action. For agencies running 100+ inboxes across clients, batch export replaces the manual process of logging into each inbox to note server settings and saves hours per onboarding cycle. The Inframail platform walkthrough shows the full flow from registration through bulk export and Instantly import at the 11:20 mark.

Breakdown of exported inbox details

The exported CSV includes per inbox:

  • Email address: The full inbox address (e.g., sarah.chen@apexoutreach.com).
  • IMAP host: The server address for retrieving incoming mail.
  • IMAP port: Typically 993 for SSL connections.
  • SMTP host: The server address for sending outgoing mail.
  • SMTP port: Typically 587 or 465 depending on encryption.
  • Username: Usually the full email address.
  • Password: The inbox-specific password generated during provisioning.

Each field maps directly to connection settings in Instantly.ai or Smartlead.

Protecting your exported credentials

The exported CSV grants full sending access to every inbox. Store it in a password manager or encrypted drive, not a shared Google Sheet or Slack channel, and delete the CSV from your local machine after import.

Step 5: Connect provisioned mailboxes to your sending platform

This step covers importing the exported CSV into Instantly.ai or Smartlead and confirming that each mailbox works.

Importing credentials into Instantly.ai

Instantly.ai supports bulk CSV import. Map the columns from your Inframail export to Instantly's fields: email address, IMAP host, IMAP port, SMTP host, SMTP port, username, and password.

If a mailbox fails after import, the usual cause is a CSV typo or a DNS record that hasn't fully propagated. The Inframail demo showing unlimited inbox creation covers the connection process end to end.

Importing mailboxes into Smartlead

Smartlead also supports bulk CSV import. Smartlead expects the same IMAP and SMTP fields as Instantly.ai, so the Inframail export maps directly without reformatting.

Run Smartlead's connection test on each imported inbox and confirm it passes before starting campaigns. If the test fails, double-check the SMTP port or wait for DNS propagation.

Confirming successful mailbox integration

After import, verify each mailbox with a test email and check three things:

  1. Authentication pass: The test email passes SPF, DKIM, and DMARC checks.
  2. Inbox placement: It lands in the primary inbox, not spam.
  3. Reply routing: Replies appear in your sending platform's unified inbox.

If any mailbox fails, check the Inframail dashboard for DNS verification status before troubleshooting the sending platform.

Optimizing inbox warmup for faster client launches

Inframail does not include warmup, so this section covers why warmup matters, what it costs, and how to confirm DNS before sending.

How warmup protects your sender reputation

New domains and inboxes have zero sending history, so email providers flag them as suspicious by default. Warmup builds trust gradually by sending and receiving small volumes that increase over time, simulating organic usage. Without it, a new inbox sending 30 cold emails on day one is likely to get flagged.

Inframail doesn't include built-in warmup, a deliberate trade-off in the flat-rate model. You bring your own service and control that cost separately. The Inframail warmup migration guide covers the recommended approach.

Warmup duration and pricing

Plan for 2 to 3 weeks of warmup for a new inbox on an existing domain before full campaign volume, or 4 to 6 weeks for a new inbox on a brand-new domain. Warmup tools typically run $15 to $50 per inbox per month, which comes to about $750 to $2,500/month for 50 inboxes. These costs apply whether you're on Inframail or Google Workspace.

Validating DNS for immediate sending

Before starting warmup or any sends, confirm your DNS records are live. Use a DNS checker to verify SPF, DKIM, and DMARC resolve correctly per domain. The Inframail dashboard shows verification status for every domain, so you can confirm authentication without leaving the platform.

If a record shows unverified, wait 15 to 30 minutes and recheck. Record creation is instant, but propagation across all resolvers can still take time depending on TTL settings.

Cost comparison: Inframail vs. current stack

This section compares Inframail's flat rate with Google Workspace per-seat pricing, including the break-even point and competitor pricing.

Google Workspace per-seat pricing

Google Workspace Business Starter costs $8.40 per user monthly on the Flexible Plan or $7.00 on the Annual Plan. For 50 inboxes on Flexible, that's $420/month. At 200 inboxes, the cost reaches $1,680/month in infrastructure alone ($8.40 x 200). Every new client adds a linear cost increase regardless of actual sending volume per inbox.

Predictable costs for unlimited inboxes

Inframail's Unlimited Plan costs a flat $147/month for unlimited inboxes, with a dedicated IP included, and domains run $5 to $16 per year. At the top of that range, 50 domains cost $800/year (50 x $16), which amortizes to approximately $66.67/month. That puts total infrastructure at approximately $213.67/month ($147 platform fee plus $66.67 in domains).

The Inframail vs. Google Workspace cost comparison breaks this down across multiple scales. Warmup tools apply on both sides and aren't included here.

Break-even point by inbox count

At $8.40 per inbox on Google Workspace Flexible, platform cost reaches $147/month at approximately 18 inboxes. Above that, Inframail's flat rate is cheaper:

Inbox count Google Workspace (Flexible) Inframail (platform only) Monthly savings
18 $151.20 $147 $4.20
50 $420 $147 $273
200 $1,680 $147 $1,533

Savings shown reflect platform fees only. Domain costs ($5-16/year each) and warmup tools ($15-50/inbox/month) apply on both sides and are not included.

At 50 inboxes, Google Workspace costs $420/month and Inframail's platform fee is $147/month. That's $273/month in platform savings alone, or $3,276 annually. For agencies managing 200+ inboxes, the scaling case for unlimited inboxes becomes even more pronounced.

"Unlimited inboxes on a flat price? That alone saves me hundreds every month compared to Google Workspace or similar." - Verified user review of Inframail

Competitor pricing follows different models and changes frequently. Based on each provider's published rates, Maildoso charges per mailbox, starting at $2.50 per mailbox at 30 mailboxes and dropping to $0.49 at 1,000. Infraforge lists pricing from $4 per mailbox monthly billed annually with a 10-mailbox minimum plus $99 per month for a dedicated IP add-on. Inframail's Unlimited Plan costs a flat $147/month and includes the dedicated IP at no extra charge.

Get started with Inframail

Inframail is a flat-rate Microsoft email infrastructure provider for agencies running 50 to 200 cold email domains. It costs $147/month for unlimited inboxes with a dedicated US-based IP, and it automates SPF, DKIM, and DMARC setup.

Watch this case study video and see how Inframail helped a client maintain reliable, cost-effective cold email infrastructure for over a year, build momentum with faster responses and increasingly consistent outreach over the last 60 days, and secure $42,000 in new sales within four weeks.

Sign up to Inframail and run a pilot with 10 domains to measure actual time-to-first-send against your current setup.

FAQs

These answers cover setup time, existing domains, blacklist handling, warmup tools, and campaign migration.

How long does full setup take from domain purchase to sending?

Domain purchase, DNS configuration, and inbox provisioning take minutes instead of hours with Inframail's automation. Warmup adds roughly 2 to 3 weeks (4 to 6 weeks for a new domain) before full campaign volume, so total time-to-first-send comes to a short setup plus the warmup period.

Can I use domains I already own?

Yes. Inframail supports migrating existing domains from any registrar and auto-configures SPF, DKIM, and DMARC records without manual DNS panel access.

What happens if an inbox gets blacklisted?

Inframail's deliverability monitoring dashboard detects blacklist events and auto-submits delisting requests on your behalf, and the company reports a 68.3% delisting success rate within 48 hours across those requests.

Do I need separate warmup tools or is it built in?

Warmup is not built into Inframail's self-service plans. Warmup tools typically run $15 to $50 per inbox per month, and Lemwarm is one example.

How do I migrate active campaigns from Google Workspace?

Export IMAP/SMTP credentials from Inframail to CSV, import into Instantly.ai or Smartlead, and run warmup on the new inboxes before switching campaign traffic. Migration risk is limited to the warmup period, not a full rebuild.

Key terms glossary

SPF, DKIM, DMARC: Email authentication protocols that verify sending identity. SPF authorizes sending servers, DKIM signs messages cryptographically, and DMARC tells receivers how to handle authentication failures.

IMAP and SMTP: IMAP (Internet Message Access Protocol) retrieves incoming mail from a server. SMTP (Simple Mail Transfer Protocol) sends outgoing mail. Both are required for cold email sending platforms to connect to your inboxes.

Dedicated IP vs. shared IP: A dedicated IP is used exclusively by your sending infrastructure, so your behavior alone determines reputation. A shared IP pool mixes your reputation with other users on the same range.

Inbox placement rate: The percentage of sent emails landing in the recipient's primary inbox rather than spam or promotions folders. Inframail reports a 98%+ deliverability rate across its infrastructure, though actual placement depends on domain age, warmup status, and sending behavior.

DNS propagation: The time DNS record changes take to spread across the internet's resolver network. Propagation typically takes 24 to 48 hours, though automated platforms can verify records faster.