The most carefully researched, perfectly personalized cold email in the world does nothing if it lands in the spam folder. Deliverability, whether your emails reach the inbox, is the invisible constraint on every outreach metric you care about. A team with 15% open rates might actually have 25% open rates among the emails that actually reached inboxes, with 40% never getting there at all. Without deliverability monitoring, you're optimizing a metric that's being silently suppressed by a problem you're not aware of.
This guide covers the technical foundation, behavioral practices, and monitoring routines that keep your cold email deliverability healthy, not just when you set up your outreach system, but continuously as you scale and as email provider algorithms evolve.
How Email Deliverability Actually Works#
When you send a cold email, it travels from your sending infrastructure to the recipient's inbox by passing through a series of checks. The recipient's email provider (Google, Microsoft, or others) evaluates your email on multiple dimensions before deciding where to place it: the inbox, the spam folder, the promotions tab, or blocking it entirely.
The evaluation criteria fall into three categories: sender reputation (is this domain and IP address associated with sending high-quality, wanted email?), authentication (can we verify this email is actually from the domain it claims to be from?), and content quality (does the content pattern match spam signals or look like legitimate communication?). Problems in any of these categories produce deliverability failures, and the solutions are completely different depending on which category the problem is in.
The Technical Foundation: Authentication Records You Can't Skip#
Three DNS records form the authentication foundation that every cold email sender needs to have correctly configured. These aren't optional best practices, they're requirements for reliable inbox delivery with major email providers.
SPF (Sender Policy Framework)#
An SPF record in your DNS specifies which mail servers are authorized to send email claiming to be from your domain. When a receiving server gets an email from your domain, it checks your SPF record to see if the sending server is on your approved list. Without a correct SPF record, many email providers will treat your emails as potentially spoofed and either reject or aggressively filter them. Add all email services you use (Google Workspace, Outreach, HubSpot, etc.) to your SPF record. Verify the record is correct at mxtoolbox.com/spf.aspx.
DKIM (DomainKeys Identified Mail)#
DKIM adds a cryptographic signature to every email you send. The signature is generated by a private key that only you control, and receiving servers verify it using the corresponding public key published in your DNS. This proves that emails claiming to be from your domain actually originated from your systems and weren't modified in transit. Your email service provider generates the DKIM keys, you just need to add the provided DNS record. Verify at mxtoolbox.com/dkim.aspx.
DMARC (Domain-based Message Authentication, Reporting, and Conformance)#
DMARC tells receiving servers what to do when SPF or DKIM fails: nothing (p=none, monitoring mode), quarantine the email (p=quarantine), or reject it outright (p=reject). Start with p=none to collect DMARC reports that show you which emails from your domain are failing authentication, there may be legitimate sending services you've forgotten to add to SPF. After cleaning up any legitimate authentication failures, move to p=quarantine and eventually p=reject to protect your domain from being used in phishing and to improve your overall sender reputation.
Domain Warming: The Step That Most Teams Skip#
Sending high-volume cold email from a domain with no history is one of the fastest paths to permanent deliverability damage. Email providers use historical sending patterns to assess sender reputation. A domain that's been sending legitimate email for two years and then adds cold outreach to its activity is evaluated very differently from a new domain that immediately starts sending 200 cold emails per day.
Domain warming builds the sending history that new domains or new outreach domains need before they can sustain high-volume cold email. The warming process: starting at 20-30 emails per day and increasing by 25-30% weekly over 6-8 weeks, using a mix of warm recipients (colleagues, newsletter subscriptions) and gradually introducing cold outreach as volume increases. Most teams also use automated warming services (Warmbox, Lemwarm, Mailreach) that exchange emails between large networks of real accounts to simulate the positive engagement patterns that build reputation.
Don't skip warming for a new outreach domain because "you need to send now." Rushing past warming for short-term volume consistently produces blacklistings that take weeks to months to recover from. The 6-8 weeks of patience upfront saves far more time than the recovery process after a premature high-volume launch.
Maintaining email deliverability health requires continuous monitoring across technical, behavioral, and content dimensions.
River's Sales workspace monitors deliverability health indicators automatically, sender reputation, bounce rates, complaint rates, with alerts when metrics fall below safe thresholds.
Monitor My Email DeliverabilitySending Behavior That Protects Your Reputation#
Technical configuration creates the foundation; sending behavior determines whether the foundation remains intact. Several common cold email behaviors consistently damage domain reputation:
High send volume to unverified contacts. Sending to email addresses that bounce hard (the address doesn't exist) raises your bounce rate. A bounce rate above 3% is a significant deliverability risk. Verify contact email addresses with NeverBounce or ZeroBounce before sending any new list. Remove hard bounces immediately, never retry a bounced address.
Identical content sent to many recipients. Bulk email filters look for identical message patterns across large send volumes. Even small variations in email content (different signal hooks, different company references) reduce the probability of being identified as bulk email. Genuine personalization improves deliverability as well as reply rates.
High spam complaint rates. When recipients mark your email as spam, that complaint signal directly affects your sender reputation. Keep spam complaint rates below 0.1%. The most common cause of elevated complaint rates: reaching recipients who have no connection to your product's value proposition and who therefore experience the email as irrelevant marketing rather than as relevant outreach. Better targeting reduces complaint rates alongside improving reply rates.
The Monitoring Routine That Catches Problems Early#
Deliverability problems develop gradually and are most addressable when caught early. A weekly 15-minute monitoring routine covers the most important indicators:
Google Postmaster Tools: Free tool from Google that shows your domain reputation for Gmail delivery (Low, Medium, High, or Very High). Any decline from High to Medium warrants investigation. Decline to Low requires immediate action and temporary pause of cold sending while the root cause is identified and addressed.
Bounce rate: Your email sending tool should show bounce rates per campaign or sequence. Review weekly. If any send produces a bounce rate above 3%, investigate the source list before sending more from the same list.
Open rate trend: A sustained decline in open rate (as a 4-week rolling average, not week-over-week noise) often indicates spam folder placement before it shows up in more direct deliverability metrics.
Inbox placement test: Run a manual test with GlockApps or Mail-Tester monthly: send a test email and see whether it lands in inbox, spam, or promotions across major email providers. This directly measures whether you have a placement problem rather than inferring it from open rates.
Recovering from a Deliverability Problem#
When deliverability is damaged, domain reputation is Low in Postmaster Tools, emails are consistently landing in spam, bounce rates are elevated, recovery requires stopping the behavior that caused the damage and rebuilding reputation through clean sending. The specific steps depend on the root cause.
For reputation damage from high bounce rates: stop sending until you've verified all lists. Implement email verification as a mandatory pre-send step. Resume sending gradually (restart the warming process) with verified lists only. For reputation damage from spam complaints: audit your targeting. Are you reaching people with no connection to your product? Tighten ICP criteria. For reputation damage from spam filter false positives: run your content through a spam score checker and address flagged elements. Reduce HTML complexity. Increase content variation across sends.
For teams using River's Sales workspace, deliverability monitoring is integrated into the outreach workflow, with health alerts that surface problems when they're still small enough to address without a full recovery process.