Cold Email Infrastructure: How to Build a Sending Setup That Won't Get Burned

Why Cold Email Demands Separate Infrastructure

Cold email is fundamentally different from every other type of email you send. You're reaching people who haven't opted in to hear from you. Some will respond positively. Others will ignore you. A meaningful fraction will mark the message as spam — that's unavoidable when you're contacting people without prior relationship, regardless of how targeted or relevant your message is.

That variance in recipient response makes cold email inherently riskier for sender reputation than opt-in email. Spam complaints from cold outreach, even at relatively low rates, can damage the sending domain and IP they came from. If you're running cold campaigns from the same infrastructure you use for transactional emails or your corporate inbox, a reputation event from one campaign affects everything else. An order confirmation that lands in spam because your cold email domain got flagged is a real operational problem.

The answer is dedicated infrastructure for cold outreach: separate domains, separate IPs, and separate SMTP routing that keeps cold email reputation isolated from your primary sending.

Choosing Your Sending Domains

Never send cold email from your primary business domain. Register dedicated domains specifically for cold outreach — commonly called outreach domains or sending domains.

Practical guidelines for selecting and setting up outreach domains:

• Keep them believable: Domains like yourbrand-team.com, helloyourbrand.com, or yourbrand-hq.com are commonly used. They should be recognisably related to your company without being your primary domain.
• Register multiple: Don't concentrate all your volume on a single outreach domain. Two or three domains spread the risk — if one gets flagged or filtered, the others continue operating.
• Age them before using them: Newly registered domains are treated with elevated suspicion by inbox providers. Register outreach domains at least 30 days before your first send, and don't start at full volume. New domains should warm up gradually.
• Add a real website: Even a minimal one-page site with your company name, a contact address, and a brief description adds domain credibility. A domain with zero web presence that sends email is a red flag for spam filters.

Authentication Is Not Optional

Proper email authentication on your sending domains is a prerequisite for reaching any modern inbox. Without it, messages will be filtered or rejected before any human decision enters the picture.

Every cold email sending domain needs:

• SPF: Authorise your cold email SMTP relay and nothing else. Keep the record minimal and accurate.
• DKIM: Generate 2048-bit keys. Sign every message. The signing domain must align with the sending domain.
• DMARC: Start with p=none and reporting enabled to confirm alignment. Move to p=quarantine once you've verified SPF and DKIM are passing consistently.

The DMARC setup guide and the SPF guide cover the implementation details for each record type.

Dedicated IPs for Cold Sending

Sending cold email from a shared IP pool means your reputation is partly determined by other senders on the same pool — including whatever they're doing today. For cold email specifically, where complaint rates tend to run higher than opt-in email by nature, the stability of a dedicated IP is worth the cost.

The tradeoff is that a new dedicated IP starts with no reputation and must be warmed before it can support higher volumes. During warm-up, keep sends low and use only your most targeted, highest-quality prospect lists — the early days of an IP's reputation are when complaint signals are disproportionately damaging. Plan two to four weeks of deliberate warm-up before running any high-volume campaign.

Volume and Sending Patterns

Cold email volume limits exist for two reasons: IP warming requirements and inbox provider rate-limit thresholds. Sending too much too fast signals automation at scale, which triggers aggressive filtering regardless of your content quality.

Common starting limits for a newly warmed cold email setup:

• Maximum 200 messages per sending inbox per day
• Maximum 400–500 messages per outreach domain per day across all associated inboxes
• Random intervals between sends rather than precise machine-like spacing — sending 50 messages in a burst at 9:00 AM looks nothing like a human working through a prospect list

Adding natural variation to your send times and spacing reduces the automation fingerprint. Most dedicated cold email tools offer this by default; if you're sending through a standard SMTP relay, you'll need to build the timing logic into your sending process.

List Quality Determines Everything Else

Technical infrastructure can protect a good list. It cannot save a bad one. The quality of your prospect data determines your complaint rate more than any configuration choice, and high complaint rates will burn through infrastructure regardless of how well it's built.

Before any cold send:

• Validate every address with an email verification service — remove addresses that fail existence checks.
• Remove all role addresses (info@, admin@, support@, contact@) — these route to shared inboxes where complaints are more likely.
• Remove duplicate contacts at the same company — sending to five people at the same organisation in the same campaign looks like spam.
• Apply your suppression list before every send — anyone who previously responded negatively or unsubscribed should not appear in a new campaign.

Handling Replies and Opt-Outs

Cold email requires a managed reply process. Every reply — positive, negative, or "take me off your list" — needs to be read and acted on. A request to stop receiving email must result in the address being suppressed immediately. Ignoring opt-out requests from cold email recipients creates both legal exposure and ongoing deliverability damage.

Configure all sending accounts to forward replies to a monitored inbox. Process opt-outs the day they arrive. Most dedicated cold outreach tools automate suppression from negative replies; if you're building a custom setup on a general-purpose SMTP relay, build this step explicitly into your workflow — it's not optional infrastructure.

Cold email done right is a legitimate and effective channel for B2B outreach. But it requires infrastructure built for the purpose, not repurposed from your primary sending setup. Getting the separation, authentication, and volume management right from the start is far easier than trying to repair a burned domain or IP afterward.