I am making the following changes for the last (next) version of Sieve.
I am going to review the document and try and find any last lingering
editorial problems and send the document off for IESG review (uh,
hopefully it's still lingering there, the RFC editor certainly doesn't
seem to have it yet).
Here are the changed sections (aside from typos). If you don't like
them, please let me know. If you like them, please disagree with all
the people that don't like them.
2.4.2.3. Addresses
A number of commands call for email addresses, which are also a subset
of strings. These addresses must be compliant with [IMAIL].
Implementations are required to parse as specified by the "mailbox"
definition in section 6.1, not as "address" is specified in that
section. "Group" syntax MUST NOT be used (if multiple addresses are
requierd, use a string-list). Implementations MUST ensure that the
addresses are syntactically valid, but need not ensure that they
actually identify an email recipient.
2.10.2. Implicit Keep
Previous experience with filtering systems suggests that cases tend to be
missed in scripts. To prevent errors, Sieve has an "implicit keep".
An implicit keep is a keep action (see section 4.4) performed in the
absence of any action that cancels the implicit keep.
An implicit keep is performed if a message is not written to a mailbox,
redirected to a new address, or explicitly thrown out. That is, if a
fileinto, a keep, a redirect, or a discard is performed, an implicit keep is
not.
Some actions may be defined to not cancel the implicit keep. These
actions may not directly effect the delivery of a message, and are
used for their side effects. None of the actions specified in this
document meet that criteria, but extension actions will.