RFC 5423: Internet Message Store Events
In plain English — editorial summary, not part of the RFC
One of the missing features in the existing Internet mail and messaging standards is a facility for server-to-server and server-to- client event notifications related to message store events. As the scope of Internet mail expands to support more diverse media (such as voice mail) and devices (such as cell phones) and to provide rich interactions with other services (such as web portals and legal compliance systems), the need for an interoperable notification system increases. This document attempts to enumerate the types of events that interest real-world consumers of such a system. This document describes events and event parameters that are useful for several cases, including notification to administrative systems and end users. This is not intended as a replacement for a message access facility such as IMAP. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5423
- Published
- March 2009
- Authors
- R. Gellens; C. Newman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5524Extended URLFETCH for Binary and Converted PartsCurrent
May 2009
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5259Internet Message Access Protocol - CONVERT ExtensionCurrent
July 2008
- RFC 5257Internet Message Access Protocol - ANNOTATE ExtensionCurrent
June 2008
- RFC 5255Internet Message Access Protocol InternationalizationCurrent
June 2008
- RFC 5232Sieve Email Filtering: Imap4flags ExtensionCurrent
January 2008
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 6154IMAP LIST Extension for Special-Use MailboxesCurrent
March 2011
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?