Sieve Email Filtering: Delivery Status Notifications and Deliver-By Extensions
RFC 6009

Note: This ballot was opened for revision 09 and is now closed.

Alexey Melnikov (was No Objection, Discuss, Yes) Yes

Comment (2010-05-08)
No email
send info
I think Ned argued successfully against this change, but I haven't checked all email exchange between Ned and Tero:

Section 5 also says that the "bytime" is "the initial integer part of
the delive-by extension", but then comments that deliver-by by-time is
decremented as message passes through the transport infrastructure.
This does not make it clear whether the Sieve filtering system should
also decrement the number while message is waiting to be processed.
I.e. if message was received earlier, but it took some time before the
Sieve email filter could be run on the message, should the "bytime" be
the original time from the smtp MAIL FROM BY= part, or whether it is
decremented.
(This needs to be clarified for both "envelope-deliverby" and "redirect-deliverby", because the answer is likely to be different for them.)

(Jari Arkko) No Objection

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

Comment (2010-04-20 for -)
No email
send info
The following spurious text appears in the IAN section:

    To: iana@iana.org
    Subject: Registration of new Sieve extensions

(Gonzalo Camarillo) No Objection

(Ralph Droms) No Objection

(Lars Eggert) No Objection

(Adrian Farrel) (was Discuss) No Objection

Comment (2010-04-22)
No email
send info
Section 1

For clarity, I suggest...
s/users may not be allowed/users might not be allowed/
or
s/users may not be allowed/users are not allowed/

---

Section 1
s/sieve/Sieve/

---

Section 4
OLD
   None of the new envelope
   parts defined here have address syntax
NEW
   None of the new envelope
   parts defined here has address syntax

(David Harrington) No Objection

(Russ Housley) No Objection

Comment (2010-04-21 for -)
No email
send info
  Please consider the Gen-ART Review comments by Spencer Dawkins:

  Section 7, redirect-deliverby extension, says:
  >
  > :bytime specifies the number of seconds within which the message
  > should be delivered. :bymode specifies whether a notification should
  > be sent or the message simply returned if the time limit is exceeded.
  > The default is "return" if :bymode is not specified.  See The
  > semantics of delivery time limits are specified and discussed at
  > length in [RFC2852].
  >
  Spencer said: I'm not sure if this is a cut-and-paste error or if you
  really meant to say something that got left out, but someone smarter
  than I am needs to look at the "See The" here.

(Tim Polk) No Objection

Comment (2010-04-21 for -)
No email
send info
Section 5.

The first paragraph states:

   The "envelope-deliverby" extension does not define any new tests or
   actions, rather, it adds three values to the list of possible (case-
   insensitive) envelope-part strings defined in Section 5.4 of
   [RFC5228].

but the text following the list of envelope-part strings states:

   All of these tests fail unconditionally if ...

perhaps the following substitution would be clearer:

OLD
   All of these tests fail unconditionally if the BY SMTP MAIL FROM
   parameter does not exist for the current message or recipient.
NEW
   The envelope test  fails unconditionally for each of these envelope-part strings
   if the BY SMTP MAIL FROM parameter does not exist for the current message or recipient.

(Dan Romascanu) No Objection

(Peter Saint-Andre) (was Discuss, No Objection) No Objection

(Robert Sparks) No Objection

(Sean Turner) No Objection

Comment (2010-04-22 for -)
No email
send info
I support Alexey's DISCUSS position.