DSN (Delivery Status Notification)
What is DSN (Delivery Status Notification)?
A DSN (Delivery Status Notification) is the standardized report a mail server sends when it can't deliver a message, defined by RFC 3461 and RFC 3464. Its status code and failing recipient are machine-readable, separate from the bounce text a person reads. AdminKit's bounce-and-backscatter guide explains how a forged sender turns DSNs into a backscatter flood.
By AdminKit team, Netbase JSC · Updated
A DSN (Delivery Status Notification) is the standardized, machine-readable report a mail server generates to tell a sender what happened to a message it couldn’t deliver, or in some cases confirm one it could — defined by RFC 3461’s SMTP extension for requesting them and RFC 3464’s format for the report itself. A DSN includes a status code drawn from IANA’s SMTP Enhanced Status Codes registry, identifying the failure class (permanent versus temporary), the recipient address that failed, and which server reported the problem: machine-parseable fields a sender’s own systems can act on automatically, separate from the human-readable bounce text a mailbox owner actually reads — Microsoft’s own documentation on non-delivery reports walks through that same status-code/bounce-text split for Exchange Online. On the sending side, Postfix’s DSN documentation describes what the extension lets a sender choose through extra parameters on the SMTP MAIL FROM and RCPT TO commands: which notifications to get (success, failure, delay or none) and whether a failure report returns only the message headers or the full message. RFC 5321 requires a DSN for a failed delivery to be sent with a null envelope sender (MAIL FROM:<>), specifically so a DSN about an undeliverable message can never itself generate another DSN and loop forever — the same rule that, when a message’s original envelope sender was forged, concentrates every resulting DSN onto whichever address was forged rather than the real sender. A domain running a catch-all address never generates this DSN for an unrecognized recipient in the first place, since it accepts the message outright instead of rejecting it.
DSN (Delivery Status Notification) is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What fields in a DSN are machine-readable?
A status code identifying the failure class (permanent versus temporary) and the recipient address that failed, separate from the human-readable bounce text a mailbox owner reads.
Why must a DSN be sent with a null envelope sender?
So a DSN about an undeliverable message can never itself generate another DSN and loop forever, as RFC 5321 requires.
What happens to DSNs when a message's original envelope sender was forged?
They concentrate onto whichever address was forged rather than the real sender, since the null-sender rule only stops DSN loops -- it doesn't stop a forged original sender from receiving them.
Does a domain with a catch-all address generate a DSN for an unrecognized recipient?
No -- it accepts the message outright instead of rejecting it, so no DSN for an unrecognized recipient is ever generated.