metasystema.org
CurrentPROPOSED STANDARDLegacy stream

RFC 3503: Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP)

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC3503
Published
March 2003
Authors
A. Melnikov
Status
PROPOSED STANDARD
Stream
Legacy
Area
—
Pages
9
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/3503-message-disposition-notification-mdn-profile-for-internet-message-access-protoco