Cold Email Infrastructure Checklist: The 2026 Setup Guide
A cold email infrastructure setup is secondary domains, lightly used mailboxes, correct SPF, DKIM and DMARC records, a gradual warm-up and monitoring that tells you when to pause. This checklist walks through each step with sourced limits and a launch-day table.
By Jerome Wrigley, GTM Engineer at Cruxfinder · Updated November 1, 2026
A cold email infrastructure setup is a set of secondary sending domains, several lightly used mailboxes per domain, correct SPF, DKIM and DMARC records, a gradual warm-up, and monitoring that tells you when to pause. Get those right and copy has a chance to be read. Get them wrong and the best sequence in the world lands in spam.
This is the full cold email setup checklist for 2026: domain and mailbox sizing, Google Workspace versus Microsoft 365 versus private SMTP, DNS record formats, what Google, Yahoo and Microsoft require, sourced sending limits, warm-up schedules, tracking trade-offs, bounce and complaint thresholds, and a launch-day table. If you only want the sizing math, use the Outbound Meeting Math Calculator.
Cold email infrastructure: domains and mailboxes
Infrastructure is everything between your list and the recipient's inbox: domains, mailboxes, DNS authentication, the sending platform, tracking links and monitoring. The goal is simple. Spread a modest volume across enough separate identities that no single one carries risk, and keep your real company domain out of the blast radius.
Why use secondary domains
Send cold email from secondary domains, not your main company domain. If a campaign draws complaints, the damage lands on a throwaway domain instead of the domain your sales, billing and support teams use every day. Lemlist's benchmark article gives the same advice: use a dedicated domain for outreach rather than your primary company domain (lemlist, 2026, see Sources).
Practical rules for choosing them:
- Pick names close to your brand, such as a different suffix or a short prefix. Avoid lookalikes of other companies.
- Forward the domain's web address to your real site, so a curious prospect lands somewhere credible.
- Give every domain its own SPF, DKIM and DMARC records. Google's DKIM instructions say each domain needs its own unique key.
- Keep a sheet of domain, provider, creation date and warm-up start. You will retire some domains.
How many mailboxes per domain
Cruxfinder's planning assumption is about three mailboxes per domain, with a ceiling of around 300 emails per mailbox per day. Treat both as planning inputs, not provider rules. The sourced data below shows real senders send far less per mailbox, so lower the 300 before you trust any output.
A worked example: sizing a 2,000 contact month
This is an illustration with stated assumptions, not a client result.
- Goal: contact 2,000 new people in a month.
- Sequence: 3 emails each, so 6,000 emails.
- Sending days: 21 weekdays, so about 286 emails per day.
- Mailboxes per domain: 3 (planning assumption).
| Per-mailbox daily cap | Mailboxes needed | Domains needed (3 per domain) | Comment |
|---|---|---|---|
| 30 | 10 | 4 | Conservative, close to the busiest quarter of senders in Smartlead's data |
| 50 | 6 | 2 | Smartlead's stated ceiling per mailbox |
| 300 | 1 | 1 | The planning ceiling, not a safe operating level |
Round up and add a spare mailbox per domain so you can pause one without cutting volume. At 30 per day that is 4 domains and 12 mailboxes. Then run the volume through the Cold Email ROI Calculator to see whether it produces enough meetings to justify the cost.
Google Workspace vs Microsoft 365 vs private SMTP mailboxes
Most cold email programs use one of three mailbox types. Each has real limits, and none is universally best.
| Option | Documented limits | Strengths | Watch-outs |
|---|---|---|---|
| Google Workspace | 2,000 messages per user per day, 1,500 for mail merge, 500 for trial accounts, rolling 24 hours (Google) | Very common, easy API connection to sending tools, strong Gmail placement tooling through Postmaster Tools | Hitting a limit blocks new sends for up to 24 hours. Trial accounts have lower limits |
| Microsoft 365 (Exchange Online) | 10,000 recipients per day, 30 messages per minute, 500 recipients per message by default (Microsoft) | Natural fit for recipients on Outlook and Microsoft 365 | Microsoft states Exchange Online "isn't designed for bulk mailing scenarios" |
| Private SMTP mailboxes | Set by your host or provider | Full control of IP, reverse DNS and headers | You own PTR records, IP reputation and every technical mistake |
What the numbers tell you
Provider caps are ceilings, not targets: Smartlead's data puts the median cold mailbox at about 14 sends per day.
Smartlead's 2026 data also splits contacts per reply by recipient provider: 90 for Gmail, 120 for Outlook and 179 for custom servers. That is a vendor's platform data and does not prove a mailbox type causes better replies, because audiences differ. Lemlist's article recommends matching providers, so Gmail recipients get mail from Gmail mailboxes and Outlook recipients from Outlook mailboxes.
Which should you choose
Most teams starting out can use Google Workspace for the bulk of sending and add Microsoft 365 if much of the list is on Microsoft. Private SMTP makes sense only when someone can manage DNS, reverse DNS and IP reputation. Google requires valid forward and reverse DNS for sending domains or IPs, and on a private server that is your job. Check each provider's current terms before committing.
SPF, DKIM and DMARC: DNS records with examples
Authentication is the part you cannot skip. Every sending domain needs SPF, DKIM and DMARC records in place before the first warm-up email goes out. The examples below use a made-up domain, getacme-mail.com.
| Record | Host | Type | Example value |
|---|---|---|---|
| SPF | @ | TXT | v=spf1 include:_spf.google.com ~all |
| DKIM | google._domainkey | TXT | v=DKIM1; k=rsa; p=(public key from your admin console) |
| DMARC | _dmarc | TXT | v=DMARC1; p=none; rua=mailto:dmarc@getacme-mail.com |
| Tracking (Instantly example) | inst | CNAME | prox.itrackly.com |
The Google SPF value and the DKIM format come from Google Workspace's own setup pages. The tracking CNAME is the value Instantly documents for its custom tracking domain. The DMARC line is a standard starting policy, with reporting addresses you should point at a mailbox you actually read.
SPF
SPF lists which servers may send for your domain. Google's setup page gives the record v=spf1 include:_spf.google.com ~all and says to enter @ as the host for the root domain, with a separate record for each domain and subdomain. Keep one SPF record per domain. If you add a sending platform that needs its own include, merge it into the same record rather than publishing a second one.
SPF also has a hard limit of 10 DNS lookups. Past that, receiving servers stop evaluating and return a PermError, which means SPF fails (MxToolbox, 2026). Every include you stack adds lookups, so keep cold sending domains simple.
DKIM
DKIM signs each message so receivers can verify it was not altered. In Google Workspace, a super administrator generates the key in Admin console under Authenticate email. Google recommends a 2048-bit key if your DNS host supports it, with google as the default selector. The TXT record host looks like google._domainkey, and the value starts with v=DKIM1; k=rsa; p=.
Google says DNS changes can take up to 48 hours to work, and to click Start authentication only after the record exists. Verify by emailing a different Gmail address and reading the Authentication-Results header for a DKIM pass.
DMARC
DMARC tells receivers what to do when SPF and DKIM do not align with your From domain, and where to send reports. Google's sender guidelines say the policy for bulk senders can be set to none, and Yahoo requires at least p=none with DMARC passing, plus a strongly recommended rua reporting tag. Start at p=none and read the reports. The aim on a secondary domain is passing authentication, not blocking spoofing.
Google, Yahoo and Microsoft bulk sender requirements in 2026
Three mailbox providers set the rules most cold senders now live under. The table summarises what each says on its official page.
| Requirement | Google (Gmail) | Yahoo | Microsoft (Outlook.com, Hotmail, Live) |
|---|---|---|---|
| Who it applies to | Everyone sending to personal Gmail has basic rules. Bulk means close to 5,000 messages to personal Gmail in 24 hours, counted across a primary domain, and the status is permanent | Basic rules for all senders. The Sender Hub page does not define a bulk volume | Senders of 5,000 or more emails per day to Outlook consumer addresses |
| Authentication | SPF or DKIM for all senders. SPF, DKIM and DMARC for bulk senders, with the From domain aligned to SPF or DKIM | SPF or DKIM for all. SPF and DKIM plus DMARC (at least p=none) for bulk | SPF, DKIM and DMARC (at least p=none) with alignment |
| DKIM key | 1024 bits or longer, 2048 recommended | 1024 bits minimum | Not stated in the source I opened |
| Unsubscribe | One-click for marketing and subscribed mail, plus a visible link. Honor within 48 hours | One-click List-Unsubscribe header, visible link, honor within 2 days | Not stated in the source I opened |
| Spam complaints | Keep below 0.10%, never reach 0.30% | Below 0.3%, calculated on mail delivered to the inbox | Not stated in the source I opened |
| Consequence | Gradual enforcement, with temporary or permanent rejections increasing from November 2025 | Gradual rollout from February 2024 | Non-compliant mail rejected from May 5, 2025 |
Sources: Google's sender guidelines and FAQ, Yahoo's Sender Hub, and dmarcian's summary of Microsoft's announcement. Microsoft's own page would not load for me, so that column relies on dmarcian's reporting.
Do these rules apply to cold email
Google's FAQ never mentions cold email. Its rules apply to bulk senders and, for the basics, to every sender writing to personal Gmail accounts. Spreading volume across many domains can keep each under the 5,000 threshold, but it does not remove the basics: authentication, valid DNS, a spam rate below 0.3% and a properly formed message.
Warm-up, sending limits and mailbox rotation
Warm-up is the gradual build of sending history on a new mailbox. Sources agree on direction, not numbers.
What the platforms say
- Instantly's own settings page says the warm-up ramp starts at one email on day one and adds one per day up to the daily limit. Its recommended values for new accounts are an increase of 1 per day, a daily warm-up limit of 10, and a 30% reply rate. It says new accounts should be warmed gradually.
- Smartlead's platform data shows the average sender warms up for 8 days before the first campaign, and recommends keeping warm-up running on every mailbox while it sends.
- Instantly's benchmark article, citing SaleHandy, says two to four weeks minimum, ramping from 5 to 10 emails a day to 20 to 30 by week four, and quotes about 100 a day for a warmed inbox (citing MailReach). These are second-hand figures in a vendor article, so treat them as opinion.
- Smartlead reports warm-up inbox placement of about 99% and calls it "a health check, not a target." Warm-up measures warm-up traffic, not your cold campaigns.
An illustrative ramp schedule
This table is a conservative plan built inside the sourced ranges. It is not a rule from any provider.
| Week | Real cold sends per mailbox per day | Warm-up | Notes |
|---|---|---|---|
| 1 | 0 | On, ramping | Authentication verified, domain forwarding live |
| 2 | 5 to 10 | On | Smallest, best verified segment only |
| 3 | 10 to 20 | On | Check bounces and replies daily |
| 4 | 20 to 30 | On | Add mailboxes before adding volume per mailbox |
| 5 and later | 30 to 50 maximum | On | Stay at or below Smartlead's 50 ceiling |
Daily limits per mailbox
Smartlead's guidance is to keep each mailbox at 50 cold emails a day or fewer. Its platform data (more than 850 million emails, senders with at least 500 emails in the period) gives this distribution of cold sends per mailbox per day:
| Group | Cold emails per mailbox per day |
|---|---|
| Busiest 5% | 70 or more |
| Busiest 10% | 42 or more |
| Busiest 25% | 24 or more |
| Median | 14 |
| Quietest 25% | 8 or fewer |
| Quietest 10% | 4 or fewer |
The page does not compare reply or bounce rates by daily volume, so it shows what senders do, not what is safe.
Rotation
Rotation means a campaign sends from several mailboxes in turn, so each carries a small share. Set a daily limit per mailbox, assign several mailboxes to each campaign, and send in the morning (Smartlead reports reply rates peak between 6am and 10am in the recipient's time zone). Pause a mailbox that shows a bounce spike and rotate a spare in.
Tracking domains and open tracking trade-offs
Custom tracking domains
Sending platforms rewrite links and add tracking pixels. Without a custom tracking domain, those links use a domain shared with other customers. Instantly's help page says a custom tracking domain acts as a proxy so your reputation stays separate from other users. In Instantly it is a CNAME (host inst, pointing to prox.itrackly.com) that can take 24 to 72 hours to propagate. Instantly suggests one tracking domain across established domains, or one per sending domain for new domains or risky experiments.
Should you track opens at all
Open counts are weaker evidence than they look. Apple's Mail Privacy Protection, introduced in Q3 2021, preloads email content through a proxy, including tracking pixels, so senders see an open whether or not the person read the message (Postmark). Postmark adds that Gmail and Yahoo also cache images. Lemlist's benchmark article says open rates above 50% likely include machine opens, and that spam-filtered emails still count as delivered.
My recommendation, as a judgment rather than a statistic: turn open tracking off for new domains while you build reputation, and track replies and bounces instead. Fewer rewritten links and no pixel make a message look more like ordinary one-to-one mail. If you track opens, treat them as a rough deliverability signal, as lemlist suggests, never as interest.
List verification, bounces, complaints and legal basics
Verify before you send
Bad addresses are the fastest way to damage a new domain. Verify every list before upload, and re-verify older contacts. Clay describes a verification flow that returns one of five statuses (valid, invalid, catch-all, role-based, unknown), starts with ZeroBounce and checks "5+ services total" when the first cannot reach a confident verdict. Clay's own 2025 benchmark gave ZeroBounce 99.25% verdict quality on non-catch-all addresses. Catch-all accuracy is the harder problem, which Clay says it tested across 10 providers on 9,500 real campaign emails.
Practical handling:
- Send to valid addresses first.
- Segment catch-all and unknown addresses and send them at lower volume, or skip them.
- Suppress role-based addresses unless the role is exactly your target.
- Suppress anyone who replied, unsubscribed, bounced or complained, across every domain you own.
Bounce thresholds
Published thresholds vary. Smartlead's data puts the typical sender at a 1.54% bounce rate, calls 2% the danger line, and reports the worst quarter of senders at 3.21% or higher. Instantly's article says under 2% is normal and above 5% signals serious list problems. Lemlist's says under 3% is healthy and above 5% is the penalty zone. They disagree because they measure different senders.
A safe operating rule is to pause and investigate at 2% on any mailbox, and to treat 5% as an emergency.
Complaint thresholds
Google says to keep the user-reported spam rate below 0.10% and to prevent it from reaching 0.30%, and that bulk senders above 0.30% are not eligible for mitigation until they spend 7 consecutive days below it. Yahoo requires below 0.3%. For cold senders, aim for the stricter 0.10% number. At 1,000 delivered emails, one complaint is already 0.10%, which is why small campaigns need care.
Legal basics
None of this is legal advice. Authentication keeps you deliverable. The law decides whether you should send at all.
- US (CAN-SPAM): the FTC lists eight requirements, including accurate headers, non-deceptive subject lines, ad identification, a valid physical address and opt-out instructions. Opt-outs must be honored within 10 business days, each violating email can carry penalties up to $53,088, and the law makes no exception for business-to-business email.
- UK (PECR and UK GDPR): the ICO says PECR's consent rule does not apply to corporate subscribers such as companies and LLPs, but you must identify yourself and give a valid opt-out address. Sole traders and some partnerships are treated as individuals and need consent or a qualifying soft opt-in. A named work email address is personal data under UK GDPR, so you also need a lawful basis.
What leading agencies and operators are doing in 2026
Public sources show a few shared practices. These are vendor claims, not audited industry facts.
- Many mailboxes, low volume each. Smartlead's 2026 data says a typical account runs 20 mailboxes, agency setups "run into the hundreds," and the typical mailbox sends about 13.9 cold emails per day. Its guidance is to add mailboxes rather than push each harder.
- Authentication as table stakes. Smartlead reports 108 contacts per reply for senders with SPF, DKIM and DMARC verified versus 120 for unverified, a modest platform-wide gap.
- Waterfall verification before send. Clay describes sequencing multiple verifiers, flagging catch-all addresses for suppression and pushing clean rows to sending tools such as Smartlead or Instantly, with recurring re-verification of older contacts. This is the practice usually grouped under GTM engineering. For what that role covers, see what a GTM engineer does.
- Know which reply rate you are quoting. Instantly's 2026 report is cited at a 3.43% average reply rate, while Smartlead's data shows a typical reply rate of 0.74%. Lemlist's roundup shows up to a 7.6x spread across sources and attributes it to counting rules, such as whether auto-replies count. Compare your own numbers to a benchmark only when the definition matches.
To decide whether to build this in house, see the outbound agency vs in-house SDR comparison and the cold email agency guide.
Monitoring and the launch-day checklist
Postmaster Tools and inbox placement
Google Postmaster Tools is the only first-party window into how Gmail sees your domain. Its dashboards cover compliance status, spam rate, IP and domain reputation (rated Bad, Low, Medium or High), authentication, encryption and delivery errors. Data uses UTC, updates within 24 hours, covers verified domains only, and low-volume days may show no data. The spam rate counts only DKIM-authenticated messages that reached the inbox and were marked as spam. Google notes that messages filtered automatically are not counted, so a low rate can mean most mail is going to spam.
That blind spot is why you also need inbox placement testing. Delivery reports say a message was accepted, not where it landed. Send periodic test messages from each sending domain to seed mailboxes you control at Gmail, Outlook and any other provider on your list, and check for inbox, promotions or spam. Many sending platforms offer a built-in placement test. Run it weekly and before any volume increase.
Review bounces per mailbox, replies, Postmaster spam rate and reputation, and placement results daily in week one and weekly after.
Launch-day checklist
| Step | Check | Pass condition |
|---|---|---|
| 1 | Secondary domains purchased and forwarded to the main site | Domain opens a credible page |
| 3 | SPF published, one record per domain | Record found, under 10 lookups |
| 4 | DKIM published and authentication started | DKIM pass in message headers |
| 5 | DMARC published with an rua mailbox | Record found, reports arriving |
| 6 | Custom tracking domain verified, or tracking off | CNAME resolves, or open and click tracking disabled |
| 7 | Warm-up running on every mailbox | At least the platform's minimum ramp completed |
| 8 | List verified, catch-all and unknown segmented | Bounce estimate under 2% |
| 9 | Suppression list loaded, including past replies and unsubscribes | No duplicates across domains |
| 10 | Unsubscribe line, sender identity and physical address in the template | Legal basics met for your regions |
| 11 | Daily limits and rotation set per mailbox | At or below planned ramp week |
| 12 | Test sends to Gmail and Outlook seeds | Inbox, not spam |
| 13 | Postmaster Tools verified and pause rules written down | 2% bounce, any complaint spike, placement drop |
Common mistakes
- Sending cold email from the main company domain. One bad campaign can then affect everyday business email.
- Running every mailbox at its provider cap. Google's 2,000 and Microsoft's 10,000 are ceilings, not targets.
- Skipping DMARC because the volume is small. It is a few minutes of DNS work.
- Stacking SPF includes. More than 10 lookups causes a PermError.
- Treating warm-up placement as proof of cold email placement. Warm-up traffic is not your campaign.
- Not verifying the list. Bounces climb fast, and 2% is the danger line in Smartlead's data.
- Having no pause rule. Decide the limits before launch, not after the damage.
- Keeping one suppression list per domain. Someone who unsubscribed on one domain should not get mail from another.
Takeaways
- Use secondary domains, about three mailboxes each as a planning assumption, and size by dividing daily volume by a realistic per-mailbox number, not by the provider cap.
- Keep each mailbox at or below 50 cold emails per day (Smartlead's ceiling) and scale by adding mailboxes.
- Publish SPF, DKIM and DMARC on every domain, verify DKIM passes in a real message header, and watch the 10-lookup SPF limit.
- Follow Google, Yahoo and Microsoft rules even below the 5,000 per day threshold: authentication, a working unsubscribe path, and complaints under 0.10% in practice.
- Verify lists, pause at a 2% bounce rate, and test inbox placement on top of Postmaster Tools.
- Treat open rates as a rough signal and judge the program on replies and meetings.
If you would rather have this built and run for you, see Cruxfinder's GTM agency, the account-based outbound service, the B2B lead generation agency, or hire a GTM engineer. To size the numbers yourself, start with the free GTM tools, and to model returns see how to calculate cold email ROI. The full set of guides lives in the GTM hub.
Sources
- Email sender guidelines, Google, 2026
- Email sender guidelines FAQ, Google, 2026
- Gmail sending limits in Google Workspace, Google, 2026
- Set up SPF, Google, 2026
- Set up DKIM, Google, 2026
- Postmaster Tools dashboards, Google, 2026
- Yahoo Sender Hub best practices, Yahoo, 2026
- Microsoft enforces SPF, DKIM and DMARC for high-volume Outlook senders, dmarcian, 2026
- Outbound spam sending limits (Exchange Online), Microsoft, 2026
- SPF lookup limit, MxToolbox, 2026
- Warmup settings explained, Instantly, 2026
- Custom tracking domain, Instantly, 2026
- Email sequence benchmarks 2026, Instantly, 2026
- Sends per mailbox benchmark, Smartlead, 2026
- The State of Cold Email 2026, Smartlead, 2026
- Cold email benchmarks 2026, lemlist, 2026
- How to re-verify stale emails, Clay, 2026
- How Apple's Mail privacy changes affect open tracking, Postmark, 2026
- CAN-SPAM Act: a compliance guide for business, US Federal Trade Commission, 2026
- Business-to-business marketing, UK Information Commissioner's Office, 2026
- Direct marketing using electronic mail, UK Information Commissioner's Office, 2026
Frequently asked questions
How many domains and mailboxes do I need for cold email?+
Divide your planned emails per day by a realistic per-mailbox number, then divide mailboxes by three per domain as a planning assumption. At about 286 sends a day and 30 per mailbox, you need roughly 10 mailboxes across 4 domains. Smartlead advises keeping each mailbox at 50 cold emails a day or fewer, so add mailboxes rather than volume.
How long should I warm up a new cold email mailbox?+
Plan for at least one to two weeks of warm-up before real sends, and ramp slowly after. Smartlead reports an 8 day average before the first campaign, while an Instantly article citing SaleHandy says two to four weeks minimum. Instantly's default ramp adds one warm-up email per day. Keep warm-up running while you send.
Do I need DMARC for cold email?+
Yes, publish it on every sending domain. Google, Yahoo and Microsoft require DMARC for bulk senders, with a policy of at least none and alignment with SPF or DKIM. Cold senders often sit below the 5,000 per day threshold, but the record takes minutes to add and its reports show who is sending as your domain.
What is a safe bounce rate for cold email?+
Keep bounces under 2%. Smartlead's platform data shows a typical bounce rate of 1.54% and calls 2% the danger line, with the worst quarter of senders at 3.21% or higher. Pause the affected mailbox at 2%, re-verify the list, and treat anything near 5% as an emergency.
Is Google Workspace or Microsoft 365 better for cold email?+
Neither wins outright. Google Workspace allows 2,000 messages per user per day, and Microsoft says Exchange Online is not designed for bulk mailing, with a 10,000 recipient daily limit. Both caps are far above sane cold volume. Many teams use both and match the mailbox provider to the recipient's provider, which lemlist recommends.
Should I turn off open tracking for cold email?+
Often yes, at least for new domains. Apple Mail Privacy Protection preloads tracking pixels through a proxy, so opens register even when nobody reads the message, and Gmail and Yahoo also cache images (Postmark). Track replies, bounces and unsubscribes instead, and use a custom tracking domain if you keep link tracking.
Do Google's 5,000 emails per day rules apply to cold email?+
Google's FAQ does not mention cold email. Bulk status means close to 5,000 messages to personal Gmail in 24 hours from one primary domain, and it is permanent once reached. Even below that, the basic rules apply: SPF or DKIM, valid DNS, TLS and a spam rate under 0.3%, ideally under 0.10%.
Want help with this?
Book a free 30 minute call and we will map your quickest wins across cold outbound and paid media.
Related