What is Email deliverability?
Between sending and reading there are three possible outcomes: the receiving server refuses the message, it accepts the message and files it in the spam folder, or it files it in the inbox. Your sending tool only sees the server's response and reports the last two cases together as delivered. The delivery rate therefore separates refusal from acceptance and nothing more. Deliverability means the third case, and no report shows it to you.
Deliverability rests on two independent checks. The first is technical and runs on every single message: do `SPF`, `DKIM` and `DMARC` line up with the sending address, does the message arrive over an encrypted connection, are the headers correctly formed. The second is reputation and builds over weeks out of how your recipients behave: complaint rate, opens, hard bounces, hits on retired addresses. A note on wording: a bounce here is a refused message and has nothing to do with the bounce rate in web analytics.
In practice that means authentication is a condition, not an advantage. It is done in an afternoon and prevents refusals, but it produces no opens whatsoever. Reputation builds slowly, and it is made by exactly the decisions that feel like marketing: how you collect addresses, how often you write, how easy the unsubscribe is to find, and whether recipients stay on the list who have opened nothing for a year. A smaller, clean list regularly delivers better than a large one.
Why does Email deliverability matter?
Google requires senders to keep the complaint rate below 0.30 per cent and recommends staying below 0.10 per cent as a steady state. At 2,000 delivered messages that is six people, or two, tapping "report spam". Small senders never get to see the rate itself, because Google only reports data in Postmaster Tools above a certain daily volume. Anyone who checks deliverability once the open rate collapses is seeing the problem months after it started.
Email deliverability in practice
- 01A business sends its newsletter with its own free mailbox address in the From field. The sending service cannot authenticate for that domain, the domain's policy sits at quarantine, and the message lands in the spam folder exactly as instructed.
- 02A list of 4,000 addresses is cut down to the 1,400 that opened something in the past year. The absolute number of opens barely moves, the complaint rate drops, and the sending domain's reputation recovers over the following sends.
- 03One single send to 5,000 Gmail addresses at the turn of the year makes the sender a bulk sender under the Google guidelines for good, even if only 300 messages a month go out afterwards.
