JMAP for Sieve Scripts
draft-murchison-jmap-sieve-01

Document Type Expired Internet-Draft (individual)
Author Kenneth Murchison 
Last updated 2020-09-06 (latest revision 2020-03-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-murchison-jmap-sieve-01.txt

Abstract

This document specifies a data model for managing Sieve scripts on a server using JMAP. Open Issues o How should doing /set{create} with an existing script name be handled? Should it fail or overwrite the existing script? Should the /set request include an 'overwrite' boolean argument? o Should setting isActive==true on a script automatically deactivate any other existing active script, or should the client have to do so itself (as is currently documented)? o Do we want/need a SieveScript/copy method? o Do we want to leverage draft-ietf-jmap-quotas to query Sieve script storage quotas?

Authors

Kenneth Murchison (murch@fastmailteam.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)