-
Notifications
You must be signed in to change notification settings - Fork 0
/
draft-ietf-extra-sieve-snooze.xml
712 lines (666 loc) · 30.7 KB
/
draft-ietf-extra-sieve-snooze.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
<!ENTITY nbsp " ">
<!ENTITY zwsp "​">
<!ENTITY nbhy "‑">
<!ENTITY wj "⁠">
]>
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc compact="yes"?>
<?rfc strict="yes"?>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std"
ipr="trust200902"
docName="draft-ietf-extra-sieve-snooze-07" obsoletes=""
submissionType="IETF" consensus="true" xml:lang="en"
tocInclude="true" symRefs="true" sortRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 3.16.0 -->
<front>
<title abbrev="Sieve Snooze">Sieve Email Filtering: Snooze Extension</title>
<seriesInfo name="Internet-Draft" value="draft-ietf-extra-sieve-snooze-07"/>
<author initials="K." surname="Murchison" fullname="Kenneth Murchison">
<organization abbrev="Fastmail">Fastmail US LLC</organization>
<address>
<postal>
<street>1429 Walnut Street - Suite 1201</street>
<city>Philadelphia</city>
<region>PA</region>
<code>19102</code>
<country>USA</country>
</postal>
<email>murch@fastmailteam.com</email>
</address>
</author>
<author initials="R." surname="Signes" fullname="Ricardo Signes">
<organization abbrev="Fastmail">Fastmail US LLC</organization>
<address>
<postal>
<street>1429 Walnut Street - Suite 1201</street>
<city>Philadelphia</city>
<region>PA</region>
<code>19102</code>
<country>USA</country>
</postal>
<email>rjbs@fastmailteam.com</email>
</address>
</author>
<author initials="N." surname="Jenkins" fullname="Neil Jenkins">
<organization abbrev="Fastmail">Fastmail Pty Ltd</organization>
<address>
<postal>
<street>Level 2, 114 William Street</street>
<city>Melbourne</city>
<region>VIC</region>
<code>3000</code>
<country>Australia</country>
</postal>
<email>neilj@fastmailteam.com</email>
</address>
</author>
<date/>
<area>ART</area>
<workgroup>EXTRA</workgroup>
<keyword>Sieve</keyword>
<abstract>
<t>This document describes the "snooze" extension to the Sieve email
filtering language.
The "snooze" extension gives Sieve the ability to postpone the
delivery of an incoming email message into a target mailbox
until a later point in time.</t>
</abstract>
<!--
<note title="Open Issues">
<t>
<list style="symbols">
</list>
</t>
</note>
-->
</front>
<middle>
<section numbered="true" toc="default">
<name>Introduction</name>
<t>Users are not always ready, willing, or able to read and
respond to email messages at the time of their arrival.
Sometimes it is desirable to have messages appear in a mailbox
at a more convenient time for the user to act upon them.</t>
<t>This document defines an extension to the
<xref target="RFC5228" format="default">Sieve language</xref> that enables
scripts to postpone the delivery of a message into a target
mailbox until a later point in time.</t>
</section>
<section numbered="true" toc="default">
<name>Conventions Used in This Document</name>
<t>Conventions for notations are as in
<xref target="RFC5228" section="1.1"/>,
including use of the "Usage:" label for the
definition of action and tagged arguments syntax.</t>
<t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
"MAY", and "OPTIONAL" in this document are to be interpreted as
described in BCP 14
<xref target="RFC2119"/> <xref target="RFC8174"/>
when, and only when, they appear in all capitals, as shown
here.</t>
</section> <!-- Intro -->
<section anchor="capability" numbered="true" toc="default">
<name>Capability Identifier</name>
<t>Sieve implementations that support this extension have
an identifier of "snooze" for use with the capability mechanism.</t>
</section>
<section anchor="snooze" numbered="true" toc="default">
<name>Snooze Action</name>
<artwork name="" type="" align="left" alt=""><![CDATA[
Usage: snooze *AWAKEN-OPTIONS <times: string-list>
]]></artwork>
<t keepWithNext="true">The AWAKEN-OPTIONS argument is defined here
in <xref target="RFC5234" format="default">ABNF</xref> syntax
so that it can be modified by other extensions.</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
AWAKEN-OPTIONS = MAILBOX / WEEKDAYS / TZID
; each option MUST NOT appear more than once
; however, per Section 2.6.2 of RFC 5228,
; the tagged arguments in AWAKEN-OPTIONS
; may appear in any order
MAILBOX = ":mailbox" string
WEEKDAYS = ":weekdays" string-list
TZID = ":tzid" string
]]></artwork>
<t>The "snooze" action cancels the implicit keep and postpones
delivery of the message into the specified mailbox at a later
point in time.</t>
<t>The snooze action is semantically equivalent to a delayed
fileinto action (see <xref target="RFC5228" section="4.1"/>).
The arguments of the snooze action specify when, where, and
how the awakened message will be filed.</t>
<t>The process of actually snoozing the message is
implementation specific and outside the scope of this document.
However, implementations MUST ensure that the intended recipient
has access to the message while snoozed.</t>
<t>To that end, a Sieve interpreter could implement the snooze action by
delivering the message to a special "snoozed" mailbox within its
mailstore.
<xref target="RFC9051">IMAP</xref> and <xref target="RFC8621">JMAP</xref>
servers utilizing such a mailbox MUST apply the
<xref target="snoozed">"Snoozed"</xref> attribute to it.
The message will reside in this special mailbox until the
prescribed awaken time at which it will be moved into the
specified target mailbox.</t>
<section anchor="mailboxarg" numbered="true" toc="default">
<name>Mailbox Argument</name>
<t>The optional :mailbox argument is used to specify the target
mailbox that the message will be filed into when it is awakened.
It is equivalent to the mailbox argument of the fileinto
action (see <xref target="RFC5228" section="4.1"/>).</t>
<t>If :mailbox is omitted, or if the specified mailbox doesn't
exist at the time of awakening, the message will be filed
into the user's main mailbox.
For instance, in an implementation where an IMAP server is
running scripts on behalf of the user at time of delivery,
the user's "INBOX" would be the implicit target for
awakening messages.</t>
</section>
<section anchor="weekdays" numbered="true" toc="default">
<name>Weekdays Argument</name>
<t>The optional :weekdays argument specifies the set of days
on which the specified set of awakening times apply.
Each day of the week is expressed as an integer between
"0" and "6". "0" is Sunday, "1" is Monday, etc.
This syntax matches that of the "weekday" date-part argument
to the date test extension (see
<xref target="RFC5260" section="4.2"/>).</t>
<t>If :weekdays is omitted, the set of awakening times applies
to every day of the week.</t>
</section>
<section anchor="times" numbered="true" toc="default">
<name>Times and TZID Arguments</name>
<t>The required times argument, along with the optional :tzid
argument, are used to specify when a snoozed message will be
awakened.
Each time is specified in "hh:mm:ss" format and is interpreted
as the local time in the time zone specified by the :tzid
argument.</t>
<t>The value of the :tzid argument MUST be a time zone
identifier from the
<xref target="tzdb">IANA Time Zone Database</xref>.
If :tzid is omitted, the time zone of the Sieve
interpreter is used.
</t>
<t>The combination of the weekdays and times form a
chronological list of awaken times. When a message is
snoozed, it is assigned the next future awaken time in the
list. If a message is snoozed on a day with no awaken times,
or after the last awaken time on a given day,
the first awaken time on the next available day is used.
</t>
<t>If the local time in the specified time zone occurs more
than once (daylight saving to standard time transition), the
first occurrence of the specified time value is used.
If the local time in the specified time zone does not occur
(standard to daylight saving time transition), the specified
time value is interpreted using the UTC offset prior to the
transition.</t>
<section numbered="true" toc="default">
<name>Awaken Times Examples</name>
<t>The following examples show, given the specified snooze
action and a set of message arrival times, the corresponding
times at which the message would be awakened and filed.</t>
<t keepWithNext="true">The following example shows awaken times rolling
into the next day or week.
Note that 2020-07-30 falls on a Thursday.</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
require "snooze";
snooze :weekdays ["1", "3", "5", "2", "4"]
:tzid "Australia/Melbourne" ["12:00:00",
"08:00:00", "16:00:00"];
]]></artwork>
<table align="center">
<thead>
<tr>
<th align="center">Arrival (UTC)</th>
<th align="center">Arrival (Melbourne)</th>
<th align="center">Awaken (Melbourne)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center">2020-07-30T00:00:00Z</td>
<td align="center">--07-30T10:00:00+10</td>
<td align="center">--07-30T12:00:00+10</td>
</tr>
<tr>
<td align="center">2020-07-30T04:00:00Z</td>
<td align="center">--07-30T14:00:00+10</td>
<td align="center">--07-30T16:00:00+10</td>
</tr>
<tr>
<td align="center">2020-07-30T08:00:00Z</td>
<td align="center">--07-30T18:00:00+10</td>
<td align="center">--07-31T08:00:00+10</td>
</tr>
<tr>
<td align="center">2020-07-31T12:00:00Z</td>
<td align="center">--07-31T22:00:00+10</td>
<td align="center">--08-03T08:00:00+10</td>
</tr>
<tr>
<td align="center">2020-08-01T16:00:00Z</td>
<td align="center">--08-02T02:00:00+10</td>
<td align="center">--08-03T08:00:00+10</td>
</tr>
</tbody>
</table>
<t keepWithNext="true">The following example shows awaken times falling
before, during, and after a daylight saving to standard
time transition.
Note that the transition occurs at 2020-11-01T02:00:00-04.
</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
require "snooze";
snooze :tzid "America/New_York" "01:30:00";
]]></artwork>
<table align="center">
<thead>
<tr>
<th align="center">Arrival (UTC)</th>
<th align="center">Arrival (New York)</th>
<th align="center">Awaken (New York)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center">2020-11-01T05:00:00Z</td>
<td align="center">--11-01T01:00:00-04</td>
<td align="center">--11-01T01:30:00-04</td>
</tr>
<tr>
<td align="center">2020-11-01T06:00:00Z</td>
<td align="center">--11-01T01:00:00-05</td>
<td align="center">--11-02T01:30:00-05</td>
</tr>
<tr>
<td align="center">2020-11-01T07:00:00Z</td>
<td align="center">--11-01T02:00:00-05</td>
<td align="center">--11-02T01:30:00-05</td>
</tr>
</tbody>
</table>
<t keepWithNext="true">The following example shows awaken times falling
before, during, and after a standard to daylight saving
time transition.
Note that the transition occurs at 2021-03-14T02:00:00-05.
</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
require "snooze";
snooze :tzid "America/New_York" "02:30:00";
]]></artwork>
<table align="center">
<thead>
<tr>
<th align="center">Arrival (UTC)</th>
<th align="center">Arrival (New York)</th>
<th align="center">Awaken (New York)</th>
</tr>
</thead>
<tbody>
<tr>
<td align="center">2021-03-13T06:30:00Z</td>
<td align="center">--03-13T01:30:00-05</td>
<td align="center">--03-13T02:30:00-05</td>
</tr>
<tr>
<td align="center">2021-03-14T06:30:00Z</td>
<td align="center">--03-14T01:30:00-05</td>
<td align="center">--03-14T03:30:00-04</td>
</tr>
<tr>
<td align="center">2021-03-14T07:30:00Z</td>
<td align="center">--03-14T03:30:00-04</td>
<td align="center">--03-15T02:30:00-04</td>
</tr>
</tbody>
</table>
</section>
</section>
<section anchor="extensions" numbered="true" toc="default">
<name>Interaction with Extensions to the Fileinto Action</name>
<t>Some tagged arguments defined in extensions to the fileinto
action can be used together with the snooze action.
The sections below describe these interactions.
Tagged arguments in future extensions to the fileinto action
need to describe their interaction with the snooze extension,
if any.</t>
<t>When any fileinto extension arguments are used with the
snooze extension, the corresponding extension MUST be enabled,
and the arguments are defined to have the same syntax,
semantics, and treatment as they do with the fileinto action.</t>
<section anchor="imap4flags" numbered="true" toc="default">
<name>Imap4flags Extension</name>
<t>When the <xref target="RFC5232">"imap4flags"</xref>
extension is enabled in a script, two additional tagged
arguments are added to "snooze" that allow manipulating the
set of flags on a snoozed message.</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
AWAKEN-OPTIONS /= ADDFLAGS / REMOVEFLAGS
ADDFLAGS = ":addflags" string-list
REMOVEFLAGS = ":removeflags" string-list
]]></artwork>
<t>The optional :addflags and :removeflags arguments are used
to specify which <xref target="RFC9051">IMAP</xref> flags
should be added to and/or removed from the set of IMAP flags
present on the snoozed message at the time of awakening.
Note the set of IMAP flags present at the time of awakening may
be the empty set.</t>
<t>If the "setflag" and/or "addflag" actions have been used to
store IMAP flags in the imap4flags internal variable,
the Sieve interpreter MUST use the current value of the
internal variable as the set of flags to associate with the
message when storing it into the "snoozed" mailbox.</t>
<t>This document doesn't dictate how the Sieve interpreter
will set the IMAP flags.
In particular, the Sieve interpreter may work as an IMAP
client or may have direct access to the mailstore.</t>
<t>The general requirements for flag handling specified in
<xref target="RFC5232" section="2"/> MUST be followed.</t>
<section numbered="true" toc="default">
<name>Example</name>
<t>The following example leverages the
<xref target="RFC5260">Date</xref>,
<xref target="RFC5231">Relational</xref>, and
<xref target="RFC5232">Imap4flags</xref> extensions
to snooze messages received after business hours until the
following work day. Note that the message is marked as
important when it is snoozed, and will be marked as unread
when it is awakened.</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
require ["snooze", "imap4flags", "date", "relational"];
if anyof(header :is "from" "boss@example.com",
currentdate :is "weekday" "0",
currentdate :is "weekday" "6",
currentdate :value "ge" "hour" "17") {
setflag "\\Important";
snooze :removeflags "\\Seen"
:weekdays ["1". "2", "3", "4", "5"]
:tzid "American/New_York", "09:00";
}
]]></artwork>
</section>
</section>
<section anchor="mailboxext" numbered="true" toc="default">
<name>Mailbox Extension</name>
<t>This document extends the definition of the
<xref target="RFC5490">":create"</xref> tagged argument so
that it can be used with the snooze action.</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
AWAKEN-OPTIONS /= CREATE
CREATE = ":create"
; MUST NOT be appear unless MAILBOX also appears
]]></artwork>
<t>If the optional ":create" argument is specified with
snooze, it instructs the Sieve interpreter to create the
target mailbox, if needed, before attempting to file the
awakened message into the target mailbox.</t>
</section>
<section anchor="specialuse" numbered="true" toc="default">
<name>Special-Use Extension</name>
<t>This document extends the definition of the
<xref target="RFC8579">":specialuse"</xref> tagged argument
so that it can be used with the snooze action.</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
AWAKEN-OPTIONS /= SPECIAL-USE
SPECIAL-USE = ":specialuse" string
]]></artwork>
<t>If the optional ":specialuse" argument is specified with
snooze, it instructs the Sieve interpreter to check whether
a mailbox exists with the specific special-use flag assigned
to it. If such a mailbox exists, the awakened message is filed
into the special-use mailbox. Otherwise, the awakened message
is filed into the target mailbox.</t>
<t>If both the optional ":specialuse" and ":create"
arguments are specified with snooze, the Sieve interpreter
is instructed to create the target mailbox per
<xref target="RFC8579" section="4.1"/>, if needed.</t>
</section>
<section anchor="mailboxid" numbered="true" toc="default">
<name>MailboxID Extension</name>
<t>This document extends the definition of the
<xref target="RFC9042">":mailboxid"</xref>
tagged argument so that it can be used with the snooze action.</t>
<artwork name="" type="" align="left" alt=""><![CDATA[
AWAKEN-OPTIONS /= MAILBOXID
MAILBOXID = ":mailboxid" string
]]></artwork>
<t>If the optional ":mailboxid" argument is specified with
snooze, it instructs the Sieve interpreter to check whether
a mailbox exists in the user's
<xref target="RFC2342">personal namespace </xref> with the
specified <xref target="RFC8474">MAILBOXID</xref>.
If such a mailbox exists, the awakened message is filed
into that mailbox. Otherwise, the awakened message
is filed into the target mailbox.</t>
<t>It is an error to specify both ":mailboxid" and
":specialuse" in the same snooze action.</t>
</section>
</section> <!-- extensions -->
</section> <!-- snooze -->
<section anchor="impl" numbered="true" toc="default">
<name>Implementation Status</name>
<t>< RFC Editor: before publication please remove this section
and the reference to <xref target="RFC7942"/> ></t>
<t>This section records the status of known implementations of
the protocol defined by this specification at the time of
posting of this Internet-Draft, and is based on a proposal
described in <xref target="RFC7942"/>. The
description of implementations in this section is intended to
assist the IETF in its decision processes in progressing
drafts to RFCs. Please note that the listing of any
individual implementation here does not imply endorsement by
the IETF. Furthermore, no effort has been spent to verify the
information presented here that was supplied by IETF
contributors. This is not intended as, and must not be
construed to be, a catalog of available implementations or
their features. Readers are advised to note that other
implementations may exist.</t>
<t>According to <xref target="RFC7942"/>,
"this will allow reviewers and working groups to assign due
consideration to documents that have the benefit of running
code, which may serve as evidence of valuable
experimentation and feedback that have made the implemented
protocols more mature. It is up to the individual working
groups to use this information as they see fit".</t>
<section anchor="cyrus" toc="exclude" numbered="true">
<name>Cyrus Server</name>
<t>The open source
<eref target="http://www.cyrusimap.org/">Cyrus Server</eref> project
is a highly scalable enterprise mail system which supports
Sieve email filtering at the point of final delivery. This
production level Sieve implementation supports all of the
requirements described in this document. This implementation
is freely distributable under a BSD style license from
<eref target="http://www.cmu.edu/computing/">
Computing Services at Carnegie Mellon University</eref>.</t>
</section>
</section> <!-- Implementations -->
<section anchor="security" numbered="true" toc="default">
<name>Security Considerations</name>
<t>Security considerations are discussed in
<xref target="RFC5228"/>, <xref target="RFC5232"/>,
<xref target="RFC8579"/>, and <xref target="RFC9042"/>.
</t>
<t>It is believed that this extension doesn't introduce any
additional security concerns.</t>
</section>
<section anchor="privacy" numbered="true" toc="default">
<name>Privacy Considerations</name>
<t>It is believed that this extension doesn't introduce any
privacy considerations beyond those in <xref target="RFC5228"/>.</t>
</section>
<section numbered="true" toc="default">
<name>IANA Considerations</name>
<section numbered="true" toc="default">
<name>Registration of Sieve Extension</name>
<t>This document defines the following new Sieve extension
to be added to the registry defined in
<xref target="RFC5228" section="6.2"/> and located here:
<eref target="https://www.iana.org/assignments/sieve-extensions/sieve-extensions.xhtml#sieve-extensions"/>
</t>
<t>IANA are requested to add a capability to the Sieve
Extensions registry:
</t>
<ul empty="true" spacing="normal">
<li>To: iana@iana.org</li>
<li>Subject: Registration of new Sieve extension</li>
<li>Capability name: snooze</li>
<li>Description: Adds the "snooze" action command to
postpone delivery of a message into a target mailbox until
a later point in time.</li>
<li>RFC number: RFC XXXX</li>
<li>Contact address: The Sieve discussion list
<sieve@ietf.org></li>
</ul>
</section>
<section numbered="true" toc="default">
<name>Registration of Sieve Action</name>
<t>This document defines the following new Sieve action
to be added to the registry defined in
<xref target="I-D.ietf-extra-sieve-action-registry" section="3.1"/>.
</t>
<t>IANA are requested to add an action to the Sieve Action
registry:
</t>
<ul empty="true" spacing="normal">
<li>Name: snooze</li>
<li>Description: Postpone delivery of a message into a
target mailbox until a later point in time.</li>
<li>References: RFC XXXX, <xref target="RFC5232"/>,
<xref target="RFC5490"/>, <xref target="RFC8579"/>,
<xref target="RFC9042"/></li>
<li>Capabilities: "snooze", "imap4flags", "mailbox",
"special-use", "mailboxid".</li>
<li>Interactions: Is not compatible with the reject or
ereject actions.</li>
<li>Cancels Implicit Keep?: Y</li>
<li>Use with IMAP Events?: Y</li>
<li>Comments: Requires a special "snoozed" mailbox in the
mailstore.</li>
</ul>
</section>
<section anchor="snoozed" numbered="true" toc="default">
<name>Registration of IMAP Mailbox Name Attribute</name>
<t>This document defines the following new IMAP mailbox name
attribute to be added to the registry defined in
<xref target="RFC8457" section="6.2"/> and located here:
<eref target="https://www.iana.org/assignments/imap-mailbox-name-attributes/imap-mailbox-name-attributes.xhtml#imap-mailbox-name-attributes"/>
</t>
<t>IANA are requested to add an attribute to the IMAP Mailbox
Name Attribute registry:
</t>
<ul empty="true" spacing="normal">
<li>To: iana@iana.org</li>
<li>Subject: Registration of new IMAP Mailbox Name Attribute</li>
<li>Attribute name: Snoozed</li>
<li>Description: Messages that have been snoozed.</li>
<li>Reference: RFC XXXX</li>
</ul>
</section>
</section>
<!-- IANA -->
<section numbered="true" toc="default">
<name>Acknowledgments</name>
<t>The authors would like to thank the following individuals for
contributing their ideas and support for writing this
specification: Ned Freed, Barry Leiba, Alexey Melnikov, and Pete
Resnick.</t>
</section>
</middle>
<back>
<references>
<name>References</name>
<references>
<name>Normative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.2342.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9051.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5228.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5232.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5490.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8474.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8579.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8457.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.9042.xml"/>
<xi:include href="https://datatracker.ietf.org/doc/bibxml3/draft-ietf-extra-sieve-action-registry.xml"/>
<reference anchor="tzdb" target="https://www.iana.org/time-zones">
<front>
<title>Time Zone Database</title>
<author>
<organization>Internet Assigned Numbers Authority</organization>
</author>
<date/>
</front>
</reference>
</references>
<references>
<name>Informative References</name>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5260.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.5231.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7942.xml"/>
<xi:include href="https://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.8621.xml"/>
</references>
</references>
<section numbered="true" toc="default">
<name>Change History (To be removed by RFC Editor before publication)</name>
<t>Changes since draft-ietf-extra-sieve-snooze-06:
</t>
<ul spacing="normal">
<li>Don't use normative language when describing possible
"snoozed" mailbox implementation.</li>
<li>Miscellaneous editorial changes.</li>
</ul>
<t>Changes since draft-ietf-extra-sieve-snooze-05:
</t>
<ul spacing="normal">
<li>Don't require implementations to use a "snoozed" mailbox.</li>
</ul>
<t>Changes since draft-ietf-extra-sieve-snooze-04:
</t>
<ul spacing="normal">
<li>Miscellaneous editorial changes.</li>
</ul>
<t>Changes since draft-ietf-extra-sieve-snooze-03:
</t>
<ul spacing="normal">
<li>Added "snooze" to the Sieve Actions Registry.</li>
</ul>
<t>Changes since draft-ietf-extra-sieve-snooze-02:
</t>
<ul spacing="normal">
<li>Updated :mailboxid reference to RFC9042.</li>
<li>Added an informative reference to RFC8621.</li>
<li>Miscellaneous editorial changes.</li>
</ul>
<t>Changes since draft-ietf-extra-sieve-snooze-01:
</t>
<ul spacing="normal">
<li>Miscellaneous editorial changes.</li>
</ul>
<t>Changes since draft-ietf-extra-sieve-snooze-00:
</t>
<ul spacing="normal">
<li>Disallow both :mailboxid and :specialuse in the same snooze
action.</li>
<li>Updated :mailboxid reference to
draft-ietf-extra-sieve-mailboxid</li>
<li>Specified that snooze cancels implicit keep.</li>
<li>Specified that implementations MUST use a "snoozed" mailbox.</li>
<li>Added registration of \Snoozed Special-Use Attribute.</li>
<li>Added example of manipulating IMAP flags at both snooze
time and awaken time.</li>
<li>Miscellaneous editorial changes.</li>
</ul>
</section>
</back>
</rfc>