Topic · Deliverability
Email deliverability
Email deliverability describes whether an accepted message ultimately reaches the intended mailbox and the appropriate folder, distinct from an SMTP acceptance event.
How it works
Delivery depends on infrastructure, authentication, reputation, engagement and filtering.
What can go wrong
Accepted SMTP delivery does not establish inbox placement. Spam-folder routing and silent quarantine are separate outcomes.
What to check or do
Track acceptance, deferrals, bounces, complaints and placement separately.
Practical scenario
A verification-code email is accepted by the recipient’s SMTP server but is delivered to spam. Deliverability is an end-to-end outcome involving authentication, reputation, content and recipient filtering, not merely successful SMTP handoff.
Verification checklist
- Confirm aligned SPF or DKIM and the current DMARC policy.
- Separate transactional from bulk traffic where practical.
- Track complaint signals, blocklist status and real inbox testing.
- Measure user-visible latency and inbox placement for time-sensitive messages.
How to investigate Email deliverability
- Signal to investigate
- A campaign receives SMTP acceptance but far fewer messages reach inbox folders.
- Evidence to collect
- Separate acceptance, deferred, bounced, spam-folder and user engagement measures.
- Common wrong conclusion
- SMTP 250 queued is not proof the message was displayed to the recipient.
How to interpret the evidence
Email delivery comprises distinct outcomes: provider acceptance, possible deferral, recipient mailbox acceptance, folder placement and the recipient's eventual action. SPF/DKIM/DMARC are about authenticated identifiers; they do not directly measure whether a message reached the primary inbox or was opened. Correctly diagnosing a problem requires separating these layers.
What to change and how to verify it
Use message IDs to join API/provider acceptance, SMTP delivery status and relevant mailbox tests. Correlate with sender reputation, complaint trends and template changes. Define measurable critical-transaction targets for OTP and receipt traffic rather than promising universal inbox placement.
Put this into practice
Run a focused check, then explore protection if your domain needs it.