Loading...

sieve@ietf.org

[Prev] Thread [Next]  |  [Prev] Date [Next]

Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-03.txt Alexey Melnikov Tue Mar 20 05:00:05 2012

Hi Barry,

On 14/03/2012 15:50, Barry Leiba wrote:
 [...]
On Tue, Mar 6, 2012 at 12:15 PM, Barry Leiba<[EMAIL PROTECTED]>  wrote:
A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Sieve Mail Filtering Language
Working Group of the IETF.

        Title           : Support for Internet Message Access Protocol (IMAP) 
Events in Sieve
...
A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sieve-imap-sieve-03.txt
And another is:
  http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve    (Hi, Alexey!)

This version should be close to ready: I've incorporated all comments
so far except what I note below, and thanks to Stephan for his last
review (quite some time ago now; sorry), which resulted in some
significant improvements.  (I do have two minor updates in my working
copy, one of which replaces the obsolete reference to RFC 4409 with
6409.)

I have added a section, 1.4, noting what's left; please review that.
In that section I have three responses to Stephan (which I think
should be final, and we should be OK),
I think Stephan's issues were addressed.
and two remaining action items
that I'd like to ask Alexey to help with.

The two items are as follows:

   To Do: "Interaction with Metadata": Add text requiring ManageSieve,
I think you already did (by making support for ManageSieve a MUST).
   and giving ManageSieve URI in IMAP capability.
I think you should update the definition of the "imapsieve" IMAP capability to be "imapsieve=<sieveurl-server>", where sieveurl-server is defined in Section 3 of RFC 5804. Also update IMAP examples accordingly.
   To Do: "Interaction with Metadata": Add ManageSieve action to set
   metadata item.
Is this still needed? And did you mean IMAP Sieve script activation for a mailbox?
Alexey, you're much more familiar with ManageSieve than I am.  Can you
come up with text to put into the "Interaction with Metadata" section
(2.3.1) that will resolve these two items?
Some suggestions for the first issue are above. I need a bit more information on the second issue. Also here are some other related changes:

2.3.1.  Interaction with Metadata

   This specifies the mechanism for "activating" a script for a given
   mailbox (or for all mailboxes), but does not specify a mechanism for
   creating, storing, or validating the script.  Implementations MUST
   support ManageSieve [RFC5804], and can use the PUTSCRIPT command to
   store the script without using the SETACTIVE command to activate it.

   In any case, the script name that is specified in the /IMAPSieve/
   Script metadata entry is in a form that depends upon how the server
   handles the storing of Sieve scripts.  Script names used here MUST
   match script names used by METADATA.

I do find the last 2 sentences confusing. How about this instead:

   Script names used in "/IMAPSieve/Script" metadata entries
   are the script names used on the corresponding ManageSieve server.
   If a "/IMAPSieve/Script" metadata entry contains a script name that
   doesn't exist in the ManageSieve server, then no Sieve script
   will be invoked for IMAP Sieve events.

If we can get text for that soon (hey, maybe even by the end of the
week, so I can re-post before the Monday deadline?), we can actually
do a WGLC on this version, and be ready to send it to the IESG after
Paris.

Barry

_______________________________________________
sieve mailing list
[EMAIL PROTECTED]
https://www.ietf.org/mailman/listinfo/sieve