Behind the Scenes of Email Deliverability and Inbox Placement

Deliverability is easy to overlook when emails are being sent without errors. But "sent" and "delivered to the inbox" are two different things, and the gap between them can be substantial without anyone noticing until open rates start declining or a campaign returns unusually high bounce numbers.

The mechanics of deliverability are unglamorous. They involve DNS records, IP reputation scores, authentication protocols, and list management practices that nobody finds exciting to think about. But they determine whether your emails reach the people you're sending them to.

Authentication: the Non-negotiable Foundation

Three authentication standards are essential for email deliverability:

SPF (Sender Policy Framework) is a DNS record that specifies which IP addresses and servers are authorized to send email on behalf of your domain. When a receiving server gets an email claiming to be from your domain, it checks your SPF record to verify the sending source is authorized.

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to each outgoing email. Receiving servers verify the signature against a public key in your DNS records, confirming the email hasn't been altered in transit and genuinely came from an authorized sender.

DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties SPF and DKIM together and specifies what should happen when authentication fails — whether to quarantine suspicious emails, reject them, or take no action. It also provides you with reports about who's sending email using your domain.

Gmail and Yahoo implemented stricter authentication requirements in 2024, requiring SPF, DKIM, and DMARC for bulk senders. These aren't best practices anymore — they're baseline requirements. If you're sending significant email volume without them, you're likely already experiencing deliverability problems.

Your email service provider's documentation will walk you through the specific DNS records needed for their infrastructure.

The Permission Problem

A surprising amount of deliverability trouble originates before the first email is sent, in how the list was built.

A list assembled through genuine opt-ins — people who actively asked to hear from you, knew what they were signing up for, and expected your emails — will typically perform very differently from a list that was scraped, purchased, added from a trade show badge scan without explicit consent, or built from checkbox pre-ticked by default.

People who didn't expect your emails are more likely to ignore them (harming engagement metrics), mark them as spam (directly damaging your sender reputation), and generate bounces (sending to addresses that were never valid). These behaviors accumulate into reputation signals that mailbox providers use to decide whether future emails go to the inbox.

This doesn't mean your list needs to be tiny. It means every addition to the list should be genuinely consensual. Double opt-in — requiring subscribers to confirm via a click before being added — produces a more reliable list and protects you from malicious or accidental sign-ups using invalid email addresses.

Understanding Your Sender Reputation

Your sender reputation is built around two identifiers: your sending IP address and your sending domain.

If you send through a shared IP (common in lower-cost ESP plans), other senders on the same IP affect your reputation. One bad actor on the same IP sending spam can cause all users on that IP to experience deliverability problems. This is one argument for dedicated IPs for higher-volume senders, though dedicated IPs come with their own requirement: you need consistent sending volume to maintain a warm reputation.

Reputation-affecting signals:

• Spam complaint rate: the percentage of recipients who mark your email as spam. Below 0.1% is healthy; above 0.3% starts causing problems with major mailbox providers.
• Bounce rate: hard bounces (invalid addresses) should be removed immediately. A hard bounce rate above 2% indicates list hygiene problems.
• Engagement rate: mailbox providers, particularly Gmail, factor engagement into placement decisions. Emails to a segment that consistently doesn't open end up in spam more readily over time.

List Hygiene: the Ongoing Practice

An email list isn't static. Addresses become invalid when people leave companies or abandon old accounts. Engagement levels shift as subscribers lose interest.

Remove hard bounces immediately after they occur — there's no value in continuing to send to invalid addresses, and continued sending harms your reputation.

For inactive subscribers — those who haven't opened or clicked anything in 6-12 months — build a re-engagement sequence. Send a small number of emails with the explicit framing of "we noticed you haven't engaged recently — is this still useful to you?" Some will re-engage. Those who don't after a few re-engagement attempts should be moved to a suppression list rather than continued sending.

Separating Transactional and Marketing Email

A password reset email and a promotional newsletter serve different purposes and have different deliverability requirements.

Transactional emails — account confirmations, receipts, shipping notifications, password resets — are expected by the recipient. They're triggered by the recipient's action and have high engagement rates. They should come from a dedicated sending domain or subdomain separate from your marketing email domain.

If your marketing email gets complaints or deliverability problems, you don't want that reputation bleeding over into your transactional email infrastructure. People need to receive their receipts and password resets even when a promotional campaign underperforms.

Content Signals That Affect Deliverability

Authentication and list quality are the foundation. Content plays a secondary role in deliverability, but it's not irrelevant.

Emails that are almost entirely image-based with little text are common in spam filters' training data. Most modern email clients can render images, but an email that's 90% image and 10% text looks like a pattern commonly used to evade text-based filters.

Certain types of links and specific phrase patterns associated with spam can trigger filters. You don't need to be paranoid about individual words, but writing emails that look and read like genuine communications — rather than marketing blasts optimized for CTR — tends to perform better on deliverability.

Sending volume matters too. Gradually increasing volume from a new sending domain or IP — known as "warming" — is necessary because sudden large sends from a domain with no history look suspicious to mailbox providers. Most ESPs have guidance on recommended warming schedules.

Monitoring Deliverability

If deliverability problems are developing, you want to know before they've become severe.

Tools like Google Postmaster Tools (free, covers Gmail deliverability) and similar tools from Microsoft provide sender reputation data directly from the mailbox provider's perspective. A declining domain reputation score in Postmaster Tools is an early warning that something is wrong.

Monitor your campaigns' spam complaint rates through your ESP's reporting. Watch for trends — a single campaign with higher complaints might indicate a specific list segment problem. Multiple campaigns with increasing complaints indicates a systemic issue.