Outbound · Deep dive

Cold email infrastructure: domains, authentication and deliverability

Since 2024, Gmail, Yahoo and Outlook enforce strict rules for bulk senders. Here's how we set up and run outbound email infrastructure that stays out of the spam folder.

By Max Chuchmai3 min read

On this page
  1. The rules, in plain language
  2. Protect your main domain
  3. Authentication, done properly
  4. Warm-up and volume
  5. List quality is deliverability
  6. Write like a person
  7. Monitor and react automatically
  8. The bottom line

Outbound email has changed more in the last three years than in the decade before. In February 2024, Google and Yahoo began enforcing new requirements for bulk senders, and Microsoft followed with similar rules for Outlook.com in 2025. Senders who ignore them don’t get a warning. Their mail just stops arriving.

This guide covers how we build outbound email infrastructure that works within those rules. It’s written for leaders who want to understand what their team or vendor should be doing.

The rules, in plain language

The requirements for anyone sending in volume to Gmail, Yahoo and Outlook.com mailboxes come down to four things:

  1. Authenticate your mail. Set up SPF and DKIM for every sending domain, and publish a DMARC policy. The visible “From” domain must align with the authenticated domain.
  2. Make unsubscribing easy. Marketing and promotional mail must support one-click unsubscribe, and requests must be honoured quickly.
  3. Keep complaints low. Google asks senders to keep the spam-complaint rate reported in Postmaster Tools below 0.1%, and to never reach 0.3%.
  4. Send valid, well-formed mail. Valid reverse DNS, proper TLS, and messages that follow the email standards.

These rules formally apply to the largest senders, but the filters behind them apply to everyone. Treat them as the baseline.

Protect your main domain

Your company domain carries your invoices, your support replies and your CEO’s email. Never risk it on cold outreach.

Instead, register a small number of secondary domains that are clearly yours (for example a variation of your brand name), and point their websites to your main site. Each sending domain gets a few inboxes, each with a real person’s name and a matching signature. If one domain runs into trouble, the damage stays contained.

Authentication, done properly

For every sending domain:

  • SPF lists the services allowed to send for the domain. Keep it short; SPF has a limit of ten DNS lookups, and long records quietly fail.
  • DKIM signs every message with a key published in DNS. Use 2048-bit keys where your provider supports them.
  • DMARC tells receivers what to do when checks fail, and sends you reports. Start with p=none to collect data, then move to quarantine once you’re confident everything legitimate passes.
  • A custom tracking domain, if you track clicks at all, so links don’t share a reputation with other senders on the same tool.

We check all of this with automated tests whenever DNS changes, not just once at setup.

Warm-up and volume

A brand-new inbox that suddenly sends hundreds of emails looks exactly like a spammer. Reputation has to be built.

  • Warm up new inboxes for several weeks before any cold sends, gradually increasing daily volume.
  • Keep volume per inbox modest. We keep cold sends per inbox well below what the provider technically allows, and scale by adding inboxes and domains rather than pushing each one harder.
  • Spread sends through the working day in the recipient’s time zone, rather than in bursts.

List quality is deliverability

Most deliverability problems start with the list, not the infrastructure.

  • Verify every address before it reaches a sequencer. Hard bounces are one of the strongest negative signals a mailbox provider sees. Our waterfall enrichment guide covers verification in more detail.
  • Remove role addresses like info@ and sales@ from cold campaigns.
  • Suppress across tools. Anyone who unsubscribes, complains or becomes a customer must be suppressed in every sending tool, not just the one where they opted out.

Write like a person

Filters, and buyers, respond to the same things. Short, plain-text messages with one clear question perform better than designed templates with images and multiple links. Personalisation should be specific and relevant, ideally tied to a real signal, not a merge field that says you noticed their company name.

Monitor and react automatically

Deliverability isn’t a setup task. It needs monitoring:

  • Bounce rate per inbox and campaign, with an automatic pause above a set threshold.
  • Spam-complaint rate from Google Postmaster Tools and Microsoft’s sender programs.
  • Inbox placement tests that show whether mail lands in the inbox, promotions or spam at each major provider.
  • Blocklist monitoring for every sending domain and IP.

When something crosses a threshold, the system should pause the affected inbox and alert a person, before the problem spreads to the rest of the domain.

The bottom line

Good outbound infrastructure is invisible when it works. Your messages arrive, your main domain is safe, and problems are caught in hours, not weeks. It takes careful setup and steady maintenance, and it’s the foundation every outbound strategy depends on.


We set up and run outbound infrastructure for B2B sales teams. See our outbound infrastructure service.

Written by

Max Chuchmai

Founder & Managing Partner, CoderStein. System architecture, AI automation, and GTM engineering.

Follow on LinkedIn

Want this running in your GTM stack?

Book a GTM systems review. We map your funnel, data and tools, and show you where the biggest gains are.

Book a GTM review