RFC 5436: Sieve Notification Mechanism: mailto
In plain English — editorial summary, not part of the RFC
This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent by electronic mail. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5436
- Published
- January 2009
- Authors
- B. Leiba; M. Haardt
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 12
- Also known as
- —
- Updates:
- RFC 3834
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5435Sieve Email Filtering: Extension for NotificationsUpdated
January 2009
- RFC 5437Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)Current
January 2009
- RFC 5442LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet MailCurrent
March 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5423Internet Message Store EventsCurrent
March 2009
- RFC 5458Security Requirements for the Unidirectional Lightweight Encapsulation (ULE) ProtocolCurrent
March 2009
- RFC 5463Sieve Email Filtering: Ihave ExtensionCurrent
March 2009
- RFC 5465The IMAP NOTIFY ExtensionCurrent
February 2009
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?