% Datatracker information for RFCs on the Legacy Stream is unfortunately often
% incorrect. Please correct the bibtex below based on the information in the
% actual RFC at https://rfc-editor.org/rfc/rfc3503.txt

@misc{rfc3503,
    series =    {Request for Comments},
    number =    3503,
    howpublished =  {RFC 3503},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC3503},
    url =       {https://www.rfc-editor.org/info/rfc3503},
    author =    {Alexey Melnikov},
    title =     {{Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP)}},
    pagetotal = 9,
    year =      2003,
    month =     mar,
    abstract =  {The Message Disposition Notification (MDN) facility defined in RFC 2298 provides a means by which a message can request that message processing by the recipient be acknowledged as well as a format to be used for such acknowledgements. However, it doesn't describe how multiple Mail User Agents (MUAs) should handle the generation of MDNs in an Internet Message Access Protocol (IMAP4) environment. This document describes how to handle MDNs in such an environment and provides guidelines for implementers of IMAP4 that want to add MDN support to their products. {[}STANDARDS-TRACK{]}},
}