Email deliverability
Deliverability is about whether expected email actually reaches the inbox. Check sending status, authentication and actual receipt separately.
Email deliverability describes how reliably expected messages reach the inbox. For your software, that includes sign-in notifications or status updates. AWS distinguishes successful delivery, bounces and complaints.
A portal example
In the fictional workflow, a portal sends status email M-453. The application reports a successful handover to its sending service. The interface should not turn that into “read by the customer”. Acceptance by the receiving mail system does not establish the displayed folder either.
In this design, each observation gets a separate status. Service feedback is linked to the message; missing feedback remains unknown. The team also checks visible placement using approved test mailboxes. This is a planned test, not a delivery result achieved here.
Investigate specific causes
Google includes authentication and spam complaints in its sender requirements. A correct SPF, DKIM or DMARC result therefore does not replace delivery observation. AWS describes separate feedback for bounces and complaints. When problems occur, examine the affected sending route and the specific feedback before triggering the same message again.
Sources
Related terms
- Sender Policy FrameworkSPF checks a sending server’s authorisation to use an SMTP domain. The visible sender line and receipt are separate questions.
- DomainKeys Identified MailDKIM links signed email components to a domain. A valid signature establishes neither encryption nor the person behind the message.
- DMARCDMARC links a successful SPF or DKIM check to the visible sender domain. Policy and reports help with its technical oversight.
Articles on this topic
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.