rfc9122xml2.original.xml   rfc9122.xml 
<?xml version="1.0" encoding="utf-8"?> <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc rfcedstyle="yes"?>
<?rfc subcompact="no"?>
<?rfc symrefs="yes"?>
<rfc ipr="trust200902" category="std" <!DOCTYPE rfc [
docName="draft-ietf-extra-sieve-action-registry-06"> <!ENTITY nbsp "&#160;">
<!ENTITY zwsp "&#8203;">
<!ENTITY nbhy "&#8209;">
<!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
ipr="trust200902"
submissionType="IETF"
category="std"
consensus="true"
docName="draft-ietf-extra-sieve-action-registry-06"
number="9122"
obsoletes=""
updates=""
xml:lang="en"
tocInclude="true"
symRefs="true"
sortRefs="true"
version="3">
<!-- xml2rfc v2v3 conversion 3.17.0 -->
<front> <front>
<title abbrev="IANA registry for Sieve actions"> <title abbrev="IANA Registry for Sieve Actions">
IANA registry for Sieve actions IANA Registry for Sieve Actions
</title> </title>
<seriesInfo name="RFC" value="9122"/>
<author initials="A." surname="Melnikov" fullname="Alexey Melnikov"> <author initials="A." surname="Melnikov" fullname="Alexey Melnikov">
<organization>Isode Ltd</organization> <organization>Isode Ltd</organization>
<address> <address>
<postal> <postal>
<street>14 Castle Mews</street> <street>14 Castle Mews</street>
<city>Hampton</city> <city>Hampton</city>
<region>Middlesex</region> <code>TW12 2NP</code>
<code>TW12 2NP</code> <country>United Kingdom</country>
<country>UK</country> </postal>
</postal> <email>Alexey.Melnikov@isode.com</email>
<email>Alexey.Melnikov@isode.com</email>
</address> </address>
</author> </author>
<author initials="K." surname="Murchison" fullname="Kenneth Murchison"> <author initials="K." surname="Murchison" fullname="Kenneth Murchison">
<organization abbrev="Fastmail">Fastmail US LLC</organization> <organization abbrev="Fastmail">Fastmail US LLC</organization>
<address> <address>
<postal> <postal>
<street>1429 Walnut Street - Suite 1201</street> <extaddr>Suite 1201</extaddr>
<street>1429 Walnut Street</street>
<city>Philadelphia</city> <city>Philadelphia</city>
<region>PA</region> <region>PA</region>
<code>19102</code> <code>19102</code>
<country>USA</country> <country>United States of America</country>
</postal> </postal>
<email>murch@fastmailteam.com</email> <email>murch@fastmailteam.com</email>
</address> </address>
</author> </author>
<date year="2023" month="June" />
<date year="2023" /> <area>art</area>
<workgroup>extra</workgroup>
<keyword>Sieve</keyword> <keyword>Sieve</keyword>
<abstract> <abstract>
<t> <t>
Sieve Email Filtering Language (RFC 5228) is a popular email filtering l anguage The Sieve Email Filtering Language (RFC 5228) is a popular email filteri ng language
used upon final mail delivery. used upon final mail delivery.
This document creates a registry of Sieve (RFC 5228) actions in order to help developers and This document creates a registry for Sieve actions to help developers an d
Sieve extension writers track interactions between different extensions. Sieve extension writers track interactions between different extensions.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section numbered="true" toc="default">
<section title="Introduction"> <name>Introduction</name>
<t> <t>
Sieve Email Filtering Language <xref target="RFC5228"/> is a popular email The Sieve Email Filtering Language <xref target="RFC5228" format="default"
filtering language /> is a popular email filtering language
used upon final mail delivery. Popularity of Sieve resulted in a myriad of used upon final mail delivery. The popularity of Sieve resulted in a myria
Sieve extensions d of Sieve extensions
that can interact with each other in wonderful and complex ways. that can interact with each other in wonderful and complex ways.
There is currently no easy way to find out all actions defined by Sieve ex Currently, there is no easy way to find out all actions defined by Sieve e
tensions published xtensions published
in RFCs, which make it quite difficult for Sieve extension writers and Sie in RFCs, which makes it quite difficult for Sieve extension writers and Si
ve implementation eve implementation
developers to forsee interactions between Sieve actions. developers to foresee interactions between Sieve actions.
</t> </t>
<t> <t>
This document creates a registry of Sieve <xref target="RFC5228"/> actions in order to help developers and This document creates a registry for Sieve <xref target="RFC5228" format=" default"/> actions in order to help developers and
Sieve extension writers track interactions between different extensions. Sieve extension writers track interactions between different extensions.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="IANA Considerations"> <name>IANA Considerations</name>
<section numbered="true" toc="default">
<section title="Sieve Actions Registration Template and Procedure"> <name>Sieve Actions Registration Template and Procedure</name>
<t> <t>
IANA is requested to create a new registry for Sieve actions (see Section IANA has created the "Sieve Actions" registry (see <xref target="RFC5228"
2.9 of <xref target="RFC5228"/> section="2.9" sectionFormat="of"/>
for details on Sieve actions). Registration of both actions specified in I for details on Sieve actions). Registration of actions specified in both R
ETF Stream RFCs FCs
and vendor specific actions is allowed and encouraged. and vendor-specific documentation is allowed and encouraged.
The registration template contains: The registration template contains the following:
</t>
<list style="numbers"> <dl spacing="compact">
<t>name of the action;</t> <dt>Name:</dt><dd>Name of the action</dd>
<t>short description;</t> <dt>Description:</dt><dd>Short description</dd>
<t>references: one or more documents describing the action and <dt>References:</dt><dd>One or more documents describing the action and
any significant updates to its definition any significant updates to its definition (this field
(this field is required for actions described in RFCs and is required for actions described in RFCs and is optional
is optional otherwise);</t> otherwise)</dd>
<t>name(s) of Sieve capabilit(ies) associated with the Sieve <dt>Capabilities:</dt><dd>Name of one or more Sieve capabilities associa
action being registered;</t> ted with the Sieve action being registered</dd>
<t>interactions with other Sieve actions (as described in Section 2.10.1 <dt>Action Interactions:</dt><dd>Interactions with other Sieve actions (
of <xref target="RFC5228"/>), if any;</t> as described in <xref target="RFC5228" sectionFormat="of" section="2.10.1"/>), i
<t>flag specifying whether the action cancels the implicit f any</dd>
keep (see Section 2.10.2 of <xref target="RFC5228"/>);</t> <dt>Cancels Implicit Keep?</dt><dd>Flag specifying whether the action ca
<t>whether or not this action can be used with IMAP events in ncels the implicit keep (see <xref target="RFC5228" sectionFormat="of" section="
Sieve (<xref target="RFC6785"/>);</t> 2.10.2"/>)</dd>
<t>optional comment.</t> <dt>Can Use With IMAP Events?</dt><dd>Whether or not this action can be
</list> used with IMAP events in Sieve <xref target="RFC6785"/></dd>
</t> <dt>Comments:</dt><dd>Optional comment or comments</dd>
</dl>
<t> <t>
Registration procedure for this registry is Expert Review. The registration procedure is Expert Review <xref target="RFC8126"/>.
The Designated Expert only checks that the name of the action being regist The designated expert only checks that the name of the action being regist
ered ered
matches documentation, that the description field is accurate, matches documentation, the description field is accurate,
that the correct documents are referenced and that the list of the correct documents are referenced, and the list of
relevant documents is as complete as possible. relevant documents is as complete as possible.
The Designated Expert can’t reject a registration based on personal dislik The designated expert can't reject a registration because of a personal di
e of slike for
the document defining an action and should always err on the side of regis the document defining an action and should always err on the side of appro
tering, ving the registration,
even if documentation is not complete. even if documentation is not complete.
</t> </t>
<t>The same registration procedure is used to add a new reference
<t> or to change the description field of an existing registration.</t>
Addition of a new reference to an existing registration or change to the d
escription field goes through
the same registration procedure as a new registration.
</t>
</section> </section>
<section anchor="initial-regs" numbered="true" toc="default">
<section title="Initial Sieve Action Registry" anchor="initial-regs"> <name>Initial Sieve Action Registry</name>
<t>The following table is used to initialize the actions <t>The following registrations are used to initialize the "Sieve Actions
registry. Note that when "Action Interactions" cell is empty it means th "
at there is no restriction registry. Note that when the relevant "Action Interactions" entry is mar
on use of the corresponding action with any other action, however implem ked "N/A", it means that there is no restriction
entors still need to read on use of the corresponding action with any other action; however, imple
the corresponding specification(s) to see if there is any surprising beh mentors still need to read
aviour. the one or more corresponding specifications to determine if there are a
Also note that the "Comments" field of the registration template is omit ny surprising behaviors.
ted from this table, Also note that the "Comments" field of the IANA registration template is
as no registration currently have any comment. omitted from these registrations,
as none of them currently have any comments.
</t> </t>
<dl spacing="compact">
<dt>Name:</dt><dd>addheader</dd>
<dt>Description:</dt><dd>Add a header field to the existing message
header</dd>
<dt>References:</dt><dd><xref target="RFC5293" format="default"/></dd>
<dt>Capabilities:</dt><dd>"editheader"</dd>
<dt>Action Interactions:</dt><dd>All subsequent tests and actions apply
to the altered message</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<texttable> <dl spacing="compact">
<ttcol>Name</ttcol> <dt>Name:</dt><dd>addflag</dd>
<ttcol>Description</ttcol> <dt>Description:</dt><dd>Add IMAP flags to a list of IMAP flags that wo
<ttcol>References</ttcol> uld be set on the message if it gets delivered to a mailbox</dd>
<ttcol>Capabilities</ttcol> <dt>References:</dt><dd><xref target="RFC5232" format="default"/> <xref
<ttcol>Action Interactions</ttcol> target="RFC5229" format="default"/></dd>
<ttcol>Cancels Implicit Keep?</ttcol> <dt>Capabilities:</dt><dd>"imap4flags", "variables"</dd>
<ttcol>Can use with IMAP Events?</ttcol> <dt>Action Interactions:</dt><dd>N/A</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<c>addheader</c> <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
<c>Add a header field to the existing message header</c> </dl>
<c><xref target="RFC5293"/></c>
<c>"editheader"</c>
<c>All subsequent tests and actions apply to the altered message</c>
<c>No</c>
<c>Yes</c>
<c>addflag</c>
<c>Add IMAP flags to a list of IMAP flags that would be set on the mes
sage if it gets delivered to a mailbox</c>
<c><xref target="RFC5232"/>, <xref target="RFC5229"/></c>
<c>"imap4flags", "variables"</c>
<c/>
<c>No</c>
<c>Yes</c>
<c>convert</c> <dl spacing="compact">
<c>Convert body parts from one MIME type to another</c> <dt>Name:</dt><dd>convert</dd>
<c><xref target="RFC6558"/></c> <dt>Description:</dt><dd>Convert body parts from one MIME type to anoth
<c>"convert"</c> er</dd>
<c>All subsequent tests and actions apply to the altered message</c> <dt>References:</dt><dd><xref target="RFC6558" format="default"/></dd>
<c>No</c> <dt>Capabilities:</dt><dd>"convert"</dd>
<c>Yes</c> <dt>Action Interactions:</dt><dd>All subsequent tests and actions apply
to the altered message</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>deleteheader</c> <dl spacing="compact">
<c>Remove a header field from the existing message header</c> <dt>Name:</dt><dd>deleteheader</dd>
<c><xref target="RFC5293"/></c> <dt>Description:</dt><dd>Remove a header field from the existing messag
<c>"editheader"</c> e header</dd>
<c>All subsequent tests and actions apply to the altered message</c> <dt>References:</dt><dd><xref target="RFC5293" format="default"/></dd>
<c>No</c> <dt>Capabilities:</dt><dd>"editheader"</dd>
<c>Yes</c> <dt>Action Interactions:</dt><dd>All subsequent tests and actions apply
to the altered message</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>discard</c> <dl spacing="compact">
<c>Silently throw away the message</c> <dt>Name:</dt><dd>discard</dd>
<c><xref target="RFC5228"/></c> <dt>Description:</dt><dd>Silently throw away the message</dd>
<c/> <dt>References:</dt><dd><xref target="RFC5228" format="default"/></dd>
<c/> <dt>Capabilities:</dt><dd>N/A</dd>
<c>Yes</c> <dt>Action Interactions:</dt><dd>N/A</dd>
<c>Yes</c> <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>enclose</c> <dl spacing="compact">
<c>Enclose a message as an attachment to a new message</c> <dt>Name:</dt><dd>enclose</dd>
<c><xref target="RFC5703"/></c> <dt>Description:</dt><dd>Enclose a message as an attachment to a new me
<c>"enclose"</c> ssage</dd>
<c>All subsequent tests and actions, except "redirect" apply <dt>References:</dt><dd><xref target="RFC5703" format="default"/></dd>
to the altered message</c> <dt>Capabilities:</dt><dd>"enclose"</dd>
<c>No</c> <dt>Action Interactions:</dt><dd>All subsequent tests and actions excep
<c>Yes</c> t "redirect" apply to the altered message</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>ereject</c> <dl spacing="compact">
<c>Refuse delivery of the message</c> <dt>Name:</dt><dd>ereject</dd>
<c><xref target="RFC5429"/></c> <dt>Description:</dt><dd>Refuse delivery of the message</dd>
<c>"ereject"</c> <dt>References:</dt><dd><xref target="RFC5429" format="default"/></dd>
<c>Incompatible with "vacation" action. Typically is not permitted wit <dt>Capabilities:</dt><dd>"ereject"</dd>
h actions that cause mail delivery, <dt>Action Interactions:</dt><dd>This action is incompatible with the "
such as "keep", "fileinto", and "redirect".</c> vacation" action. Typically is not permitted with actions that cause mail delive
<c>Yes</c> ry, such as "keep", "fileinto", and "redirect"</dd>
<c>No</c> <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
<dt>Can Use with IMAP Events?</dt><dd>No</dd>
</dl>
<c>extracttext</c> <dl spacing="compact">
<c>Store text of a MIME part into a variable</c> <dt>Name:</dt><dd>extracttext</dd>
<c><xref target="RFC5703"/>, <xref target="RFC5229"/></c> <dt>Description:</dt><dd>Store text of a MIME part into a variable</dd>
<c>"extracttext", "variables"</c> <dt>References:</dt><dd><xref target="RFC5703" format="default"/> <xref
<c/> target="RFC5229" format="default"/></dd>
<c>No</c> <dt>Capabilities:</dt><dd>"extracttext", "variables"</dd>
<c>Yes</c> <dt>Action Interactions:</dt><dd>N/A</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>fileinto</c> <dl spacing="compact">
<c>Deliver the message into the specified mailbox</c> <dt>Name:</dt><dd>fileinto</dd>
<c><xref target="RFC5228"/>, <xref target="RFC3894"/>, <dt>Description:</dt><dd>Deliver the message into the specified mailbox
<xref target="RFC5232"/>, <xref target="RFC5490"/>, </dd>
<xref target="RFC9042"/>, <xref target="RFC8579"/></c> <dt>References:</dt><dd><xref target="RFC5228" format="default"/> <xref
<c>"fileinto", "copy", "imap4flags", "mailbox", "mailboxid", target="RFC3894" format="default"/> <xref target="RFC5232" format="default"/> <
"special-use"</c> xref target="RFC5490" format="default"/> <xref target="RFC9042" format="default"
<c>Use of :copy suppresses cancelation of implicit keep</c> /> <xref target="RFC8579" format="default"/></dd>
<c>Yes</c> <dt>Capabilities:</dt><dd>"fileinto", "copy", "imap4flags", "mailbox",
<c>Yes</c> "mailboxid", "special-use"</dd>
<dt>Action Interactions:</dt><dd>Use of :copy suppresses cancellation o
f implicit keep</dd>
<dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>keep</c> <dl spacing="compact">
<c>File message into the user's main mailbox</c> <dt>Name:</dt><dd>keep</dd>
<c><xref target="RFC5228"/>, <xref target="RFC5232"/></c> <dt>Description:</dt><dd>File the message into the user's main mailbox<
<c>"imap4flags"</c> /dd>
<c/> <dt>References:</dt><dd><xref target="RFC5228" format="default"/> <xref
<c>Yes</c> target="RFC5232" format="default"/></dd>
<c>Yes</c> <dt>Capabilities:</dt><dd>"imap4flags"</dd>
<dt>Action Interactions:</dt><dd>N/A</dd>
<dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>notify</c> <dl spacing="compact">
<c>Send a notification to a user</c> <dt>Name:</dt><dd>notify</dd>
<c><xref target="RFC5435"/>, <xref target="RFC8580"/></c> <dt>Description:</dt><dd>Send a notification to a user</dd>
<c>"enotify", "fcc"</c> <dt>References:</dt><dd><xref target="RFC5435" format="default"/> <xref
<c/> target="RFC8580" format="default"/></dd>
<c>No</c> <dt>Capabilities:</dt><dd>"enotify", "fcc"</dd>
<c>Yes</c> <dt>Action Interactions:</dt><dd>N/A</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>redirect</c> <dl spacing="compact">
<c>Send (forward) the message to another user</c> <dt>Name:</dt><dd>redirect</dd>
<c><xref target="RFC5228"/>, <xref target="RFC3894"/>, <dt>Description:</dt><dd>Send (forward) the message to another user</dd
<xref target="RFC6009"/>, <xref target="RFC6134"/></c> >
<c>"copy", "redirect-dsn", "redirect-deliverby", "extlists"</c> <dt>References:</dt><dd><xref target="RFC5228" format="default"/> <xref
<c>Use of :copy suppresses cancelation of implicit keep</c> target="RFC3894" format="default"/> <xref target="RFC6009" format="default"/> <
<c>Yes</c> xref target="RFC6134" format="default"/></dd>
<c>Yes</c> <dt>Capabilities:</dt><dd>"copy", "redirect-dsn", "redirect-deliverby",
"extlists"</dd>
<dt>Action Interactions:</dt><dd>Use of :copy suppresses cancellation o
f implicit keep</dd>
<dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>reject</c> <dl spacing="compact">
<c>Refuse delivery of the message</c> <dt>Name:</dt><dd>reject</dd>
<c><xref target="RFC5429"/></c> <dt>Description:</dt><dd>Refuse delivery of the message</dd>
<c>"reject"</c> <dt>References:</dt><dd><xref target="RFC5429" format="default"/></dd>
<c>Incompatible with "vacation" action. Typically is not permitted wit <dt>Capabilities:</dt><dd>"reject"</dd>
h actions that cause mail delivery, <dt>Action Interactions:</dt><dd>This action is incompatible with the "
such as "keep", "fileinto", and "redirect".</c> vacation" action. Typically is not permitted with actions that cause mail delive
<c>Yes</c> ry, such as "keep", "fileinto", and "redirect"</dd>
<c>No</c> <dt>Cancels Implicit Keep?</dt><dd>Yes</dd>
<dt>Can Use with IMAP Events?</dt><dd>No</dd>
</dl>
<c>removeflag</c> <dl spacing="compact">
<c>Remove IMAP flags from a list of IMAP flags that would be set on th <dt>Name:</dt><dd>removeflag</dd>
e message if it gets delivered to a mailbox</c> <dt>Description:</dt><dd>Remove IMAP flags from a list of IMAP flags th
<c><xref target="RFC5232"/>, <xref target="RFC5229"/></c> at would be set on the message if it gets delivered to a mailbox</dd>
<c>"imap4flags", "variables"</c> <dt>References:</dt><dd><xref target="RFC5232" format="default"/> <xref
<c/> target="RFC5229" format="default"/></dd>
<c>No</c> <dt>Capabilities:</dt><dd>"imap4flags", "variables"</dd>
<c>Yes</c> <dt>Action Interactions:</dt><dd>N/A</dd>
<dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>replace</c> <dl spacing="compact">
<c>Replace a MIME part</c> <dt>Name:</dt><dd>replace</dd>
<c><xref target="RFC5703"/></c> <dt>Description:</dt><dd>Replace a MIME part</dd>
<c>"replace"</c> <dt>References:</dt><dd><xref target="RFC5703" format="default"/></dd>
<c>All subsequent tests and actions, except "redirect" apply <dt>Capabilities:</dt><dd>"replace"</dd>
to the altered message</c> <dt>Action Interactions:</dt><dd>All subsequent tests and actions excep
<c>No</c> t "redirect" apply to the altered message</dd>
<c>Yes</c> <dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>set</c> <dl spacing="compact">
<c>Store a value in a variable</c> <dt>Name:</dt><dd>set</dd>
<c><xref target="RFC5229"/></c> <dt>Description:</dt><dd>Store a value in a variable</dd>
<c>"variables"</c> <dt>References:</dt><dd><xref target="RFC5229" format="default"/></dd>
<c/> <dt>Capabilities:</dt><dd>"variables"</dd>
<c>No</c> <dt>Action Interactions:</dt><dd>N/A</dd>
<c>Yes</c> <dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>setflag</c> <dl spacing="compact">
<c> <dt>Name:</dt><dd>setflag</dd>
Set IMAP system flags or keywords that would be set on the message if <dt>Description:</dt><dd>Set IMAP system flags or keywords that would b
it gets delivered to a mailbox e set on the message if it gets delivered to a mailbox</dd>
</c> <dt>References:</dt><dd><xref target="RFC5232" format="default"/> <xref
<c><xref target="RFC5232"/>, <xref target="RFC5229"/></c> target="RFC5229" format="default"/></dd>
<c>"imap4flags", "variables"</c> <dt>Capabilities:</dt><dd>"imap4flags", "variables"</dd>
<c/> <dt>Action Interactions:</dt><dd>N/A</dd>
<c>No</c> <dt>Cancels Implicit Keep?</dt><dd>No</dd>
<c>Yes</c> <dt>Can Use with IMAP Events?</dt><dd>Yes</dd>
</dl>
<c>vacation</c> <dl spacing="compact">
<c>Vacation autoresponder</c> <dt>Name:</dt><dd>vacation</dd>
<c><xref target="RFC5230"/>, <xref target="RFC6131"/>, <dt>Description:</dt><dd>Implement a vacation autoresponder</dd>
<xref target="RFC8580"/></c> <dt>References:</dt><dd><xref target="RFC5230" format="default"/> <xref
<c>"vacation", "vacation-seconds", "fcc"</c> target="RFC6131" format="default"/> <xref target="RFC8580" format="default"/></
<c> dd>
Incompatible with "reject" and "ereject" actions. <dt>Capabilities:</dt><dd>"vacation", "vacation-seconds", "fcc"</dd>
</c> <dt>Action Interactions:</dt><dd>This action is incompatible with "reje
<c>No</c> ct" and "ereject" actions</dd>
<c>No</c> <dt>Cancels Implicit Keep?</dt><dd>No</dd>
<dt>Can Use with IMAP Events?</dt><dd>No</dd>
</dl>
</texttable>
</section> </section>
</section> </section>
<section anchor="seccons" numbered="true" toc="default">
<section title="Security Considerations" anchor="seccons"> <name>Security Considerations</name>
<t>
<t> The sole purpose of this document is to create the "Sieve Actions" registr
The sole purpose of this document is to create a new IANA registry, y;
so it doesn't create new security considerations for Sieve implementations therefore, it doesn't create new security considerations for Sieve impleme
. ntations.
</t> </t>
<t> <t>
The new registry should help Sieve extension writers and Sieve implementor s The new registry should help Sieve extension writers and Sieve implementor s
track interactions between different Sieve actions, so it might improve qu ality track interactions between different Sieve actions; therefore, it might im prove the quality
of specifications and implementations, including security aspects. of specifications and implementations, including security aspects.
</t> </t>
<t> <t>
For the Security Considerations of particular actions, see the RFC(s) refe For security considerations related to particular actions, see the one or
renced more RFCs referenced
for that action in the Initial Sieve Action Registry in <xref target="init for the action in question in the "Sieve Actions" registry (<xref target="
ial-regs"/>. initial-regs" format="default"/>).
</t> </t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references>
<name>References</name>
<!--<?rfc include="reference.RFC.2119"?>--> <!-- Keywords, part 1 --> <references>
<?rfc include="reference.RFC.5228"?> <!-- Sieve --> <name>Normative References</name>
<?rfc include="reference.RFC.6785"?> <!-- IMAP Sieve --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.522
<!--<?rfc include="reference.RFC.8174"?>--> <!-- Keywords, part 2 --> 8.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.678
5.xml"/>
</references> </references>
<references>
<references title="Informative References"> <name>Informative References</name>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.389
<?rfc include="reference.RFC.3894"?> <!-- Copy --> 4.xml"/>
<?rfc include="reference.RFC.5229"?> <!-- Variables --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.522
<?rfc include="reference.RFC.5230"?> <!-- Vacation --> 9.xml"/>
<?rfc include="reference.RFC.5232"?> <!-- Imap4Flags --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.523
<?rfc include="reference.RFC.5293"?> <!-- Editheader --> 0.xml"/>
<?rfc include="reference.RFC.5429"?> <!-- [Extended] Reject --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.523
<?rfc include="reference.RFC.5435"?> <!-- Notify --> 2.xml"/>
<?rfc include="reference.RFC.5490"?> <!-- Mailbox --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.529
<?rfc include="reference.RFC.5703"?> <!-- MIME --> 3.xml"/>
<?rfc include="reference.RFC.6009"?> <!-- DSN / Deliver-By --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.542
<?rfc include="reference.RFC.6131"?> <!-- Vacation-Seconds --> 9.xml"/>
<?rfc include="reference.RFC.6134"?> <!-- Externally Stored Lists --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.543
<?rfc include="reference.RFC.6558"?> <!-- Convert --> 5.xml"/>
<?rfc include="reference.RFC.8579"?> <!-- Special-Use --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.549
<?rfc include="reference.RFC.8580"?> <!-- FCC --> 0.xml"/>
<?rfc include="reference.RFC.9042"?> <!-- Mailbox ID --> <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.570
3.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.600
9.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.613
1.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.613
4.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.655
8.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.812
6.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.857
9.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.858
0.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.904
2.xml"/>
</references> </references>
</references>
<section title="Acknowledgements"> <section numbered="true" toc="default">
<name>Acknowledgements</name>
<!--
<t> <t>
Thank you to XXX for comments on this document. Thank you to <contact fullname="Barry Leiba"/>, <contact fullname="Donald Eastlake"/>, <contact fullname="Yoshiro Yoneya"/>, and <contact fullname="Murray Kucherawy"/> for reviews and feedback on this document.
</t> </t>
-->
<t>TBD.</t>
</section> </section>
</back> </back>
</rfc> </rfc>
 End of changes. 57 change blocks. 
310 lines changed or deleted 370 lines changed or added

This html diff was produced by rfcdiff 1.48.