Blog
How to Improve Email Deliverability: 9 Fixes (2026)

How to Improve Email Deliverability: 9 Fixes (2026)

Last Updated on: Oct 21, 2026
•
5 min read
Summarize with

Most advice on improving email deliverability starts with subject lines and spam words. In my experience, that's the last place the problem usually is.

When I audit a cold email setup that's landing in spam, the cause is almost always further down the stack: the wrong kind of mailbox, too few domains, a missing DMARC record, or a mailbox sending 150 emails a day in its second week.

So this guide works from the mailbox up. It covers 9 fixes in the order I'd apply them, starting with the ones that make the biggest difference.

TL;DR

  • Fix the foundation first: send from real Google Workspace and Microsoft 365 mailboxes on secondary domains, never your main domain, and never EDU or loophole mailboxes.
  • Match the provider: Google mailboxes to Google recipients and Microsoft to Microsoft (ESP matching), and run at least two providers.
  • Authenticate every domain with SPF, DKIM and DMARC, plus a custom tracking domain and domain forwarding.
  • Warm up for about two weeks and keep warmup running. Aim for a Heat Score™ of 85 or above before scaling.
  • Cap volume per mailbox (I keep cold sends to roughly 20 to 30 a day), verify every list, write plain one-to-one emails, and monitor placement weekly.
  • Primeforge handles the foundation: real Google Workspace and Microsoft 365 mailboxes with automated DNS and ESP matching, live in about 30 minutes.

Why Cold Email Deliverability Breaks in 2026

The inbox providers raised the bar, and cold email has less room for error than any other kind of email.

Since February 2024, Google and Yahoo have required bulk senders to authenticate with SPF, DKIM and DMARC, support easy unsubscribes and keep spam complaints below 0.3%. Google's bulk sender guidelines break down what applies to outreach. Microsoft followed on May 5, 2025, routing mail from non-compliant domains that send over 5,000 emails a day to Junk.

Newsletters have one advantage cold email doesn't: subscribers asked for them. A cold email arrives with no history, so the provider judges it almost entirely on the sender. That's why the fixes below start with the sender, not the copy.

Send From Real Google and Microsoft Mailboxes

The mailbox you send from carries more weight than anything you write in it.

Most B2B prospects receive email on Google Workspace or Microsoft 365. Mail sent from those same providers looks normal to their filters, because it travels the way legitimate business mail travels. Mail from cheap SMTP servers or unknown hosts has to earn trust from scratch.

The shortcut I'd avoid is the "cheap Google mailbox" market: education accounts, repurposed tenants and resold seats that break when the provider tightens its policies. When they break, every mailbox on the tenant goes down at once. These EDU mailbox risks are worth reading before you buy anything that sounds too cheap.

Buy properly licensed Google Workspace and Microsoft 365 mailboxes, configured for outreach. That single decision removes a whole category of deliverability problems before you send anything.

Use Secondary Domains, Never Your Main One

Your primary domain carries your website, your invoices and your team's daily email, so keep cold outreach off it.

If a cold campaign goes wrong on your main domain, the damage spreads to everything else that domain sends. I always run outreach from secondary domains that look like the brand (for example, a "get" or "try" variation of the company name) and redirect them to the main website.

Subdomains are a common middle ground, but they still share reputation signals with the root domain. This comparison of domain vs subdomain for cold email explains when each makes sense.

Why Your Main Domain Is Dying (Stop Doing This)

Get the Number of Domains and Mailboxes Right

Deliverability problems often come from asking too few mailboxes to send too many emails.

Work backward from your volume. Multiply the contacts you want to reach each month by the number of emails in your sequence, then divide by what one mailbox can safely send. Two or three mailboxes per domain keeps any single domain's footprint small.

For example, reaching 3,000 contacts a month with a 3-step sequence means 9,000 emails. Primeforge's Mailbox Calculator turns that into 8 domains and 15 mailboxes at 2 mailboxes per domain, which works out to roughly 600 emails per mailbox per month.
Primeforge Mailbox Calculator showing 8 required domains and 15 required mailboxes for 3,000 contacts a month
If you'd like the full math, this guide on how many domains you need for cold email walks through it at different volumes.

Match Your Sending Provider to Your Prospect's

Google-to-Google and Microsoft-to-Microsoft delivery is the closest thing to a free deliverability gain I know.

ESP matching means sending from a Google mailbox when the prospect uses Google, and from a Microsoft mailbox when they use Microsoft. Each provider tends to trust mail from its own ecosystem, and you avoid the cross-provider filtering that pushes cold mail into spam or promotions.

This explainer on how ESP matching improves deliverability covers how the matching is done.
Diagram of ESP matching: Google mailboxes sending to Google recipients and Microsoft mailboxes sending to Microsoft recipients
To match, you need both providers in your setup. I recommend running at least two, so there's always a mailbox on the same provider as the prospect, and so one provider's policy change doesn't stop your outreach. Here's more on why to diversify your cold email infrastructure.
Primeforge create new domains screen with a choice between Google and Microsoft as the platform

You NEED at least 2 Different Email Service Providers, here's why (Salesforge)

Get real Google and Microsoft mailboxes for cold outreach

Primeforge sets up Google Workspace and Microsoft 365 mailboxes with SPF, DKIM and DMARC done for you, ready to send in about 30 minutes.

Authenticate Every Domain Properly

Authentication proves your mail is really from you, and it's now a requirement rather than a best practice.

  • SPF lists the servers allowed to send for your domain. Keep it to one record per domain and within the 10-lookup limit.
  • DKIM signs each email so the receiver can check it wasn't altered. Use a 2048-bit key where your provider supports it.
  • DMARC tells receivers what to do when SPF or DKIM fails, and it needs alignment with your From domain. I start at p=none to collect reports, then move to quarantine once everything passes.
This SPF, DKIM and DMARC setup guide for Google Workspace covers the exact records.

Two more pieces complete the setup. A custom tracking domain stops your links from sharing a tracking domain with thousands of other senders. And domain forwarding redirects each secondary domain to your main website, so a prospect who checks the domain finds a real business.

Warm Up Before You Send Cold Email

A new mailbox has no history, and warmup is how it earns one before the first cold email goes out.

Warmup sends and receives realistic conversations from your new mailbox, gradually increasing volume, so providers see normal engagement. I give every new mailbox about two weeks before cold sends, and I keep warmup running afterwards rather than switching it off. This email warm-up checklist for new domains lays out the ramp.

I use Warmforge for this. Its Heat Score™ gives each mailbox a reputation score, and I wait for 85 or above before scaling. If you can't wait two weeks, pre-warmed Google mailboxes let you start sending sooner.
Warmforge mailbox warmup view with a Heat Score™ of 98 and a chart of warmup emails that reached the inbox

Stay Inside Safe Sending Limits

Volume is where good setups break, because a warm mailbox can still be overloaded.

I keep each mailbox to roughly 20 to 30 cold emails a day, ramp new mailboxes gradually, and spread volume across mailboxes and domains instead of pushing one harder. Microsoft in particular reacts quickly to sudden spikes, so these Microsoft 365 throttling best practices are worth following if you send from Outlook mailboxes.

This piece on how sending limits affect cold email deliverability goes deeper. When you need more volume, add mailboxes and domains, then rotate across them; here's how domain rotation keeps any single domain's reputation intact.

Keep Your List Clean

Bounces are a direct reputation hit, so verifying your list is one of the cheapest fixes on this page.

Verify every list before it's sent, remove role and catch-all addresses you can't confirm, and stop any campaign where hard bounces rise above 2%. Knowing the difference between hard and soft bounces tells you which addresses to remove and which to retry.

Data quality starts upstream. Leadsforge uses waterfall enrichment across multiple data providers, so fewer addresses are wrong in the first place, and Salesforge's Bounce Shield blocks sends to addresses likely to bounce.

Write Emails That Look Like One-to-One Mail

Once the infrastructure is right, copy decides whether you land in primary or promotions.

  • Send plain text. No images, no HTML templates, no tracking pixels if you can avoid them.
  • Use one link at most, and none in the first email if possible.
  • Keep it short and specific, with one clear reason for writing and one ask.
  • Avoid hype phrases such as "guaranteed", "act now" or "100% free".
  • Keep the signature light. A heavy signature with logos and social icons reads like marketing mail. This guide on email signatures and deliverability shows what to keep.
  • Include a simple opt-out line, and honor it.
If your emails reach Gmail but sit in the wrong tab, these steps to avoid the Gmail Promotions tab usually fix it.
Nine email deliverability fixes stacked from mailboxes at the foundation up to plain copy at the top

Mailbox Options Compared

Here's how the common ways to get sending mailboxes compare on deliverability and risk.

Option Best for Deliverability Setup effort Main risk
Primeforge (Google Workspace and Microsoft 365) Teams that want ESP matching and provider-native trust High: real Google and Microsoft mailboxes, ESP matching Low: automated DNS, ready in about 30 minutes Higher cost per mailbox than shared infrastructure
Mailforge (shared infrastructure) Cost-efficient volume Good with warmup and sensible limits Low: automated DNS Shared IP reputation
Infraforge (dedicated IPs) Teams that want full control over IP reputation High once IPs are warmed Medium: dedicated IP provisioning IP reputation is yours alone to build
Buying Google Workspace or Microsoft 365 yourself Very small teams with time to configure High if configured correctly High: manual DNS, profiles and forwarding per domain Configuration mistakes and slow setup at scale
EDU or resold "loophole" mailboxes Not recommended Unstable Low Tenant-wide suspensions when the provider enforces its policies
Your main company domain Not recommended for cold email Fine at first None Spam issues spread to all company email
The setup I see working best combines options: Primeforge for ESP-matched Google and Microsoft mailboxes, paired with Mailforge or Infraforge for extra volume and diversification.

Monitor Deliverability Every Week

Deliverability drifts slowly and then drops quickly, so a weekly check catches problems while they're still small.

  • Inbox placement tests from your real mailboxes, read per provider.
  • Google Postmaster Tools for your sending domains, including its compliance status view.
  • Blocklist checks for every sending domain. Here's how to check if your domain is blacklisted.
  • Bounce codes and reply rate by mailbox, since one weak mailbox usually shows up there first.
This step-by-step email deliverability check turns these into a routine you can run in one sitting.

How Primeforge Handles the Foundation

Primeforge covers the first five fixes on this list, so you start from infrastructure that's already set up for cold outreach.

It provides real Google Workspace and Microsoft 365 mailboxes built for cold email. Here's what's included:

  • Real Google Workspace and Microsoft 365 mailboxes: Properly licensed and configured on the two providers most prospects use. No EDU accounts, repurposed tenants or loopholes that break when a provider updates its policies.
  • ESP matching: Send from the same provider your recipient uses, Google to Google and Microsoft to Microsoft, for better primary inbox placement.
  • Automated DNS setup: SPF, DKIM and DMARC are configured automatically on every domain, with no manual DNS work.
  • Pre-warmed mailboxes: Mailboxes that are ready to send from day one, sold separately.
  • Mailbox profile branding: Profile pictures, GIFs and profile setup handled out of the box, so every sender looks like a real person.
  • Domain forwarding: Redirect secondary domains to your main website or a landing page from inside Primeforge, with no external registrar needed.
  • Workspaces: Organize mailboxes across projects and clients.
  • Works with any sending tool, with a native Salesforge integration that shares the same login.
  • Primeforge API and Forge MCP CLI: Provision mailboxes programmatically, or let an AI agent manage them through MCP.

Pricing: $4.50 to $3.50 per mailbox per month billed annually, with the price dropping at volume. Your first mailbox is live in about 30 minutes. There's no free trial because mailboxes have to be purchased, but you can explore the app for free before buying.

Primeforge is one of three infrastructure options in the Forge Stack, all under one login: Mailforge for shared infrastructure and Infraforge for dedicated IPs. The most successful teams I see run two or more providers, typically Primeforge with Mailforge or Infraforge, so they always have a matching mailbox for each prospect.

On Salesforge, the rest of the list is handled too. Warmforge warmup is included free with unlimited slots on every plan, and ESP matching, sender rotation, Bounce Shield and text-only sending protect the mailboxes you just set up. You can run the stack with your own team, hand it to Agent Frank, Salesforge's AI SDR, or work with a certified Forge Expert agency.

Easiest Email Infrastructure Set Up Tutorial 2026 (Primeforge Guide)

Start from infrastructure built for cold email

Google Workspace and Microsoft 365 mailboxes with automated DNS, ESP matching, profile branding and domain forwarding. First mailbox live in about 30 minutes.

Final Verdict

Fix deliverability from the bottom of the stack up, and most of the copy problems disappear on their own.

If I had to rank the nine fixes, the first four do most of the work: real Google and Microsoft mailboxes, secondary domains, enough mailboxes for your volume, and ESP matching. Authentication and warmup are the requirements that let those mailboxes earn trust. Sending limits, list hygiene and plain copy keep that trust intact, and weekly monitoring tells you when something slips.

Primeforge is how I'd build the foundation. Paired with Mailforge or Infraforge, warmed with Warmforge and sending through Salesforge, it's part of the only stack I know that puts infrastructure, deliverability, lead data from Leadsforge, multichannel outreach and an AI SDR in Agent Frank under one roof.
Checklist of nine cold email deliverability fixes, from real mailboxes to plain-text copy

Build your cold email foundation in 30 minutes

Pick Google or Microsoft per domain, let Primeforge set up DNS, and start warming the same day.

FAQs About Improving Email Deliverability

Quick answers to the questions I get most about improving deliverability for cold email.

What is the fastest way to improve email deliverability?

Check your foundation first. Make sure you send from real Google Workspace or Microsoft 365 mailboxes on secondary domains, that SPF, DKIM and DMARC pass, and that no mailbox sends more than about 20 to 30 cold emails a day. Those fixes usually move placement faster than any copy change.

Why are my cold emails going to spam?

The most common causes are sending from a new or unwarmed mailbox, missing or misaligned authentication, too much volume per mailbox, a high bounce rate from an unverified list, and marketing-style formatting. Fix them in that order, then retest placement.

What is ESP matching?

ESP matching means sending from the same email provider your recipient uses: a Google mailbox to a Gmail or Google Workspace recipient, and a Microsoft mailbox to an Outlook or Microsoft 365 recipient. Providers tend to trust mail from their own ecosystem, which improves primary inbox placement.

Should I send cold emails from my main domain?

No. Send from secondary domains that redirect to your main website. If a campaign damages a secondary domain's reputation, your main domain and everyday company email stay unaffected.

How many cold emails can one mailbox send per day?

I keep each mailbox to roughly 20 to 30 cold emails a day once it's warmed, and ramp new mailboxes up gradually. When you need more volume, add mailboxes and domains instead of pushing each mailbox harder.

How long should I warm up a new mailbox?

About two weeks before sending cold email, and keep warmup running afterwards. A Heat Score™ of 85 or above in Warmforge is a good signal that a mailbox is ready to scale. Pre-warmed mailboxes let you start sooner.

Are Google Workspace or Microsoft 365 mailboxes better for cold email?

Neither wins on its own. The best results come from having both, so you can match each prospect's provider. Running two providers also protects your outreach if one of them changes its policies.

Does Primeforge include email warmup?

Primeforge provides the mailboxes and handles DNS setup. Warmup comes from Warmforge, which is included free with unlimited slots on every Salesforge plan and also available on its own. Primeforge also sells pre-warmed mailboxes separately for teams that want to send from day one.

Scale outreach with real Google and Microsoft inboxes

Set up Google Workspace and Microsoft 365 inboxes faster.
Start with
4.6 rating on G2
Add as a preferred
source on Google