Delivery: a technical, binary outcome

Delivery is decided during the SMTP conversation described in RFC 5321. After your server sends the message data, the receiving server either replies 250 OK, meaning it has accepted responsibility for the message, or it refuses with a 4xx (temporary) or 5xx (permanent) code. An accepted message counts as delivered. A refused one becomes a deferral or a bounce.

That’s what most email platforms report as “delivery rate”: accepted messages divided by messages sent. It mainly reflects three things:

  • Address validity. Non-existent mailboxes and dead domains return 5xx codes and show up as hard bounces.
  • Outright blocks. A provider that has blocklisted your IP or domain, or that rejects unauthenticated mail, refuses the message before it’s ever accepted.
  • Throttling. Providers that distrust your sending pattern defer mail with 4xx codes, which can turn into soft bounces if retries run out.

Deliverability: what happens after acceptance

Acceptance is only the first step. Once the receiving server has the message, its filtering decides where it goes: the primary inbox, a category tab such as Gmail’s Promotions, the spam folder, or occasionally nowhere visible at all. This is deliverability, often measured as inbox placement.

The main inputs are:

  • Sender reputation for your sending domain and IPs, built from complaint rates, bounce history, spam-trap hits and engagement. See sender reputation.
  • Authentication. SPF, DKIM and DMARC results, and whether the authenticated domain aligns with the visible From address. Google’s sender guidelines require all of these for bulk senders.
  • Complaints. Google and Yahoo both ask senders to keep the user-reported spam rate below 0.3%, and Google recommends staying under 0.1%.
  • Engagement. Opens, replies, deletions without reading, and moves out of spam all shape future filtering.
  • Content and formatting. Broken HTML, misleading subject lines, link shorteners and messages that don’t follow RFC 5322 formatting are all negative signals.

Why the distinction matters

The two metrics fail in different ways, so they need different fixes. A team can see a 99% delivery rate in its dashboard and conclude everything is fine while open rates and conversions quietly decline, because a growing share of “delivered” mail is going to spam. Delivery rate alone will never show that problem.

The reverse also happens. A sender with strong reputation and authentication can still post a poor delivery rate if they import an old list full of invalid addresses. In that case, the bounces themselves become the reputation problem, and deliverability follows delivery downward.

A third pattern sits in between: delivery holds steady at most providers but drops at one, with a cluster of 4xx deferrals or 5.7.x policy rejections. That is a provider-specific reputation problem. It shows up first in your delivery data, but the fix is on the deliverability side.

How to improve each one

To improve delivery:

  1. Verify addresses before sending, and suppress hard bounces immediately.
  2. Make sure your domain passes SPF and DKIM and publishes a DMARC record, so providers don’t reject unauthenticated mail.
  3. Check whether your sending IPs or domains appear on major blocklists when bounces spike.

To improve deliverability:

  1. Monitor Gmail Postmaster Tools for spam rate, reputation and authentication, and use complaint feedback loops where providers offer them.
  2. Mail engaged recipients first and sunset people who haven’t opened or clicked in months.
  3. Offer one-click unsubscribe so unhappy recipients leave rather than complain.
  4. Run seed-list or panel-based placement tests when you change infrastructure, content templates or volume.

Industry groups such as M3AAWG publish sender best practices that cover both sides in more depth.

Where RocketVerifier helps

List hygiene is the part of the delivery problem you fully control. RocketVerifier’s bulk email verification removes addresses that would bounce before you send, and the free email deliverability checker confirms your SPF, DKIM and DMARC setup. For ongoing visibility, deliverability monitoring checks your SPF, DKIM and DMARC records on a schedule and alerts you when one breaks, before it shows up as falling engagement.