RFC 3798:Message Disposition Notification
RFC-Ref

Message Disposition Notification


1. Introduction
1.1. Purposes
1.2. Requirements
1.3. Terminology
2. Requesting Message Disposition Notifications
2.1. The Disposition-Notification-To Header
2.2. The Disposition-Notification-Options Header
2.3. The Original-Recipient Header
2.4. Use with the Message/Partial Content Type
3. Format of a Message Disposition Notification
3.1. The message/disposition-notification content-type
3.1.1. General conventions for fields
3.1.2. "*-type" subfields
3.2. Message/disposition-notification Fields
3.2.1. The Reporting-UA field
3.2.2. The MDN-Gateway field
3.2.3. Original-Recipient field
3.2.4. Final-Recipient field
3.2.5. Original-Message-ID field
3.2.6. Disposition field
3.2.6.1. Disposition modes
3.2.6.2. Disposition types
3.2.6.3. Disposition modifiers
3.2.7. Failure, Error, and Warning fields
3.3. Extension-fields
4. Timeline of events
5. Conformance and Usage Requirements
6. Security Considerations
6.1. Forgery
6.2. Privacy
6.3. Non-Repudiation
6.4. Mail Bombing
7. Collected Grammar
8. Message headers:
9. Report content:
10. Guidelines for Gatewaying MDNs
10.1. Gatewaying from other mail systems to MDNs
10.2. Gatewaying from MDNs to other mail systems
10.3. Gatewaying of MDN-requests to other mail systems
11. Example
12. IANA Considerations
12.1. Disposition-Notification-Options header parameter names
12.2. Disposition modifier names
12.3. MDN extension field names
13. Acknowledgments
14. References
14.1. Normative References
14.2. Informative References
15. Appendix A - Changes from RFC 2298
16. Authors' Addresses
17. Full Copyright Statement
18. Intellectual Property
19. Acknowledgement

Google
Web
RFC-Ref
RFC-Ref.org
Frontpage
Global Index
RFC
Sister Sites
Chess-Ref.org
Law-Ref.org
InChI.info
Zvon.org