Home › Blog

Cold Email Infrastructure for Agencies: Domains, Mailboxes, Warm-Up and Cost

By BobWork07 Nov 202612 min read
Agency cold email infrastructure diagram with client domains, mailboxes, warm-up pools, DNS checks and cost ladder.

For most agencies, cold email infrastructure means 2–5 mailboxes per sending domain, 30–50 cold emails per mailbox per day, and 2–3 weeks of warm-up for new domains. If you ignore that spacing, one bad list can damage a whole client cluster. This guide gives the setup, costs, pool choices, import flow and weekly controls.

A reliable agency stack is not one inbox sending harder. It is many modest senders, clean DNS, clear client boundaries and measurable warm-up health. If you are still sizing volume, start with the mailbox math in how many mailboxes you need for cold email, then use this page to turn the numbers into operating infrastructure.

What is cold email infrastructure?

Cold email infrastructure has five layers: domains, mailboxes, DNS, warm-up and control. Each layer should be visible to your team and explainable to the client.

Use secondary sending domains for outreach, not the client’s main website domain. Keep the brand recognisable, but separate enough that outreach problems do not hit normal business mail.

Each mailbox should behave like a normal human sender. It needs authentication, a profile name, working replies and a daily cap. It should not jump from zero to campaign volume overnight.

SPF, DKIM and DMARC are not optional. Google, Yahoo and Microsoft expect authenticated mail for bulk or higher-volume senders. Google says spam complaint rate should stay below 0.1% and never reach 0.3%.

Warm-up should create normal sending, receiving, replies, spam rescue and thread activity before campaigns start. Keep it running during campaigns at a lower steady level.

LayerAgency operating ruleNumber to useFailure sign
DomainsUse secondary domains per client2–5 mailboxes per domainOne domain carries too much volume
MailboxesUse named sender inboxes30–50 cold emails/dayBounces or spam rate rise
Warm-up ageRamp before campaigns7 days existing, 2–3 weeks newMailbox starts outreach too soon
Warm-up volumeKeep active during campaigns10–15/dayNo ongoing positive activity
DNSSPF, DKIM, DMARCDMARC at least p=noneAuthentication fails
Google complaintsMonitor where possibleBelow 0.1%, never 0.3%Complaint warnings or spam placement
Yahoo complaintsFollow sender rulesBelow 0.3%Filtering or blocking
ScalingAdd mailboxes, then domainsDo not force one inboxProvider locks or throttling

Use this table as an operating policy, not a one-time setup sheet. Client lists change. A list that behaved last month can still create complaints this month.

How many domains and mailboxes?

Start with the client’s target daily send volume. Then work backwards from mailbox limits.

If a client wants 300 cold emails per day, use about 6–10 sending mailboxes at 30–50 per day. With 2–5 mailboxes per domain, that usually means two to five domains.

If a client wants 1,000 cold emails per day, do not put that on 10 aggressive inboxes. Use about 20–34 mailboxes across several domains. The exact number depends on reply quality, bounce rate, complaints and domain age.

New domains need more patience. Use a 2–3 week warm-up before normal outreach. Existing domains with clean history may be ready after about 7 days, but only if authentication passes and warm-up signals are clean.

Client targetMailboxes at 30/dayMailboxes at 50/dayDomains at 2–5 eachNotes
150/day531–3Starter client cluster
300/day1062–5Watch list quality closely
500/day17104–9Launch by domain in stages
1,000/day34207–17Needs stronger monitoring
2,000/day674014–34Treat as infrastructure

Do not average all clients together. A high-risk client list should not consume the reputation budget of a cautious client. Each client needs its own domains, mailboxes, unsubscribe suppression and health reporting.

For a repeatable launch pack, start with two domains, six mailboxes, 21 days of warm-up, then 180–300 cold emails per day if early signals are clean.

Which DNS records must pass?

Set DNS before warm-up. Warm-up cannot compensate for broken authentication.

SPF tells receivers which services may send for the domain. Keep SPF under the 10 DNS lookup limit. If you send through Google Workspace, Zoho, SendGrid, Mailgun, Amazon SES or another provider, include only the services you actually use.

DKIM signs messages. Enable DKIM for every sending provider. Common selectors include google, zmail, default, selector1, selector2, k1, s1, mail, dkim, lark, feishu and zoho.

DMARC tells receivers what to do when SPF or DKIM alignment fails. Start with p=none while you verify alignment and reporting. Move stricter only when legitimate mail passes consistently.

Google’s sender guidance covers authentication, complaints and one-click unsubscribe for applicable bulk senders. Use Google’s email sender guidelines as the primary reference for Gmail and Google Workspace recipients.

Yahoo requires SPF and DKIM, DMARC at least p=none, aligned From domains, one-click unsubscribe for bulk, unsubscribe handling within two days and a spam rate below 0.3%. Use Yahoo’s sender best practices when campaigns target Yahoo addresses.

Microsoft requires SPF, DKIM and DMARC with alignment for domains sending more than 5,000 emails per day to Outlook.com consumer mailboxes. Microsoft does not state a numeric complaint threshold in the same way. Use Microsoft’s Outlook.com sender requirements for high-volume planning.

For implementation details, keep SPF, DKIM and DMARC for cold email open while you create records. If Gmail placement is already weak, use Gmail emails going to spam before adding more mailboxes.

Should clients use private pools?

Warm-up pools decide who exchanges warm-up mail with whom. Agencies should treat this as a client-boundary decision.

A shared warm-up network is faster to start because one mailbox can warm with other active mailboxes in the network. A private pool is stricter. Only mailboxes inside that account exchange warm-up mail, so it needs at least two mailboxes.

BobWork Email Warm-up uses a shared warm-up network by default, with private pool available per account from Mailbox pool → Pool mode. If you switch an account to private pool, that account’s mailboxes only warm each other. The live shared-network count is shown in the dashboard.

For agencies, the important detail is that private pool mode is per account. If Client A and Client B need separate private pools, put them in separate accounts. Do not place both clients in one account and expect separate private pools inside it.

Use private pools when a client requires isolation, when you manage a large client fleet, or when the client does not want addresses entering a shared network. Use the shared network when you need a simple start, have one mailbox, or do not require client-level isolation.

In BobWork, warm-up emails are generated as short office notes. They contain no links or images. Real mail is never read, moved or answered; the engine only handles warm-up mail carrying its own hidden header.

The ramp starts at 3 emails per day, adds 2 per day, and caps at 30 per day by default. The cap is editable per mailbox up to 100. Weekends run at 30%. Sends spread across 09:00–18:00 in the mailbox’s own time zone.

About 40% of received warm-up mail gets a reply. Threads end after three messages. Warm-up mail found in Spam is moved to Inbox, marked read, labelled Warm-up and archived after 24 hours.

How do you import mailboxes?

Manual setup breaks once an agency manages 20, 50 or 500 mailboxes. Use CSV onboarding where possible.

In BobWork Email Warm-up, go to Add mailbox → Many mailboxes: upload a CSV. Paste or upload rows with email, app_password and name. For Gmail, Yahoo and iCloud, the host settings are filled in. For other domains, add imap_host.

Every row gets the same IMAP and SMTP login test as a single mailbox connection. Failed rows are listed with the reason. Already-connected rows are skipped, so re-uploading the same CSV is safe.

Mailboxes above the free limit need billing active before they connect. New accounts get up to 3 mailboxes free per person or company domain, with no card and no time limit. Extra mailboxes are priced by volume.

The default account limit is 200 mailboxes. Larger fleets, such as 500 or 1,000 mailboxes, can request a higher limit by email. Each mailbox ramps on its own schedule, so 500 mailboxes can reach up to 15,000 warm-up emails per day once fully ramped at 30 each.

Use app passwords where providers require them. Gmail and Google Workspace are best connected through IMAP with an app password, which needs 2-Step Verification. One-click Google sign-in also exists, but Google shows an unverified-app notice and caps unverified apps at 100 users.

Zoho Mail can connect through the Zoho Mail API with a Self Client code, including on Zoho’s free plan. Zoho can also connect by IMAP on Mail Lite and above. Lark, Yahoo and iCloud use IMAP with app or mail-client passwords.

Amazon SES, SendGrid and Mailgun use the platform’s SMTP credentials for sending plus a receiving inbox over IMAP. Outlook and Microsoft 365 are not supported yet because Microsoft requires OAuth for this connection path. The Outlook warm-up guide explains the current gap.

What will the fleet cost?

Agency infrastructure pricing changes sharply at volume. Cost the whole fleet, not the first inbox.

BobWork’s current model for new accounts is 3 free mailboxes. Extra mailboxes use one rate across all extras: $5 each for 1–9 extra, $3 each from 10 extra, and $2 each from 50 extra. Billing is through Stripe, prorated and cancellable any time. Extra mailboxes pause without billing.

Yearly billing is available for extra mailboxes at 10 times the monthly price. That gives two months free compared with paying monthly.

Total mailboxesFree mailboxesPaid extrasMonthly costYearly costBest fit
532$10$100Test client
1037$35$350Small client cluster
20317$51$510Multi-domain starter
50347$141$1,410Small agency pool
100397$194$1,940Several clients
2003197$394$3,940Default large limit
5003497$994$9,940Large agency fleet
1,0003997$1,994$19,940Enterprise-scale operation

The price per mailbox falls to $2 from 53 total mailboxes on a new account because that is where you reach 50 paid extras. Older accounts may have different free allowances, but new accounts should be planned around 3 free mailboxes.

For deeper comparisons, use email warm-up cost per month and cheapest way to warm up 50 inboxes. If you run a service business, also read email warm-up tools for agencies.

How should agencies control risk?

Do not rely only on a human checking dashboards. Add gates to your operating process.

At minimum, block cold outreach until a mailbox has warmed for at least 7 days, has a 7-day spam rate at or below 10%, and has received at least 30 warm-up emails. In BobWork, that is the ready-for-outbound gate.

Spam rate is measured as the share of a sender’s warm-up mail that receiving mailboxes found in Spam over 7 days. That is direct mailbox observation, not a third-party seed-list estimate.

The health score runs from 0 to 100. Healthy is 85 or higher. Watch is 60–84. At risk is below 60. Blocked means login or permission failed.

BobWork exposes a REST API with personal keys, Bearer auth and 120 requests per minute per key. It covers mailboxes, warm-up stats, domain checks, IMAP and Zoho connections, campaigns and contacts. API access is free; outbound sends triggered through it use credits if you use the sending product.

There is also a remote MCP endpoint at https://app-emailwarmup.bobwork.ai/mcp using the same Bearer key. AI assistants and agents can use it to check warm-up, connect mailboxes, check DNS and run outbound campaigns.

Use API or MCP controls to check every mailbox connection each morning, export client-level health, verify SPF, DKIM and DMARC before launch, and stop campaigns when bounce or spam signals cross your threshold. The email warm-up API guide covers the automation model.

StepActionHow to verify
1Confirm client separationNo unrelated clients share sender domains
2Check mailbox densityEach domain typically has 2–5 mailboxes
3Verify DNSSPF, DKIM and DMARC pass
4Review warm-up ageNew domains have 2–3 weeks; existing domains have 7+ days
5Check 7-day spam ratePause mailboxes above 5% for a few days
6Confirm ready gate7+ days warming, spam ≤10%, 30+ received
7Audit cold volumeEach mailbox stays around 30–50/day
8Keep warm-up runningWarm-up remains around 10–15/day
9Check unsubscribe handlingRequired one-click unsubscribe and suppression work
10Review bouncesAct on the alert above 10% bounce rate

The 5% spam-rate pause rule is stricter than the ready gate. It gives you time to fix a mailbox before it becomes a client problem.

Also check list source and message fit. Warm-up cannot repair a purchased list, misleading subject line or irrelevant offer. Postmark, for example, requires permission-based lists and prohibits purchased or rented lists, so it is not a cold email route.

BobWork’s outbound product is optional. If you use it, only mailboxes that passed the ready gate can send. It sends 30 cold emails per day in the first week after ready and 50 per day after, inside working hours, with 4–9 minutes between sends. Warm-up keeps running on the same mailboxes.

The practical agency setup is simple: isolate clients, spread volume, warm before sending, measure every mailbox and pause early. BobWork Email Warm-up at emailwarmup.bobwork.ai can handle the warm-up layer with CSV import, shared network or private pool per account, DNS checks, API access and MCP controls.

What do agencies ask?

How many mailboxes per domain?

Typically use 2–5 mailboxes per sending domain. Add more domains instead of forcing more mailboxes onto one domain. This keeps volume spread out and makes it easier to pause a damaged domain.

Should each client use private warm-up?

Use a private pool when a client requires isolation or when you manage many mailboxes for that client. A private pool needs at least two mailboxes. If isolation is not required, a shared warm-up network can start with one mailbox.

How long should new domains warm?

Use 2–3 weeks for a new domain before normal cold outreach. Existing domains with clean history can often start after 7 days if DNS is correct, spam rate is low and the mailbox has received enough warm-up mail.

Can one account manage all clients?

It depends on the isolation model. One account can manage many mailboxes, but private pool mode is per account. If every client needs its own private pool, use a separate account per client.

What daily mailbox limit is safe?

A typical operating range is 30–50 cold emails per mailbox per day after warm-up. New mailboxes should start lower. Add mailboxes and domains for more volume instead of pushing one mailbox too hard.

Does warm-up guarantee inbox placement?

No. Warm-up helps build mailbox activity and detect spam placement problems, but it does not guarantee inbox placement. DNS, list quality, relevance, complaints, bounces, unsubscribe handling and provider rules still decide delivery.

Frequently asked questions

How many mailboxes should an agency put on one domain?

Typically use 2–5 mailboxes per sending domain. Add more domains instead of forcing more mailboxes onto one domain. This keeps volume spread out and makes it easier to pause a damaged domain without stopping every client campaign.

Should each client have a private warm-up pool?

Use a private pool when a client requires isolation or when you manage many mailboxes for that client. A private pool needs at least two mailboxes. If isolation is not required, a shared warm-up network can start with one mailbox.

How long should agencies warm new client domains?

Use 2–3 weeks for a new domain before normal cold outreach. Existing domains with clean history can often start after 7 days, provided DNS is correct, spam rate is low and the mailbox has received enough warm-up mail.

Can one agency account manage all clients?

It depends on the isolation model. One account can manage many mailboxes, but private pool mode is per account. If every client needs its own private pool, use a separate account per client rather than mixing them in one account.

What daily cold email limit is safe per mailbox?

A typical operating range is 30–50 cold emails per mailbox per day after warm-up. New mailboxes should start lower. Add mailboxes and domains for more volume instead of pushing one mailbox too hard.

Does warm-up guarantee inbox placement?

No. Warm-up helps build mailbox activity and find spam placement problems, but it does not guarantee inbox placement. DNS, list quality, relevance, complaints, bounces, unsubscribe handling and provider rules still decide delivery.

Can agencies automate infrastructure checks?

Yes, if the warm-up tool exposes an API or MCP server. Useful checks include mailbox connection state, spam rate, health score, SPF, DKIM, DMARC and campaign readiness before a mailbox is allowed to send.

Warm up your mailboxes free

Connect Gmail, Google Workspace, Zoho or Lark. Your mailboxes warm on a shared network, or in a private pool of your own, starting today.

Start free