RFC 3656: The Mailbox Update (MUPDATE) Distributed Mailbox Database Protocol
In plain English — editorial summary, not part of the RFC
As the demand for high-performance mail delivery agents increases, it becomes apparent that single-machine solutions are inadequate to the task, both because of capacity limits and that the failure of the single machine means a loss of mail delivery for all users. It is preferable to allow many machines to share the responsibility of mail delivery. The Mailbox Update (MUPDATE) protocol allows a group of Internet Message Access Protocol (IMAP) or Post Office Protocol - Version 3 (POP3) servers to function with a unified mailbox namespace. This document is intended to serve as a reference guide to that protocol.
Document record
- Document ID
- RFC3656
- Published
- December 2003
- Authors
- R. Siemborski
- Status
- EXPERIMENTAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 19
- Also known as
- —
- Updated by:
- RFC 8996
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2595Using TLS with IMAP, POP3 and ACAPUpdated
June 1999
- RFC 3691Internet Message Access Protocol (IMAP) UNSELECT commandCurrent
February 2004
- RFC 6186Use of SRV Records for Locating Email Submission/Access ServicesUpdated
March 2011
- RFC 3807V5.2-User Adaptation Layer (V5UA)Current
June 2004
- RFC 3503Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP)Current
March 2003
- RFC 3502Internet Message Access Protocol (IMAP) - MULTIAPPEND ExtensionUpdated
March 2003
- RFC 3501INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1Obsoleted
March 2003
- RFC 4314IMAP4 Access Control List (ACL) ExtensionCurrent
December 2005
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?