rfc9122v2.txt | rfc9122.txt | |||
---|---|---|---|---|
Internet Engineering Task Force (IETF) A. Melnikov | Internet Engineering Task Force (IETF) A. Melnikov | |||
Request for Comments: 9122 Isode Ltd | Request for Comments: 9122 Isode Ltd | |||
Category: Standards Track K. Murchison | Category: Standards Track K. Murchison | |||
ISSN: 2070-1721 Fastmail | ISSN: 2070-1721 Fastmail | |||
May 2023 | June 2023 | |||
IANA Registry for Sieve Actions | IANA Registry for Sieve Actions | |||
Abstract | Abstract | |||
The Sieve Email Filtering Language (RFC 5228) is a popular email | The Sieve Email Filtering Language (RFC 5228) is a popular email | |||
filtering language used upon final mail delivery. This document | filtering language used upon final mail delivery. This document | |||
creates a registry for Sieve actions to help developers and Sieve | creates a registry for Sieve actions to help developers and Sieve | |||
extension writers track interactions between different extensions. | extension writers track interactions between different extensions. | |||
skipping to change at line 117 ¶ | skipping to change at line 117 ¶ | |||
The same registration procedure is used to add a new reference or to | The same registration procedure is used to add a new reference or to | |||
change the description field of an existing registration. | change the description field of an existing registration. | |||
2.2. Initial Sieve Action Registry | 2.2. Initial Sieve Action Registry | |||
The following registrations are used to initialize the "Sieve | The following registrations are used to initialize the "Sieve | |||
Actions" registry. Note that when the relevant "Action Interactions" | Actions" registry. Note that when the relevant "Action Interactions" | |||
entry is marked "N/A", it means that there is no restriction on use | entry is marked "N/A", it means that there is no restriction on use | |||
of the corresponding action with any other action; however, | of the corresponding action with any other action; however, | |||
implementors still need to read the one or more corresponding | implementors still need to read the one or more corresponding | |||
specifications to determine if there are any surprising behaviours. | specifications to determine if there are any surprising behaviors. | |||
Also note that the "Comments" field of the IANA registration template | Also note that the "Comments" field of the IANA registration template | |||
is omitted from these registrations, as none of them currently have | is omitted from these registrations, as none of them currently have | |||
any comments. | any comments. | |||
Name: addheader | Name: addheader | |||
Description: Add a header field to the existing message header | Description: Add a header field to the existing message header | |||
References: [RFC5293] | References: [RFC5293] | |||
Capabilities: "editheader" | Capabilities: "editheader" | |||
Action Interactions: All subsequent tests and actions apply to the | Action Interactions: All subsequent tests and actions apply to the | |||
altered message | altered message | |||
skipping to change at line 179 ¶ | skipping to change at line 179 ¶ | |||
Capabilities: "enclose" | Capabilities: "enclose" | |||
Action Interactions: All subsequent tests and actions except | Action Interactions: All subsequent tests and actions except | |||
"redirect" apply to the altered message | "redirect" apply to the altered message | |||
Cancels Implicit Keep? No | Cancels Implicit Keep? No | |||
Can Use with IMAP Events? Yes | Can Use with IMAP Events? Yes | |||
Name: ereject | Name: ereject | |||
Description: Refuse delivery of the message | Description: Refuse delivery of the message | |||
References: [RFC5429] | References: [RFC5429] | |||
Capabilities: "ereject" | Capabilities: "ereject" | |||
Action Interactions: Incompatible with "vacation" action. Typically | Action Interactions: This action is incompatible with the "vacation" | |||
is not permitted with actions that cause mail delivery, such as | action. Typically is not permitted with actions that cause mail | |||
"keep", "fileinto", and "redirect" | delivery, such as "keep", "fileinto", and "redirect" | |||
Cancels Implicit Keep? Yes | Cancels Implicit Keep? Yes | |||
Can Use with IMAP Events? No | Can Use with IMAP Events? No | |||
Name: extracttext | Name: extracttext | |||
Description: Store text of a MIME part into a variable | Description: Store text of a MIME part into a variable | |||
References: [RFC5703] [RFC5229] | References: [RFC5703] [RFC5229] | |||
Capabilities: "extracttext", "variables" | Capabilities: "extracttext", "variables" | |||
Action Interactions: N/A | Action Interactions: N/A | |||
Cancels Implicit Keep? No | Cancels Implicit Keep? No | |||
Can Use with IMAP Events? Yes | Can Use with IMAP Events? Yes | |||
Name: fileinto | Name: fileinto | |||
Description: Deliver the message into the specified mailbox | Description: Deliver the message into the specified mailbox | |||
References: [RFC5228] [RFC3894] [RFC5232] [RFC5490] [RFC9042] | References: [RFC5228] [RFC3894] [RFC5232] [RFC5490] [RFC9042] | |||
[RFC8579] | [RFC8579] | |||
Capabilities: "fileinto", "copy", "imap4flags", "mailbox", | Capabilities: "fileinto", "copy", "imap4flags", "mailbox", | |||
"mailboxid", "special-use" | "mailboxid", "special-use" | |||
Action Interactions: Use of :copy suppresses cancelation of implicit | Action Interactions: Use of :copy suppresses cancellation of | |||
keep | implicit keep | |||
Cancels Implicit Keep? Yes | Cancels Implicit Keep? Yes | |||
Can Use with IMAP Events? Yes | Can Use with IMAP Events? Yes | |||
Name: keep | Name: keep | |||
Description: File message into the user's main mailbox | Description: File the message into the user's main mailbox | |||
References: [RFC5228] [RFC5232] | References: [RFC5228] [RFC5232] | |||
Capabilities: "imap4flags" | Capabilities: "imap4flags" | |||
Action Interactions: N/A | Action Interactions: N/A | |||
Cancels Implicit Keep? Yes | Cancels Implicit Keep? Yes | |||
Can Use with IMAP Events? Yes | Can Use with IMAP Events? Yes | |||
Name: notify | Name: notify | |||
Description: Send a notification to a user | Description: Send a notification to a user | |||
References: [RFC5435] [RFC8580] | References: [RFC5435] [RFC8580] | |||
Capabilities: "enotify", "fcc" | Capabilities: "enotify", "fcc" | |||
Action Interactions: N/A | Action Interactions: N/A | |||
Cancels Implicit Keep? No | Cancels Implicit Keep? No | |||
Can Use with IMAP Events? Yes | Can Use with IMAP Events? Yes | |||
Name: redirect | Name: redirect | |||
Description: Send (forward) the message to another user | Description: Send (forward) the message to another user | |||
References: [RFC5228] [RFC3894] [RFC6009] [RFC6134] | References: [RFC5228] [RFC3894] [RFC6009] [RFC6134] | |||
Capabilities: "copy", "redirect-dsn", "redirect-deliverby", | Capabilities: "copy", "redirect-dsn", "redirect-deliverby", | |||
"extlists" | "extlists" | |||
Action Interactions: Use of :copy suppresses cancelation of implicit | Action Interactions: Use of :copy suppresses cancellation of | |||
keep | implicit keep | |||
Cancels Implicit Keep? Yes | Cancels Implicit Keep? Yes | |||
Can Use with IMAP Events? Yes | Can Use with IMAP Events? Yes | |||
Name: reject | Name: reject | |||
Description: Refuse delivery of the message | Description: Refuse delivery of the message | |||
References: [RFC5429] | References: [RFC5429] | |||
Capabilities: "reject" | Capabilities: "reject" | |||
Action Interactions: Incompatible with "vacation" action. Typically | Action Interactions: This action is incompatible with the "vacation" | |||
is not permitted with actions that cause mail delivery, such as | action. Typically is not permitted with actions that cause mail | |||
"keep", "fileinto", and "redirect" | delivery, such as "keep", "fileinto", and "redirect" | |||
Cancels Implicit Keep? Yes | Cancels Implicit Keep? Yes | |||
Can Use with IMAP Events? No | Can Use with IMAP Events? No | |||
Name: removeflag | Name: removeflag | |||
Description: Remove IMAP flags from a list of IMAP flags that would | Description: Remove IMAP flags from a list of IMAP flags that would | |||
be set on the message if it gets delivered to a mailbox | be set on the message if it gets delivered to a mailbox | |||
References: [RFC5232] [RFC5229] | References: [RFC5232] [RFC5229] | |||
Capabilities: "imap4flags", "variables" | Capabilities: "imap4flags", "variables" | |||
Action Interactions: N/A | Action Interactions: N/A | |||
Cancels Implicit Keep? No | Cancels Implicit Keep? No | |||
skipping to change at line 276 ¶ | skipping to change at line 276 ¶ | |||
Name: setflag | Name: setflag | |||
Description: Set IMAP system flags or keywords that would be set on | Description: Set IMAP system flags or keywords that would be set on | |||
the message if it gets delivered to a mailbox | the message if it gets delivered to a mailbox | |||
References: [RFC5232] [RFC5229] | References: [RFC5232] [RFC5229] | |||
Capabilities: "imap4flags", "variables" | Capabilities: "imap4flags", "variables" | |||
Action Interactions: N/A | Action Interactions: N/A | |||
Cancels Implicit Keep? No | Cancels Implicit Keep? No | |||
Can Use with IMAP Events? Yes | Can Use with IMAP Events? Yes | |||
Name: vacation | Name: vacation | |||
Description: Vacation autoresponder | Description: Implement a vacation autoresponder | |||
References: [RFC5230] [RFC6131] [RFC8580] | References: [RFC5230] [RFC6131] [RFC8580] | |||
Capabilities: "vacation", "vacation-seconds", "fcc" | Capabilities: "vacation", "vacation-seconds", "fcc" | |||
Action Interactions: Incompatible with "reject" and "ereject" | Action Interactions: This action is incompatible with "reject" and | |||
actions | "ereject" actions | |||
Cancels Implicit Keep? No | Cancels Implicit Keep? No | |||
Can Use with IMAP Events? No | Can Use with IMAP Events? No | |||
3. Security Considerations | 3. Security Considerations | |||
The sole purpose of this document is to create the "Sieve Actions" | The sole purpose of this document is to create the "Sieve Actions" | |||
registry; therefore, it doesn't create new security considerations | registry; therefore, it doesn't create new security considerations | |||
for Sieve implementations. | for Sieve implementations. | |||
The new registry should help Sieve extension writers and Sieve | The new registry should help Sieve extension writers and Sieve | |||
End of changes. 9 change blocks. | ||||
16 lines changed or deleted | 16 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |