Email Deliverability · How Inbox Placement Works

Two terms are often confused: email delivery and email deliverability. Delivery means the receiving mail server accepted your email — it did not bounce. Deliverability means the email reached the recipient's inbox rather than their spam/junk folder or promotions tab.

A 0% hard bounce rate and 100% delivery rate does not mean your emails are reaching inboxes. An email accepted by Gmail's servers may still be routed to Spam — delivery succeeded but deliverability failed. Most ESP dashboards show delivery rates (non-bounced sends) but not inbox placement rates — which requires dedicated inbox placement monitoring tools.

When you send an email campaign, each message travels through multiple decision points before reaching (or not reaching) the inbox:

1. ESP sends from a sending IP. Your email service provider (Mailchimp, Klaviyo, etc.) sends your email from its infrastructure — either a shared IP pool used by many senders or a dedicated IP assigned to your account.
2. Receiving server looks up DNS records. The recipient's mail server (Gmail, Outlook, etc.) looks up SPF, DKIM, and DMARC records for your sending domain to verify authenticity. Unauthenticated email is immediately suspect.
3. Reputation check. The receiving server checks the sending IP and domain against reputation databases (Spamhaus, SORBS, Barracuda) and its own reputation data. IPs and domains on block lists are rejected or filtered.
4. Content filtering. The email content is evaluated by spam filters — checking subject line, body text, link URLs, image-to-text ratio, and dozens of other signals.
5. Engagement data applied. Gmail, Outlook, and other major providers use their users' historical engagement with your domain — how often recipients open, click, reply, delete unread, or mark as spam — as a major inbox placement signal.
6. Inbox placement decision. Based on all signals, the email is routed to Inbox, Promotions, Social, Spam, or rejected.

Sender reputation is a score maintained by internet service providers (ISPs) and mailbox providers (Gmail, Outlook) for sending IP addresses and domains. High reputation = preferential inbox treatment. Low reputation = spam folder or block. Reputation is invisible to senders — no single public score, but behaviour over time determines it.

Factors that build reputation

• Consistent sending volume (not large spikes after silence)
• Low bounce rates (under 2% hard bounce rate)
• Low spam complaint rate (under 0.08% per send)
• High engagement — opens, clicks, replies, forwarding
• Proper authentication (SPF, DKIM, DMARC all passing)
• Clean list — only subscribers who explicitly opted in

Factors that damage reputation

• High spam complaint rates — even 0.1% triggers ISP action
• High bounce rates — particularly hard bounces from invalid addresses
• Sending to spam trap addresses — ISPs maintain hidden addresses; emailing them signals a dirty list
• Sudden large volume spikes from a new or dormant IP
• Recipients consistently deleting emails unread (signal of disinterest)

Gmail and other major providers use their users' behaviour as a direct inbox placement signal — treating engagement data as the strongest indicator of whether emails are wanted. Key engagement signals:

Spam filters evaluate hundreds of signals. Key content-level signals:

• Spammy subject line patterns. ALL CAPS, excessive punctuation (!!!), trigger words ("FREE", "Act Now", "Limited Time") in subject lines are still weighted by some filters — though modern filters are more sophisticated than simple keyword matching.
• Image-to-text ratio. Emails with very high image content and minimal text are flagged — a common spam technique is sending images containing the message text to avoid text-based filtering. Aim for at least 60:40 text-to-image ratio.
• Link reputation. URLs in your email are checked against reputation databases. Links to domains on block lists cause the entire email to be filtered, even if the sending domain is clean.
• Shortened URLs. URL shorteners (bit.ly, tinyurl) are frequently abused by spammers — many spam filters treat shortened URLs with suspicion. Use full URLs in email.
• HTML quality. Broken HTML, excessive nested tables, non-standard code structures, and HTML-only emails with no plain text alternative are red flags.

IP warming is the process of gradually increasing sending volume from a new IP address to build a positive sending reputation before sending at full volume. ISPs are suspicious of IP addresses that suddenly appear and immediately send hundreds of thousands of emails — this pattern matches spam behaviour.

When IP warming is required

• New dedicated sending IP (switching ESP or requesting a dedicated IP)
• Previously dormant IP that has not sent email in 90+ days
• Migrating to a new ESP and using their dedicated IP infrastructure

Typical warming schedule

• Check bounce reports. Your ESP reports hard bounces (permanent invalid addresses) and soft bounces (temporary delivery failures). A hard bounce rate above 2% is a deliverability risk — remove hard-bounced addresses immediately and investigate the source of invalid addresses.
• Monitor spam complaint rate. Your ESP provides complaint rate data; Google Postmaster Tools shows complaint rate specifically for Gmail recipients. Rates above 0.08% should trigger immediate investigation — typically caused by sending to non-opt-in contacts or to very old, disengaged lists.
• Check Google Postmaster Tools. Free tool from Google showing: domain reputation, IP reputation, spam rate, authentication results, and delivery errors for Gmail specifically. Essential for senders where Gmail is a significant portion of their list.
• Test inbox placement. Tools like GlockApps, Mail-Tester, and Litmus Email Analytics send test emails to seed accounts across major inbox providers and report the actual inbox/spam/tab placement.
• Check block lists. MXToolbox (mxtoolbox.com/blacklists) checks your sending domain and IP against major block lists. Being listed on Spamhaus or Barracuda requires immediate remediation — contact the block list operator with a delisting request after addressing the underlying issue.

Authentic Sources