RFC 5463: Sieve Email Filtering: Ihave Extension
In plain English — editorial summary, not part of the RFC
This document describes the "ihave" extension to the Sieve email filtering language. The "ihave" extension provides a means to write scripts that can take advantage of optional Sieve features but can still run when those optional features are not available. The extension also defines a new error control command intended to be used to report situations where no combination of available extensions satisfies the needs of the script. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5463
- Published
- March 2009
- Authors
- N. Freed
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5784Sieve Email Filtering: Sieves and Display Directives in XMLCurrent
March 2010
- RFC 6009Sieve Email Filtering: Delivery Status Notifications and Deliver-By ExtensionsCurrent
October 2010
- RFC 5260Sieve Email Filtering: Date and Index ExtensionsCurrent
July 2008
- RFC 9422The LIMITS SMTP Service ExtensionCurrent
February 2024
- RFC 5429Sieve Email Filtering: Reject and Extended Reject ExtensionsCurrent
March 2009
- RFC 5550The Internet Email to Support Diverse Service Environments (Lemonade) ProfileCurrent
August 2009
- RFC 5337Internationalized Delivery Status and Disposition NotificationsObsoleted
September 2008
- RFC 4952Overview and Framework for Internationalized EmailObsoleted
July 2007
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?