RFC 5435: Sieve Email Filtering: Extension for Notifications
In plain English — editorial summary, not part of the RFC
Users go to great lengths to be notified as quickly as possible that they have received new mail. Most of these methods involve polling to check for new messages periodically. A push method handled by the final delivery agent gives users quicker notifications and saves server resources. This document does not specify the notification method, but it is expected that using existing instant messaging infrastructure such as Extensible Messaging and Presence Protocol (XMPP), or Global System for Mobile Communications (GSM) Short Message Service (SMS) messages will be popular. This document describes an extension to the Sieve mail filtering language that allows users to give specific rules for how and when notifications should be sent. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5435
- Published
- January 2009
- Authors
- A. Melnikov; B. Leiba; W. Segmuller; T. Martin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 17
- Also known as
- —
- Updated by:
- RFC 8580
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 5436Sieve Notification Mechanism: mailtoCurrent
January 2009
- RFC 5437Sieve Notification Mechanism: Extensible Messaging and Presence Protocol (XMPP)Current
January 2009
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5442LEMONADE Architecture - Supporting Open Mobile Alliance (OMA) Mobile Email (MEM) Using Internet MailCurrent
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?