Cold Email Infrastructure: The Complete Setup Guide for B2B Outbound

You can write the best cold email in the world. If your infrastructure is wrong, nobody will ever see it. Cold email deliverability is a technical problem first and a copywriting problem second. This guide covers every step of setting up the infrastructure that gets your emails into primary inboxes, not spam folders.

This is what we build for every client at Visbl. It's not glamorous work, but it's the foundation that makes everything else possible. Skip any of these steps and your outbound campaigns will underperform no matter how good your copy or targeting is.

Step 1: Buy dedicated sending domains

Never send cold email from your primary business domain. If your company is acme.com, do not send outbound campaigns from john@acme.com. If your sending domain gets flagged (and at scale, it eventually will), you want that flag on a secondary domain, not on the domain your entire company uses for client communication.

How many domains do you need?

Plan for 2-3 mailboxes per domain and 30-40 emails per mailbox per day. Work backward from your desired sending volume:

• 500 emails/day: 4-5 domains, 2-3 mailboxes each (12-15 mailboxes total)
• 1,000 emails/day: 8-10 domains, 2-3 mailboxes each (25-30 mailboxes total)
• 2,000+ emails/day: 15-20 domains, 2-3 mailboxes each (50+ mailboxes total)

These numbers might seem excessive if you're used to thinking about email as a single inbox. But spreading volume across many mailboxes is how you maintain sender reputation at scale. Sending 500 emails from one inbox is a red flag. Sending 35 emails each from 15 inboxes looks like normal business communication.

Choosing domain names

Your secondary domains should be recognizably related to your primary domain. If your company is Acme Corp (acme.com), good secondary domains include:

• acmecorp.com
• acme-team.com
• getacme.com
• tryacme.com
• acmehq.com

Avoid domains that look spammy or are completely unrelated to your brand. The recipient should be able to look at the sender address and connect it to your company. Buy domains from a reputable registrar like Google Domains, Namecheap, or Cloudflare.

Redirect secondary domains to your main site

Set up a 301 redirect from each secondary domain to your primary website. If someone types getacme.com into their browser, it should take them to acme.com. This does two things: it makes the domain look legitimate (it's not a dead page), and it ensures anyone who looks you up from your email lands on your real website.

Step 2: Set up DNS authentication records

DNS records tell email providers that you are who you say you are. Without proper DNS authentication, your emails will either go to spam or get rejected entirely. There are three records you need to configure for every sending domain.

SPF (Sender Policy Framework)

SPF tells receiving mail servers which servers are authorized to send email on behalf of your domain. It's a TXT record in your DNS that lists the IP addresses and services allowed to send as your domain.

If you're using Google Workspace, your SPF record will include Google's servers. If you're using a sending tool like Smartlead or Instantly, you'll need to add their servers too. The key rule: only include servers that actually need to send as your domain. Every extra entry increases the chance of abuse.

Common mistake: having multiple SPF records for the same domain. You can only have one SPF record per domain. If you need to authorize multiple services, combine them into a single record using the include: mechanism.

DKIM (DomainKeys Identified Mail)

DKIM adds a digital signature to your outgoing emails. The receiving server checks this signature against a public key published in your DNS to verify the email wasn't modified in transit and actually came from your domain.

Most email providers (Google Workspace, Microsoft 365) generate DKIM keys for you during setup. You just need to add the CNAME or TXT records they provide to your DNS. Enable DKIM for every sending domain — there's no reason not to.

DMARC (Domain-based Message Authentication, Reporting, and Conformance)

DMARC ties SPF and DKIM together and tells receiving servers what to do if an email fails authentication. For cold email, start with a DMARC policy of "none" (monitoring mode) so you can see how your emails are being authenticated without rejecting anything.

A basic DMARC record looks like: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

The rua tag sends you aggregate reports about authentication results. Review these reports for the first 2-4 weeks to make sure everything is passing before tightening your policy. Once you're confident your SPF and DKIM are configured correctly, you can move to p=quarantine or p=reject for stronger protection.

Custom tracking domain

If you're using a cold email platform that tracks opens or clicks, set up a custom tracking domain. Default tracking domains are shared across thousands of users, and if any of them get flagged for spam, your deliverability suffers too. A custom tracking domain isolates your tracking reputation.

Step 3: Create and configure mailboxes

Google Workspace is the standard for cold email sending. Microsoft 365 works too but tends to have stricter sending limits and more aggressive internal spam filtering. For each domain, create 2-3 mailboxes with real-sounding names:

• firstname@domain.com (preferred)
• firstname.lastname@domain.com
• first initial + lastname@domain.com

Each mailbox should have:

• A professional display name (real person's name)
• A profile photo (real photo, not a stock image)
• An email signature with name, title, company, and phone number

These details matter because email providers evaluate sender legitimacy partly based on profile completeness. A fully configured mailbox looks like a real person. An empty profile with no photo sending hundreds of emails looks like a bot.

Step 4: Warm your inboxes

New mailboxes have no sender reputation. If you start sending 40 cold emails a day from a brand new inbox, you'll land in spam immediately. Email warming solves this by gradually building your sender reputation before you start outbound campaigns.

How warming works

Warming tools (Instantly, Warmbox, Smartlead's built-in warmer) automatically send and receive emails between your inbox and a network of other real inboxes. These emails get opened, replied to, and marked as important — all the positive engagement signals that tell Google and Microsoft your inbox is legitimate.

Warming timeline

• Week 1-2: Start at 5-10 warming emails per day. Let the inbox establish a baseline of normal activity.
• Week 2-3: Ramp up to 20-30 warming emails per day. Monitor deliverability scores.
• Week 3-4: Reach your target warming volume (30-40 per day). Begin sending a small volume of real cold emails (5-10/day).
• Week 4+: Gradually increase cold email volume while maintaining warming. Your warming volume should always be at least 50% of your total sending volume.

Never stop warming

Warming isn't a one-time setup. Keep it running permanently. The positive engagement signals from warming offset the negative signals that cold email naturally generates (low open rates on some emails, occasional spam complaints). Think of it as ongoing reputation maintenance.

Step 5: Set up inbox rotation

Inbox rotation distributes your sending volume across all your mailboxes automatically. Instead of sending 500 emails from one inbox, you send 35 emails each from 15 inboxes. This keeps each individual inbox well below the volume thresholds that trigger spam filters.

Most modern cold email platforms (Smartlead, Instantly, Salesforge) support inbox rotation natively. Connect all your warmed mailboxes, set your daily sending limits per inbox, and the platform distributes automatically.

Key settings for inbox rotation:

• Max emails per inbox per day: 30-40 for Google Workspace, 20-30 for Microsoft 365
• Time between emails: 3-8 minutes minimum. Don't send in rapid bursts.
• Sending window: Send during business hours in the recipient's timezone. Emails sent at 3am look automated.
• Daily randomization: Vary the exact sending times and volumes slightly each day. Perfectly consistent patterns look robotic.

Step 6: Monitor deliverability continuously

Your infrastructure isn't "set it and forget it." Deliverability fluctuates based on your sending behavior, recipient engagement, email content, and factors outside your control (like changes to Gmail's spam algorithms). You need ongoing monitoring.

What to monitor

• Inbox placement rate: What percentage of your emails land in the primary inbox vs. spam? Use tools like GlockApps or MailReach to test. Target 85%+ inbox placement.
• Open rates by mailbox: If one mailbox has significantly lower open rates than others, it may be getting flagged. Pause it, increase warming, or replace it.
• Bounce rates: Keep hard bounces under 3%. Higher bounce rates signal bad list quality and hurt sender reputation. Verify your email lists before sending.
• Spam complaint rate: Google penalizes senders with complaint rates above 0.3%. If you're getting complaints, your targeting or copy needs work.
• Blacklist checks: Run periodic checks to see if your sending IPs or domains are listed on email blacklists (MXToolbox, MultiRBL). Getting blacklisted tanks deliverability immediately.

When things go wrong

If your deliverability drops suddenly, the most common causes are:

• Sending volume spike: You increased volume too fast. Scale back and ramp up gradually.
• Bad list data: High bounce rates from unverified emails. Always verify before sending.
• Content triggers: Certain words, links, or formatting are triggering spam filters. Test your email content through a deliverability checker.
• Warming stopped: If warming was paused or the warming tool had issues, your reputation decays quickly.
• Domain age: Domains under 30 days old have minimal reputation. Be patient during the initial warming period.

Step 7: Maintain and scale

Once your infrastructure is running, maintenance is about consistency. Here's the weekly checklist:

• Review deliverability scores across all mailboxes
• Rotate out any underperforming mailboxes
• Check DMARC reports for authentication failures
• Verify that warming is running consistently
• Clean your prospect lists (remove bounces, unsubscribes, and unresponsive contacts)
• Test inbox placement for your current email copy

To scale volume, add new domains and mailboxes following the same process: buy domain, configure DNS, create mailboxes, warm for 3-4 weeks, then start sending. Don't try to increase volume from existing mailboxes beyond 40/day. Add capacity horizontally.

Why most teams get this wrong

Infrastructure is the unsexy part of cold email. Most sales teams want to jump straight to writing emails and hitting send. But sending cold email without proper infrastructure is like building a house without a foundation. It might look fine for a week, then everything collapses.

The teams that struggle most are the ones that:

• Send from their primary domain and torch their company's email reputation
• Skip DNS authentication and wonder why emails go to spam
• Don't warm inboxes and get flagged within the first week
• Send too many emails from too few inboxes
• Never monitor deliverability and don't realize they're in spam until months later

At Visbl, infrastructure setup is the first thing we do for every client. Before we write a single email sequence, before we build a single list, we make sure the technical foundation is right. We manage the domains, DNS records, mailbox creation, warming, rotation, and ongoing monitoring. Our clients never have to think about SPF records or inbox placement — they just get meetings.

If you want to handle this yourself, this guide gives you everything you need. If you'd rather have someone who does this every day handle it for you, that's what our deliverability team is here for.