Oy.
These comments are VERY late, and the document has already gone
through IESG approval. I'll look at them and see what I think we can
address now.
I also have a question for the working group:
In his IESG evaluation review, Robert Sparks has this comment:
<< The environment names live in a global space - other extensions might want to
put a cause into the environment. Would it be worth the pain to scope the name
_this_ extension is adding to this extension ("imapcause" or something like
that)? >>
I think that's a reasonable change, and will change "cause" to
"imapcause", unless there's objection from the WG (and one or two
"That sounds fine." comments would be good).
On Tue, Sep 11, 2012 at 4:51 AM, Stephan Bosch
<stephan(_at_)rename-it(_dot_)nl> wrote:
There is no changelog in the document, so I wondered what changed
That's why &deity made diffs. When you go to the tools page:
http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve
...you can click on "Diff1" if you like strike-out diffs or "Diff2" if
you like side-by-side diffs. Tools are your friends.
#1) The final paragraph of Section 2.1 lists a few IMAP and Sieve
capabilities for which support is required: IMAP "METADATA" and Sieve
"environment". I would expect this Section to list all such dependencies,
but apparently it does not. Section 3.8 adds the Sieve imap4flags extension
as a requirement. Yet, section 4.5 suggests that it is optional again. So
what is it?
We made imap4flags required at a fairly late date, and I didn't get
everything changed consistently. I've fixed that for -09; thanks.
#2) Section 2.2.2 suggests that there is a MULTIAPPEND command for IMAP.
There is no such thing: it is an IMAP capability that extends APPEND to
accept multiple messages at once. I would merge this with the previous
section:
I have added this second paragraph to 2.2.1, eliminated 2.2.2, and
eliminated the other references to a MULTIAPPEND command:
If the IMAP server also supports the IMAP MultiAppend extension
<xref target="RFC3502"/>, the APPEND command can create more
than one message at a time.
In that case, each message creation is considered a separate
event, and any applicable Sieve script is called once for each
message.
I also gave the issue of useless script triggers, i.e. events that are never
of interest for the script involved, some more thought. For example, I would
hate to have my Sieve script executed for each message that I read (added
\Seen flag) while it doesn't do anything useful with that event. Wouldn't it
be useful to have a `/shared/imapsieve/cause' Metadata item that indicates
which causes (the items from Section 7.3.1 in a space-separated list) should
trigger the Sieve script? More detailed control could be used to select
specific flags that are relevant (e.g. in a '/share/imapsieve/changedflags'
Metatada item).
It might, and we considered this, but rejected the complexity. I
don't think this is the time to reconsider it.
Barry
_______________________________________________
sieve mailing list
sieve(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/sieve