Browse Prior Art Database

IMAP4 Multi-Accessed Mailbox Practice (RFC2180)

IP.com Disclosure Number: IPCOM000002739D
Original Publication Date: 1997-Jul-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 14 page(s) / 16K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Gahrns: AUTHOR

Related Documents

10.17487/RFC2180: DOI

Abstract

The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 14% of the total text.

Network Working Group M. Gahrns Request for Comments: 2180 Microsoft Category: Informational July 1997

IMAP4 Multi-Accessed Mailbox Practice

Status of this Memo

This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

1. Abstract

IMAP4[RFC-2060] is rich client/server protocol that allows a client to access and manipulate electronic mail messages on a server. Within the protocol framework, it is possible to have differing results for particular client/server interactions. If a protocol does not allow for this, it is often unduly restrictive.

For example, when multiple clients are accessing a mailbox and one attempts to delete the mailbox, an IMAP4 server may choose to implement a solution based upon server architectural constraints or individual preference.

With this flexibility comes greater client responsibility. It is not sufficient for a client to be written based upon the behavior of a particular IMAP server. Rather the client must be based upon the behavior allowed by the protocol.

By documenting common IMAP4 server practice for the case of simultaneous client access to a mailbox, we hope to ensure the widest amount of inter-operation between IMAP4 clients and servers.

The behavior described in this document reflects the practice of some existing servers or behavior that the consensus of the IMAP mailing list has deemed to be reasonable. The behavior described within this document is believed to be [RFC-2060] compliant. However, this document is not meant to define IMAP4 compliance, nor is it an exhaustive list of valid IMAP4 behavior. [RFC-2060] must always be consulted to determine IMAP4 compliance, especially for server behavior not described within this document.

Gahrns Informational [Page 1]

RFC 2180 IMAP4 Multi-Accessed Mailbox Practice July 1997

2. Conventions used in this document

In examples,"C1:", "C2:" and "C3:" indicate lines sent by 3 different clients (client #1, client #2 and client #3) that are connected to a server. "S1:", "S2:" and "S3:" indicated lines sent by the server to client #1, client #2 and client #3 respectively.

A shared mailbox, is a mailbox that can be used by multiple users.

A multi-accessed mailbox, is a mailbox that has multiple clients simultaneously accessing it.

A client is said to have accessed a mailbox after a successful SELECT or EXAMINE command.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC-2119].

3. Deletion/Renaming of a multi-accessed mailbox

If an external agent or multiple clients are accessing a mailbox, care must be taken when handling the deletion or renaming of the mailbox. Following are some strategies an IMAP server may choose to use when dealing with this situation.

3.1. The server MAY fail the DELETE/RENAME command of a multi-accessed mailbox...

Processing...
Loading...