Email Deliverability Explained: Why "It Sent" Doesn't Mean "It Arrived"

Most people think of email as binary: either it sends, or it fails and you get an error message. In reality, there’s a third and much more common outcome — it sends successfully, your outbox shows no error, and it never reaches the inbox anyway. It might land in spam. It might be silently dropped by the receiving server with no notification to you at all. Either way, you have no idea it happened, and neither does your recipient.
This is what “deliverability” actually means, and why it’s a genuinely different problem from “can I send email.”
Sending vs delivering: two separate systems
When you hit send, your email server hands the message off to the recipient’s mail server. That handoff succeeding is what makes your outbox show “sent” — it just means the message was accepted for delivery attempt, not that it reached an inbox.
From there, the receiving server (Gmail, Outlook, Yahoo, or a business’s own mail system) runs its own independent judgement on what to do with that message: accept it into the inbox, route it to spam, or reject it outright. Your sending server has no visibility into that decision and no way to override it. This is why “I definitely sent it” and “they definitely got it” are two completely different claims — and why deliverability problems are so often invisible until a customer happens to mention it.
Why this matters more than it seems
For a small business, this gap tends to show up in specific, costly ways:
- Invoices that are never paid, not because the customer is difficult, but because they never saw the invoice — it sat in spam, and no one checked
- Quotes and proposals that go quiet, where you assume the customer lost interest when in fact your email never reached them
- Password reset or account emails from your website that customers report as “broken,” when the site is working fine and the email is simply not arriving
- A slow, compounding reputation problem — because every email a recipient never sees is also an email they never open, and low open rates are themselves one of the signals that damages your sending reputation further (see our [spam diagnostic checklist] for how this compounds)
None of these show up as an error on your end. They show up as lost revenue and confused customers, with the actual cause invisible unless you’re specifically looking for it.
How to actually check your deliverability, not just your sending
Because “sent successfully” tells you nothing about delivery, checking deliverability requires different tools:
- Seed testing — sending a test email to a set of addresses across different providers (Gmail, Outlook, Yahoo) and checking exactly where it lands: inbox, promotions tab, or spam.
- Google Postmaster Tools — free, and shows your domain’s reputation and spam-rate data directly from Gmail’s perspective, which is otherwise completely invisible to you.
- Reading full email headers — as covered in our [SPF, DKIM and DMARC guide], the authentication results embedded in a message’s headers are one of the strongest predictors of whether it was trusted on arrival.
- DMARC reporting — once DMARC is correctly configured, it generates regular reports showing exactly which of your sending sources are passing or failing authentication across every major provider — effectively an ongoing deliverability health check, rather than a one-off snapshot.
Why this is easy to miss for months
The uncomfortable part of deliverability problems is that they’re self-concealing. A business with a 20% delivery failure rate doesn’t see 20% of their outbox marked as failed — they see 100% marked as sent, and simply don’t hear back from a fifth of the people they emailed. Without deliberately testing for it, there’s no natural trigger that tells you to look.
That’s why we’d generally recommend treating a deliverability check as routine maintenance — worth doing after any change to your email setup (new provider, new website, new marketing tool), rather than only after you’ve already noticed a problem.
Where to go from here
If you’re not sure whether this affects you, the fastest way to find out is a proper deliverability test across major providers rather than guessing from your own inbox. If you already suspect it, our guides on why emails go to spam and what SPF, DKIM and DMARC mean cover the two most common underlying causes in more depth.
If you’d rather have someone check this properly and fix whatever’s found, that’s exactly what our free initial assessment does.
Need help fixing this?
We provide:
- Free initial assessment
- Clear explanation of the issue
- Fixed-price solutions
- UK-based support
If your emails are going to spam, we can identify the cause and fix it properly.
