UpdatedPROPOSED STANDARDIETF stream

RFC 5804: A Protocol for Remotely Managing Sieve Scripts

Still current, but amended. Parts of this document are changed or extended by RFC 7817, RFC 8553. Read both.

In plain English — editorial summary, not part of the RFC

Sieve scripts allow users to filter incoming email. Message stores are commonly sealed servers so users cannot log into them, yet users must be able to update their scripts on them. This document describes a protocol "ManageSieve" for securely managing Sieve scripts on a remote server. This protocol allows a user to have multiple scripts, and also alerts a user to syntactically flawed scripts. [STANDARDS TRACK]

Document record

Document ID
RFC5804
Published
July 2010
Authors
A. Melnikov; T. Martin
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
49
Also known as
Updated by:
RFC 7817, RFC 8553

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/5804-a-protocol-for-remotely-managing-sieve-scripts