Deliverability is the word people use for everything between pressing send and getting a reply. This page is the map: what the term covers, how it differs from delivery and placement, the six factors behind it, the order a new sender should fix them in, and where cold-email practice disagrees with industry standards.
What is email deliverability?
Deliverability is the outcome; delivery, placement and reputation are its parts. With good deliverability, messages are accepted, filed in the inbox and read. With poor deliverability, every message can be accepted and still draw no replies, because it went to spam or was quarantined by a gateway.
Cold email raises the stakes. Recipients did not ask for the message, so filters start out doubtful, and one badly targeted campaign can damage a domain for every send after it.
Delivery, inbox placement and reputation: how do they differ?
- Delivery: the receiving server accepted the message. The sending tool sees this, because the server answers during the transfer.
- Inbox placement: the accepted message reached the inbox, not spam. Validity's 2026 benchmark puts it at 87.2% globally, measured with seed accounts, so more than one accepted message in ten misses the inbox.
- Reputation: the receiver's memory of your domain and mailboxes, built from complaints, bounces, authentication results and engagement. It drives placement and changes slowly.
The three move in order. Reputation drives placement, placement decides whether anyone reads the message, and only replies prove that someone did.
Which six factors decide deliverability?
| Factor | What it means | Read more |
|---|---|---|
| Authentication | SPF, DKIM and DMARC prove the domain sent the message | Email authentication |
| Domain reputation | The receiver's history with your sending domain | Cold email infrastructure, Spam trap |
| Security gateways | Corporate filters in front of large companies' mail servers | Email security gateway |
| Inbox placement | Inbox or spam, after the server accepts the message | Inbox placement |
| Content | Images, links and heavy formatting read like phishing | Plain text email |
| Volume | How many messages each mailbox and domain sends a day | Email sending limits |
List quality runs through two of these. Bought or old lists carry spam traps, and a trap hit lands on the domain's reputation.
Validity's 2026 benchmark separates delivery rate from inbox placement and puts global placement at 87.2%. Spamhaus's sender guidelines require confirmed opt-in, rule out bought lists, and state that validation does not replace consent. M3AAWG's Sender Best Common Practices v4.0 (August 2026) treats opt-in as best practice and advises against cousin domains. Google's sender guidelines set the requirements for bulk senders, including one-click unsubscribe.
In what order should a new sender fix them?
In the order a message meets them, starting before the first send.
- Before sending: a separate domain. Keep the main company domain out of cold outreach.
- Before sending: authentication. SPF, DKIM and DMARC on every sending domain, confirmed with a test message.
- First weeks: low volume. Add mailboxes and domains rather than pushing one mailbox harder. Leadspicker's guidance is 5 cold emails per mailbox per day.
- First weeks: plain text. No images, no tracking pixel, one link at most.
- First weeks: gateway exclusion. Leave gateway-protected enterprise recipients out until the campaign draws replies.
- From then on: replies by domain. A domain whose replies stop while the others continue has a reputation problem; take it out of the rotation.
Where does cold-email practice conflict with industry standards?
In four places. Know them before choosing a side.
- Consent. Spamhaus and M3AAWG treat opt-in as the baseline and reject bought lists. Spamhaus adds that email validation does not replace consent. Cold outreach writes to people who did not opt in.
- Lookalike domains. M3AAWG advises against lookalike, or cousin, domains. Leadspicker, like much cold-email practice, recommends separate outreach domains so a problem cannot reach the main domain.
- New domains. Spamhaus advises against sending from a new domain for its first 30 days and treats warm-up services as grounds for listing. Cold-email setups usually start sooner, at low volume.
- Unsubscribe. Google requires one-click unsubscribe from senders above 5,000 messages a day. Leadspicker measured lower reply rates with an unsubscribe footer and sends one-to-one messages far below that threshold.
Standards protect recipients and the mail system as a whole. Cold-email practice protects a sender's ability to reach people who have not heard of them. Know which rule you are breaking and what it costs if a receiver enforces it.
Leadspicker sends plain text with open tracking off by default; a daily limit per mailbox, provider-matched rotation and gateway exclusion are set per sequence, and Leadspicker excludes gateway-protected recipients in its own campaigns.
Frequently asked questions
What is the difference between deliverability and delivery rate?
Delivery rate counts messages the receiving server accepted. Deliverability asks whether they reached the inbox and were read, which a high delivery rate does not guarantee.
What should a new sender fix first?
A separate sending domain and authentication, before the first message. Then low daily volume, plain text and gateway exclusion during the first weeks.
Does email verification fix deliverability?
It lowers bounces and removes typo and dead addresses. It does not make a list consented, and Spamhaus is explicit that validation does not replace opt-in.
