Browse Prior Art Database

Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP) (RFC3503)

IP.com Disclosure Number: IPCOM000011812D
Original Publication Date: 2003-Mar-01
Included in the Prior Art Database: 2003-Mar-18
Document File: 10 page(s) / 17K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Melnikov: AUTHOR

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 17% of the total text.

Network Working Group                                        A. Melnikov

Request for Comments: 3503                 ACI Worldwide/MessagingDirect

Category: Standards Track                                     March 2003

          Message Disposition Notification (MDN) profile for

                Internet Message Access Protocol (IMAP)

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

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.

Melnikov                    Standards Track                     [Page 1]

RFC 3503                  MDN profile for IMAP                March 2003

Table of Contents

   1.  Conventions Used in this Document.............................  2

   2.  Introduction and Overview.....................................  2

   3.  Client behavior...............................................  3

       3.1. Client behavior when receiving a message.................  5

       3.2. Client behavior when copying a message...................  5

       3.3. Client behavior when sending a message...................  5

       3.4. Client behavior when saving a temporary message..........  5

   4.  Server behavior...............................................  5

       4.1. Server that supports arbitrary keywords..................  5

       4.2. Server that supports only $MDNSent keyword...............  5

       4.3. Interaction with IMAP ACL extension......................  6

   5.  Examples......................................................  6

   6.  Security Considerations.......................................  7

   7.  Formal Syntax.................................................  7

   8.  Acknowledgments...............................................  7

   9.  Normative References..........................................  8

   10. Author's Address..............