You can write the perfect email and never reach the inbox. The copy is sharp, the offer is right, the list is your actual buyers, and the email lands in spam anyway. Deliverability is the problem most B2B teams never check until their numbers quietly collapse and nobody can say why.

Here is the part that frustrates people: deliverability is mostly a technical problem, not a creative one. The fix is rarely "write better." The fix is usually "set up the authentication you skipped."

The three reasons mail goes to spam

Almost every deliverability problem is one of three things.

Authentication is incomplete. Your domain is missing or misconfiguring SPF, DKIM, or DMARC. This is the most common cause and the easiest to fix.

Reputation is poor. Too many bounces, too many spam complaints, or a sudden volume spike has trained the receiving servers to distrust your domain.

Content trips filters. Spammy phrasing, an image-only email with no text, too many links, a misleading subject line. This matters, but it is the last layer, not the first.

People reach for the content explanation because it feels like something they can control by writing differently. But the content is rarely the real problem. The authentication usually is.

SPF, DKIM, DMARC: the foundation

These three records prove your email actually comes from you. SPF lists which servers can send for your domain. DKIM adds a cryptographic signature. DMARC tells receiving servers what to do with mail that fails the first two.

As of February 2024, this stopped being best practice and became a requirement. [Google and Yahoo's sender rules](https://blog.google/products/gmail/gmail-security-authentication-spam-protection/) now require bulk senders to authenticate with SPF and DKIM, publish a DMARC policy, keep spam complaints below 0.3 percent, and include one-click unsubscribe. The bar moved. B2B senders who set this up years ago are fine. The ones who never did are watching deliverability degrade and blaming their copy.

This is a one-time technical fix. A developer or your email platform's support can complete it in an afternoon. It is the single highest-impact thing on this list because it is the foundation everything else sits on.

Reputation is earned and lost over time

Your sending domain has a reputation with the receiving servers, built from how recipients treat your mail. High engagement and low complaints build trust. Bounces, complaints, and spam-folder placements erode it.

The fastest way to wreck it is a sudden volume spike to a stale list. You import an old list of 10,000 addresses, send to all of them at once, half bounce, a chunk mark it as spam, and now the domain your real client emails come from is flagged. The damage outlasts the campaign.

Protect the reputation. Send to engaged addresses. Ramp volume gradually. Keep the complaint rate low. Reputation is slow to build and fast to lose, so treat it like the asset it is.

Cold outreach belongs on a separate domain

This one catches B2B companies constantly. They run cold outreach from their main domain, the bounces and complaints pile up, and suddenly their normal client communication is landing in spam.

Serious cold outreach uses a separate sending domain, verified addresses, warmed-up inboxes, and conservative volume. The whole point is to isolate the risk. If the cold domain's reputation takes a hit, your primary domain, the one your invoices and client emails go from, is untouched. Mixing cold outreach into your primary domain is one of the most common ways B2B teams poison their own deliverability without realizing it.

Clean the list

Sending to old, unverified, or unengaged addresses produces the exact signals that hurt you: bounces and spam-folder placements that train receiving servers to distrust you.

Clean it. Remove hard bounces. Verify addresses before a large send. Sunset contacts who have not engaged in a long time, even though it feels wrong to shrink the list. A smaller engaged list outperforms a larger stale one on both deliverability and actual results. The vanity of a big number is costing you the inbox.

Then, and only then, the content

Once authentication is solid, reputation is protected, and the list is clean, content is the last layer. Avoid spam-trigger phrasing. Include a plain-text version, not just an image. Keep the link count reasonable. Write the way you would to one person, because mail that reads like a human wrote it to a human performs better with filters and recipients both.

Run a test through a tool like Mail-Tester before a big send. It scores the message and flags both authentication and content problems in one shot. If your opens dropped suddenly without a content change, deliverability is the first place to look, not the last.

Closing thought

Deliverability is not a writing problem. It is a technical one, and most B2B teams never check it until the numbers fall.

Set up SPF, DKIM, and DMARC. Protect your sending reputation. Keep cold outreach off your main domain. Clean the list. Get those right and the inbox opens back up, and your good copy finally gets the chance to work.

How to diagnose a deliverability problem: the five-step triage sequence

If your open rates dropped, your emails are bouncing more than usual, or a prospect told you they never received your message, do not guess. Run through this sequence in order before touching anything.

Step one: check authentication. Go to MXToolbox and run a free check on your domain's SPF, DKIM, and DMARC records. If any of them are missing or return errors, that is your problem. Fix authentication before doing anything else.

Step two: check your domain's reputation. Use Google Postmaster Tools (free, takes 10 minutes to set up) to see how Gmail rates your domain's reputation. Postmaster shows you your spam rate, IP reputation, and domain reputation over time. A yellow or red rating on domain reputation explains most deliverability collapses.

Step three: check your bounce rate. Log into your sending platform — HubSpot, Mailchimp, Instantly, or whichever tool you use — and pull the bounce rate on your last five sends. A hard bounce rate above 2 percent is a red flag. Above 5 percent means the list needs immediate attention before the next send.

Step four: send a test through Mail-Tester. Go to mail-tester.com, get a test address, send a real email to it, and check the score. Mail-Tester flags authentication gaps, spam-trigger phrases, broken HTML, and missing plain-text versions in one report. A score below 8 out of 10 tells you where to fix.

Step five: check your spam complaint rate. If you send through Google Workspace, Google Postmaster shows your complaint rate. If you send through an ESP, the platform dashboard shows it. A complaint rate above 0.1 percent is worth investigating. Above 0.3 percent is the threshold where Google and Yahoo begin filtering your mail more aggressively. Any complaint rate trend upward needs attention immediately.

Warming a new sending domain: the 30-day schedule that works

If you are setting up a new sending domain — for cold outreach, for a new company, or to replace a damaged domain — you cannot send at full volume on day one. The receiving servers have no history with you, and a sudden burst of email from an unknown domain will be treated as suspicious. Warming is the process of building that reputation gradually.

The core principle: start very low and increase volume slowly over 30 days, sending only to your most engaged contacts early on. High engagement signals (opens, replies, clicks) in the first two weeks teach the receiving servers that recipients want your mail.

A working 30-day schedule for a B2B team:

  • Days 1–5: Send 20–30 emails per day to contacts you know personally or who have recently engaged with you. Expect high open rates. That is the point.
  • Days 6–10: Increase to 50–75 per day. Still use your most engaged segment. Monitor bounce rate daily — if it climbs above 2 percent, pause and clean the list.
  • Days 11–20: Increase to 150–200 per day. You can now begin including contacts who are warm but not your highest-engagement segment. Watch Google Postmaster for domain reputation changes.
  • Days 21–30: Move to 300–500 per day. By now the domain has enough positive history to handle moderate volume without triggering filters.

Use a tool built for warming — Instantly, Lemwarm, or Mailwarm — which automate the ramp and add warming interactions between real inboxes to accelerate reputation building. Never skip the warm-up on a new domain and expect to go straight to 1,000 sends a day. The reputation damage from that mistake can take months to repair.

Related guides: HubSpot for SMBs · HubSpot Breeze AI review · Marketing ops automation with n8n · AI lead generation system · Work with José