Delivery Status Notification: Unterschied zwischen den Versionen
| Zeile 23: | Zeile 23: | ||
==DSN laut RFC | ==DSN laut RFC 3463== | ||
[https://datatracker.ietf.org/doc/html/rfc3463 rfc3463: Enhanced Mail System Status Codes] | [https://datatracker.ietf.org/doc/html/rfc3463 rfc3463: Enhanced Mail System Status Codes] | ||
Leider gibt es keine Bindung an die RFC Vorgabe. Mailserver Administratoren können beliebige Texte mit den Statuscodes verknüpfen. Es gibt also keine Gewähr für die korrekte Verwendung der Numerischen Codes. Dadurch können Kombinationen auftreten, mit gegensätzlichen Informationen. Beispiel: ein numerischer Hard-Bounce, mit einem textlichen Soft-Bounce. | Leider gibt es keine Bindung an die RFC Vorgabe. Mailserver Administratoren können beliebige Texte mit den Statuscodes verknüpfen. Es gibt also keine Gewähr für die korrekte Verwendung der Numerischen Codes. Dadurch können Kombinationen auftreten, mit gegensätzlichen Informationen. Beispiel: ein numerischer Hard-Bounce, mit einem textlichen Soft-Bounce. | ||
| Zeile 37: | Zeile 37: | ||
|- | |- | ||
| 5.XXX.XXX || Permanent Failure || A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery. | | 5.XXX.XXX || Permanent Failure || A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery. | ||
|} | |||
{| class="wikitable" | |||
|+ SUBJECT | |||
|- | |||
! DSN !! Kurzbezeichnung !! Beschreibung | |||
|- | |||
| X.0.XXX || Other or Undefined Status || There is no additional subject information available. | |||
|- | |||
| X.1.XXX || Addressing Status || The address status reports on the originator or destination address. It may include address syntax or validity. These errors can generally be corrected by the sender and retried. | |||
|- | |||
| X.2.XXX || Mailbox Status || Mailbox status indicates that something having to do with the mailbox has caused this DSN. Mailbox issues are assumed to be under the general control of the recipient. | |||
|- | |||
| X.3.XXX || Mail System Status || Mail system status indicates that something having to do with the destination system has caused this DSN. System issues are assumed to be under the general control of the destination system administrator. | |||
|- | |||
| X.4.XXX || Network and Routing Status || The networking or routing codes report status about the delivery system itself. These system components include any necessary infrastructure such as directory and routing services. Network issues are assumed to be under the control of the destination or intermediate system administrator. | |||
|- | |||
| X.5.XXX || Mail Delivery Protocol Status || The mail delivery protocol status codes report failures involving the message delivery protocol. These failures include the full range of problems resulting from implementation errors or an unreliable connection. | |||
|- | |||
| X.6.XXX || Message Content or Media Status || The message content or media status codes report failures involving the content of the message. These codes report failures due to translation, transcoding, or otherwise unsupported message media. Message content or media issues are under the control of both the sender and the receiver, both of which must support a common set of supported content-types. | |||
|- | |||
| X.7.XXX || Security or Policy Status || The security or policy status codes report failures involving policies such as per-recipient or per-host filtering and cryptographic operations. Security and policy status issues are assumed to be under the control of either or both the sender and recipient. Both the sender and recipient must permit the exchange of messages and arrange the exchange of necessary keys and certificates for cryptographic operations. | |||
|} | |} | ||
Aktuelle Version vom 24. März 2022, 15:24 Uhr
Eine Delivery Status Notification (DSN) ist eine automatisch verschickte E-Mail eines Mailservers an den Absender einer E-Mail, um diesen über den Verlauf der Zustellung zu unterrichten.
DSNs werden in der Regel ausgelöst, wenn E-Mails endgültig nicht zustellbar sind („Permanent Failure“).
Ebenfalls üblich sind Zwischenmeldungen über ausstehende Lieferungen, wenn E-Mails vorübergehend nicht zugestellt werden können („Persistent Transient Failure“), beispielsweise wenn die Empfängermailbox voll ist oder kein Mail Transfer Agent des Adressaten verfügbar ist. Darauf folgt dann nach einiger Zeit entweder eine DSN über das endgültige Scheitern der Zustellung („Permanent Failure“) oder eine positive DSN über die erfolgreiche Zustellung („Success“).
Eine DSN bezüglich einer nicht oder vorübergehend nicht zustellbaren E-Mail bezeichnet man umgangssprachlich auch als Bounce Message.
Nicht jeder Mailanbieter unterstützt DSNs. Üblicherweise erhält der Sender, wenn er eine Zustellbestätigung erwartet, bei Auslieferung an einen Mailserver, welcher DSNs nicht unterstützt, eine Meldung, die zum Beispiel als „relayed to non-DSN-aware mailer“ wiedergegeben wird – insbesondere auch dann, wenn die Mail ordnungsgemäß zugestellt wurde.
Beziehung zwischen den Mailservern[Bearbeiten]
+-----+ +--------+ +---------+ +---------+ +------+ | | | | |Received-| | | | | | | => |Original| => ... => | From | => |Reporting| ===> |Remote| | user| | MTA | | MTA | | MTA | <No! | MTA | |agent| +--------+ +---------+ +----v----+ +------+ | | | | | <-------------------------------------------+ +-----+ (DSN returned to sender by Reporting MTA)
DSN laut RFC 3463[Bearbeiten]
rfc3463: Enhanced Mail System Status Codes Leider gibt es keine Bindung an die RFC Vorgabe. Mailserver Administratoren können beliebige Texte mit den Statuscodes verknüpfen. Es gibt also keine Gewähr für die korrekte Verwendung der Numerischen Codes. Dadurch können Kombinationen auftreten, mit gegensätzlichen Informationen. Beispiel: ein numerischer Hard-Bounce, mit einem textlichen Soft-Bounce.
| DSN | Kurzbezeichnung | Beschreibung |
|---|---|---|
| 2.XXX.XXX | Success | Success specifies that the DSN is reporting a positive delivery action. Detail sub-codes may provide notification of transformations required for delivery. |
| 4.XXX.XXX | Persistent Transient Failure | A persistent transient failure is one in which the message as sent is valid, but persistence of some temporary condition has caused abandonment or delay of attempts to send the message. If this code accompanies a delivery failure report, sending in the future may be successful. |
| 5.XXX.XXX | Permanent Failure | A permanent failure is one which is not likely to be resolved by resending the message in the current form. Some change to the message or the destination must be made for successful delivery. |
| DSN | Kurzbezeichnung | Beschreibung |
|---|---|---|
| X.0.XXX | Other or Undefined Status | There is no additional subject information available. |
| X.1.XXX | Addressing Status | The address status reports on the originator or destination address. It may include address syntax or validity. These errors can generally be corrected by the sender and retried. |
| X.2.XXX | Mailbox Status | Mailbox status indicates that something having to do with the mailbox has caused this DSN. Mailbox issues are assumed to be under the general control of the recipient. |
| X.3.XXX | Mail System Status | Mail system status indicates that something having to do with the destination system has caused this DSN. System issues are assumed to be under the general control of the destination system administrator. |
| X.4.XXX | Network and Routing Status | The networking or routing codes report status about the delivery system itself. These system components include any necessary infrastructure such as directory and routing services. Network issues are assumed to be under the control of the destination or intermediate system administrator. |
| X.5.XXX | Mail Delivery Protocol Status | The mail delivery protocol status codes report failures involving the message delivery protocol. These failures include the full range of problems resulting from implementation errors or an unreliable connection. |
| X.6.XXX | Message Content or Media Status | The message content or media status codes report failures involving the content of the message. These codes report failures due to translation, transcoding, or otherwise unsupported message media. Message content or media issues are under the control of both the sender and the receiver, both of which must support a common set of supported content-types. |
| X.7.XXX | Security or Policy Status | The security or policy status codes report failures involving policies such as per-recipient or per-host filtering and cryptographic operations. Security and policy status issues are assumed to be under the control of either or both the sender and recipient. Both the sender and recipient must permit the exchange of messages and arrange the exchange of necessary keys and certificates for cryptographic operations. |