From internet-drafts@ietf.org Mon Sep 10 10:27:44 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9AD21F84CD; Mon, 10 Sep 2012 10:27:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.513 X-Spam-Level: X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fy9r-mVLFFeq; Mon, 10 Sep 2012 10:27:43 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92C3221F84E2; Mon, 10 Sep 2012 10:27:43 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20120910172743.29435.99209.idtracker@ietfa.amsl.com> Date: Mon, 10 Sep 2012 10:27:43 -0700 Cc: sieve@ietf.org Subject: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-07.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 17:27:44 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Sieve Mail Filtering Language Working Gro= up of the IETF. Title : Support for Internet Message Access Protocol (IMAP) Even= ts in Sieve Author(s) : Barry Leiba Filename : draft-ietf-sieve-imap-sieve-07.txt Pages : 24 Date : 2012-09-10 Abstract: Sieve defines an email filtering language that can, in principle, plug into any point in the processing of an email message. As defined in the base specification, it plugs into mail delivery. This document defines how Sieve can plug into points in the IMAP protocol where messages are created or changed, adding the option of user- defined or installation-defined filtering (or, with Sieve extensions, features such as notifications). Because this requires future Sieve extensions to specify their interactions with this one, this document updates the base Sieve specification, RFC 5228. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sieve-imap-sieve-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From internet-drafts@ietf.org Mon Sep 10 14:16:14 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE8011E80F2; Mon, 10 Sep 2012 14:16:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.507 X-Spam-Level: X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xcaeBvS5kDkn; Mon, 10 Sep 2012 14:16:13 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D659C11E80E6; Mon, 10 Sep 2012 14:16:13 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> Date: Mon, 10 Sep 2012 14:16:13 -0700 Cc: sieve@ietf.org Subject: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 21:16:14 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Sieve Mail Filtering Language Working Gro= up of the IETF. Title : Support for Internet Message Access Protocol (IMAP) Even= ts in Sieve Author(s) : Barry Leiba Filename : draft-ietf-sieve-imap-sieve-08.txt Pages : 23 Date : 2012-09-10 Abstract: Sieve defines an email filtering language that can, in principle, plug into any point in the processing of an email message. As defined in the base specification, it plugs into mail delivery. This document defines how Sieve can plug into points in the IMAP protocol where messages are created or changed, adding the option of user- defined or installation-defined filtering (or, with Sieve extensions, features such as notifications). Because this requires future Sieve extensions to specify their interactions with this one, this document updates the base Sieve specification, RFC 5228. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sieve-imap-sieve-08 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From stephan@rename-it.nl Tue Sep 11 01:52:27 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3BD321F856F for ; Tue, 11 Sep 2012 01:52:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.096 X-Spam-Level: X-Spam-Status: No, score=0.096 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, J_CHICKENPOX_45=0.6] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30K+QKKjapoM for ; Tue, 11 Sep 2012 01:52:26 -0700 (PDT) Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id C227D21F87BA for ; Tue, 11 Sep 2012 01:52:24 -0700 (PDT) Received: from klara.student.utwente.nl ([130.89.162.218]:62105 helo=[10.168.3.2]) by drpepper.rename-it.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TBMCY-0000PM-2f; Tue, 11 Sep 2012 10:52:21 +0200 Message-ID: <504EFB8F.7000806@rename-it.nl> Date: Tue, 11 Sep 2012 10:51:27 +0200 From: Stephan Bosch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: sieve@ietf.org References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> In-Reply-To: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RenameIT-MailScanner-SpamScore: -2.3 (--) X-RenameIT-MailScanner-SpamCheck: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=ham version=3.3.1 Cc: Barry Leiba Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Sep 2012 08:52:28 -0000 On 9/10/2012 11:16 PM, internet-drafts@ietf.org 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 > Author(s) : Barry Leiba > Filename : draft-ietf-sieve-imap-sieve-08.txt > Pages : 23 > Date : 2012-09-10 > > Abstract: > Sieve defines an email filtering language that can, in principle, > plug into any point in the processing of an email message. As > defined in the base specification, it plugs into mail delivery. This > document defines how Sieve can plug into points in the IMAP protocol > where messages are created or changed, adding the option of user- > defined or installation-defined filtering (or, with Sieve extensions, > features such as notifications). Because this requires future Sieve > extensions to specify their interactions with this one, this document > updates the base Sieve specification, RFC 5228. There is no changelog in the document, so I wondered what changed and therefore I read it again. Rather than finding out what had changed, I noticed a few other things: #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? #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: -- 2.2.1. The IMAP APPEND Command A message may be added to a mailbox through the IMAP APPEND command. In a server that advertises "imapsieve", new messages added in this way MUST trigger the execution of a Sieve script, subject to the settings defined through Metadata (see Section 2.3.1). If the IMAP server supports the IMAP MultiAppend extension [RFC3502], multiple messages may be added to a mailbox through a single APPEND command. In a server that advertises "imapsieve", new messages added in this way MUST each individually trigger the execution of a Sieve script. -- This also stresses the fact that each individual message triggers the Sieve script. At other places in the document MULTIAPPEND is listed as a separate command, but there it would suffice to just remove it. 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). Regards, Stephan. From barryleiba.mailing.lists@gmail.com Thu Sep 13 12:05:54 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B47F421F859F for ; Thu, 13 Sep 2012 12:05:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.657 X-Spam-Level: X-Spam-Status: No, score=-102.657 tagged_above=-999 required=5 tests=[AWL=-0.280, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShiwFeg8MauO for ; Thu, 13 Sep 2012 12:05:53 -0700 (PDT) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9175221F85F9 for ; Thu, 13 Sep 2012 12:05:53 -0700 (PDT) Received: by mail-lpp01m010-f44.google.com with SMTP id m15so2317452lah.31 for ; Thu, 13 Sep 2012 12:05:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=2nhewkP+ZHNTDk/ptKlCJ/auU6s3KQvLIt2Ol8WP0Ig=; b=cjPkSwZ/UZxx9dbEqqianb6MVZ6uRafMfqV5za8lbWT8feuhHSJMsmGBCaSowGw++P JGg5LGb/vJnY9Pcg1t/fNUgi/w6cWCQBwh4vRucYwNrGXKCfoQu9WYpZ/2o9ZjuraooO AVb5YyJRoSCXUHupHP0fXJiZvnatgTxL0kvWt9iDBG+/40PC+y/km3RlfCnI88pcQI/b /vVjkWNDS8oReXY3yc6uNPY2G8IRQGaxjBvTc1T6CpxeAkrOU4p9wlZiL8L/yeCxwBwQ gL2TAHJz5q69NiMHVTaAFESNSCoNFkxjI9m2dlQPDrfp/MemC8fhlzpbYFYCpT6pNASI r+qA== MIME-Version: 1.0 Received: by 10.112.31.197 with SMTP id c5mr254558lbi.50.1347563153178; Thu, 13 Sep 2012 12:05:53 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.112.91.33 with HTTP; Thu, 13 Sep 2012 12:05:53 -0700 (PDT) In-Reply-To: <504EFB8F.7000806@rename-it.nl> References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> Date: Thu, 13 Sep 2012 15:05:53 -0400 X-Google-Sender-Auth: dRhRmL6Ba-sZZUAeTlnqiFnt1Bk Message-ID: From: Barry Leiba To: Stephan Bosch Content-Type: text/plain; charset=ISO-8859-1 Cc: sieve@ietf.org Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 19:05:54 -0000 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 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 , 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 From stephan@rename-it.nl Thu Sep 13 12:25:58 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7012421F84C5 for ; Thu, 13 Sep 2012 12:25:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.204 X-Spam-Level: X-Spam-Status: No, score=-0.204 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-Ci9CKLqJgx for ; Thu, 13 Sep 2012 12:25:58 -0700 (PDT) Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id D11C021F84B8 for ; Thu, 13 Sep 2012 12:25:56 -0700 (PDT) Received: from klara.student.utwente.nl ([130.89.162.218]:51721 helo=[10.168.3.2]) by drpepper.rename-it.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TCF2n-0000Uo-6d; Thu, 13 Sep 2012 21:25:51 +0200 Message-ID: <5052332F.3060407@rename-it.nl> Date: Thu, 13 Sep 2012 21:25:35 +0200 From: Stephan Bosch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Barry Leiba References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RenameIT-MailScanner-SpamScore: -2.3 (--) X-RenameIT-MailScanner-SpamCheck: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=ham version=3.3.1 Cc: sieve@ietf.org Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 19:25:58 -0000 On 9/13/2012 9:05 PM, Barry Leiba wrote: > 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. My previous comments were late already and I wonder why I missed these ones. > 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). That sounds fine. > On Tue, Sep 11, 2012 at 4:51 AM, Stephan Bosch 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. Indeed they are; good to know. It's good that I didn't use that though, otherwise I would not have made these comments. :) >> #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 > , 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. Agreed. >> 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. Yes, I agree. This document is too far along. I'll remember this for a future revision/extension. Regards, Stephan. From barryleiba.mailing.lists@gmail.com Thu Sep 13 12:32:44 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8E321F84BF for ; Thu, 13 Sep 2012 12:32:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.953 X-Spam-Level: X-Spam-Status: No, score=-102.953 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b2J5n2WpTRMq for ; Thu, 13 Sep 2012 12:32:39 -0700 (PDT) Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id EDCF321F8498 for ; Thu, 13 Sep 2012 12:32:35 -0700 (PDT) Received: by lbky2 with SMTP id y2so2390397lbk.31 for ; Thu, 13 Sep 2012 12:32:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=H3+fuJHXAp67DjWKBgVZlPhqPtdC+pv1Q1cfoTMivIc=; b=GZNlgHccKLs4JMrOLmWAIhSd1yeoxg11Bo3uh3P4p0LlVZQ5KwHg3gzVa3KFqLvlGk AZSRVU4khXUJXfYK+M4VC4kytyfxWs2oz3EOn9DXL5oNKGiD7mWeCq4zim+iJWjXcWo/ 4u/5CSWZ2Ayt3SN4ATVmHIFb7sbfjcJmVPPJVZYaHx0mFBMkk8YTPp0mxn1wzqxTXT6G 6yqsfuging/aUrpZsFCQJzqVDSuGYLuaPz18LBs2+QQIPkkn0C6WuHn7ReSTG4wA2FIO cvbQ/x57vmlblmp9rjwHkR/fo1D4oefMSooi4n38e2031QBbV1wb6PVAa7Zy9+xDXdpG Y5VQ== MIME-Version: 1.0 Received: by 10.112.51.228 with SMTP id n4mr276316lbo.55.1347564754786; Thu, 13 Sep 2012 12:32:34 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.112.91.33 with HTTP; Thu, 13 Sep 2012 12:32:34 -0700 (PDT) In-Reply-To: <5052332F.3060407@rename-it.nl> References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> <5052332F.3060407@rename-it.nl> Date: Thu, 13 Sep 2012 15:32:34 -0400 X-Google-Sender-Auth: HXs7B8vLRsry5db-8jNyQnMazPk Message-ID: From: Barry Leiba To: Stephan Bosch Content-Type: text/plain; charset=ISO-8859-1 Cc: sieve@ietf.org Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 19:32:44 -0000 > My previous comments were late already and I wonder why I missed these ones. It happens. I'll add, for the public record, that your reviews are always useful, and I'm very happy that you're taking the time to do them. Thanks. Barry From aaron@serendipity.cx Thu Sep 13 13:31:43 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595E721F84F6 for ; Thu, 13 Sep 2012 13:31:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.343 X-Spam-Level: X-Spam-Status: No, score=-101.343 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_45=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvXOYGO2Y+29 for ; Thu, 13 Sep 2012 13:31:42 -0700 (PDT) Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id EF29E21F84D1 for ; Thu, 13 Sep 2012 13:31:38 -0700 (PDT) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by slice.serendipity.cx (Postfix) with ESMTPSA id 7977F94004 for ; Thu, 13 Sep 2012 13:27:58 -0700 (PDT) Received: by dadf8 with SMTP id f8so1950054dad.31 for ; Thu, 13 Sep 2012 13:31:23 -0700 (PDT) Received: by 10.68.200.8 with SMTP id jo8mr988749pbc.148.1347568283698; Thu, 13 Sep 2012 13:31:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.14.100 with HTTP; Thu, 13 Sep 2012 13:31:03 -0700 (PDT) In-Reply-To: References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> From: Aaron Stone Date: Thu, 13 Sep 2012 13:31:03 -0700 Message-ID: To: Barry Leiba Content-Type: text/plain; charset=ISO-8859-1 Cc: sieve@ietf.org Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Sep 2012 20:31:43 -0000 On Thu, Sep 13, 2012 at 12:05 PM, Barry Leiba wrote: > 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). I don't think we're going to impact any existing implementations with this change, so it sounds fine to me. > On Tue, Sep 11, 2012 at 4:51 AM, Stephan Bosch 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 > , 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@ietf.org > https://www.ietf.org/mailman/listinfo/sieve From NED+mta-filters@mauve.mrochek.com Thu Sep 13 19:24:15 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B12721F86B5 for ; Thu, 13 Sep 2012 19:24:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_45=0.6] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aHxVpEMwZi6p for ; Thu, 13 Sep 2012 19:24:14 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id D5B7321F8694 for ; Thu, 13 Sep 2012 19:24:14 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OK7V9DV728008SO3@mauve.mrochek.com> for sieve@ietf.org; Thu, 13 Sep 2012 19:19:09 -0700 (PDT) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Thu, 13 Sep 2012 19:19:04 -0700 (PDT) From: NED+mta-filters@mauve.mrochek.com Message-id: <01OK7V9AS7RE0006TF@mauve.mrochek.com> Date: Thu, 13 Sep 2012 19:13:42 -0700 (PDT) In-reply-to: "Your message dated Thu, 13 Sep 2012 15:05:53 -0400" MIME-version: 1.0 Content-type: TEXT/PLAIN References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> To: Barry Leiba Cc: sieve@ietf.org Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 02:24:15 -0000 > << 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). I agree it's a reasonable change. However, RFC 5183 states: 4.3. IANA Registration of Environment Items A registry of environment items is provided by IANA. Item names may be registered on a first-come, first-served basis. Groups of items defined in a standards track or experimental RFC MAY choose to use a common name prefix of the form "name.", where "name" is a string that identifies the group of related items. I would therefore suggest "imap.cause". > > #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. > If the IMAP server also supports the IMAP MultiAppend extension > , 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. Although I still like the general idea, I agree now is not the time to reconsider. Ned From NED+mta-filters@mauve.mrochek.com Thu Sep 13 19:48:29 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D05D21F8624 for ; Thu, 13 Sep 2012 19:48:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EDuoXRaU6V-m for ; Thu, 13 Sep 2012 19:48:29 -0700 (PDT) Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 25C8F21F861C for ; Thu, 13 Sep 2012 19:48:29 -0700 (PDT) Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OK7W4EOKXS009I3N@mauve.mrochek.com> for sieve@ietf.org; Thu, 13 Sep 2012 19:43:24 -0700 (PDT) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OJFFFOH4280006TF@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Thu, 13 Sep 2012 19:43:17 -0700 (PDT) From: NED+mta-filters@mauve.mrochek.com Message-id: <01OK7W4AVWMA0006TF@mauve.mrochek.com> Date: Thu, 13 Sep 2012 19:42:59 -0700 (PDT) In-reply-to: "Your message dated Thu, 13 Sep 2012 15:32:34 -0400" MIME-version: 1.0 Content-type: TEXT/PLAIN References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> <5052332F.3060407@rename-it.nl> To: Barry Leiba Cc: sieve@ietf.org Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 02:48:29 -0000 > > My previous comments were late already and I wonder why I missed these ones. > It happens. I'll add, for the public record, that your reviews are > always useful, and I'm very happy that you're taking the time to do > them. Thanks. I emphatically agree. Ned From stephan@rename-it.nl Fri Sep 14 00:23:40 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 343C821F8600 for ; Fri, 14 Sep 2012 00:23:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.354 X-Spam-Level: X-Spam-Status: No, score=-0.354 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqqYPIWdHmjc for ; Fri, 14 Sep 2012 00:23:39 -0700 (PDT) Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id A65B021F85F9 for ; Fri, 14 Sep 2012 00:23:38 -0700 (PDT) Received: from klara.student.utwente.nl ([130.89.162.218]:61441 helo=[10.168.3.2]) by drpepper.rename-it.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1TCQFA-0005Vs-HX; Fri, 14 Sep 2012 09:23:27 +0200 Message-ID: <5052DB4C.2090706@rename-it.nl> Date: Fri, 14 Sep 2012 09:22:52 +0200 From: Stephan Bosch User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Ned Freed References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> <01OK7V9AS7RE0006TF@mauve.mrochek.com> In-Reply-To: <01OK7V9AS7RE0006TF@mauve.mrochek.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RenameIT-MailScanner-SpamScore: -2.3 (--) X-RenameIT-MailScanner-SpamCheck: No, score=-2.3 required=5.0 tests=ALL_TRUSTED, BAYES_00 autolearn=ham version=3.3.1 Cc: Barry Leiba , sieve@ietf.org Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 07:23:40 -0000 On 9/14/2012 4:13 AM, Ned Freed wrote: >> << 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). > I agree it's a reasonable change. However, RFC 5183 states: > > 4.3. IANA Registration of Environment Items > > A registry of environment items is provided by IANA. Item names may > be registered on a first-come, first-served basis. > > Groups of items defined in a standards track or experimental RFC MAY > choose to use a common name prefix of the form "name.", where "name" > is a string that identifies the group of related items. > > I would therefore suggest "imap.cause". Good point. Two others have an "imap" prefix too, so those should then become "imap.user" and "imap.email". For consistency, I'd also make "imap.changedflags" and "imap.mailbox". Regards, Stephan. From barryleiba@gmail.com Fri Sep 14 05:48:56 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7F421F84FD for ; Fri, 14 Sep 2012 05:48:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.955 X-Spam-Level: X-Spam-Status: No, score=-102.955 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id In+WSa5BbpSH for ; Fri, 14 Sep 2012 05:48:55 -0700 (PDT) Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9676621F84F1 for ; Fri, 14 Sep 2012 05:48:55 -0700 (PDT) Received: by vcbfo14 with SMTP id fo14so5270653vcb.31 for ; Fri, 14 Sep 2012 05:48:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=uoJ5sdKh5mKsJemwW8sG2Pw9mL70tudq37QDoG5F+tA=; b=FbNj4H8ufotqcEgsdrkWpp4diiVE4dEeD2i2NTrs7UbQUeCZ8Ys6kGI3v1DbnEqain GyVStFTkkQ0LXLlhuaiFtwYFpTNpcN45JfhOK9rOP87dQVSzFBym81Tzcnqp0M/982Fv +Q8EyDxkw2duROSZE/k9Qo3y2G/zx5GGhCkbrbLwz/lyfvgsrR4KBazA537aGHZEWV8r GNBpmmbCNQLgEnyyiyWW87tMxHs7fxvd/Pq14DQFbTHlpf67SJjxfOIzSBrvYtEM5kIf 4x2ubz3a8A4xVupX2W3Kk2XJw4H8roeY/GTZRRKBwHLLaVgq9qBRz8NwXgDCunqluLqa w4TQ== MIME-Version: 1.0 Received: by 10.220.152.67 with SMTP id f3mr2047104vcw.19.1347626934716; Fri, 14 Sep 2012 05:48:54 -0700 (PDT) Sender: barryleiba@gmail.com Received: by 10.58.58.41 with HTTP; Fri, 14 Sep 2012 05:48:54 -0700 (PDT) In-Reply-To: <5052DB4C.2090706@rename-it.nl> References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> <01OK7V9AS7RE0006TF@mauve.mrochek.com> <5052DB4C.2090706@rename-it.nl> Date: Fri, 14 Sep 2012 08:48:54 -0400 X-Google-Sender-Auth: SYNv9v9jfplnS-rcfj76Tp8pXnY Message-ID: From: Barry Leiba To: Stephan Bosch Content-Type: text/plain; charset=ISO-8859-1 Cc: sieve@ietf.org, Ned Freed Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 12:48:56 -0000 Ned says... > I would therefore suggest "imap.cause". Stephan says... > Two others have an "imap" prefix too, so those should then become > "imap.user" and "imap.email". For consistency, I'd also make > "imap.changedflags" and "imap.mailbox". So let it be written; so let it be done! Barry From internet-drafts@ietf.org Fri Sep 14 19:06:34 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A45E721E803A; Fri, 14 Sep 2012 19:06:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qqod4MsNbOL3; Fri, 14 Sep 2012 19:06:34 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3638F21E803F; Fri, 14 Sep 2012 19:06:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20120915020634.9588.76361.idtracker@ietfa.amsl.com> Date: Fri, 14 Sep 2012 19:06:34 -0700 Cc: sieve@ietf.org Subject: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-09.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 02:06:34 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Sieve Mail Filtering Language Working Gro= up of the IETF. Title : Support for Internet Message Access Protocol (IMAP) Even= ts in Sieve Author(s) : Barry Leiba Filename : draft-ietf-sieve-imap-sieve-09.txt Pages : 23 Date : 2012-09-14 Abstract: Sieve defines an email filtering language that can, in principle, plug into any point in the processing of an email message. As defined in the base specification, it plugs into mail delivery. This document defines how Sieve can plug into points in the IMAP protocol where messages are created or changed, adding the option of user- defined or installation-defined filtering (or, with Sieve extensions, features such as notifications). Because this requires future Sieve extensions to specify their interactions with this one, this document updates the base Sieve specification, RFC 5228. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-09 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sieve-imap-sieve-09 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From barryleiba.mailing.lists@gmail.com Sat Sep 15 05:33:25 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E15C121F8501 for ; Sat, 15 Sep 2012 05:33:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.958 X-Spam-Level: X-Spam-Status: No, score=-102.958 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVxP1ByjWs0W for ; Sat, 15 Sep 2012 05:33:25 -0700 (PDT) Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id DE81821F84F5 for ; Sat, 15 Sep 2012 05:33:24 -0700 (PDT) Received: by lahm15 with SMTP id m15so3491742lah.31 for ; Sat, 15 Sep 2012 05:33:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=dQd+WrnWEj4baq2i2ttckTIO9dtr2sMkfSjACLn6B58=; b=CqkBQ4kXlhMeTteAwsvv5SBK/7l0SKEj8k9GPzf1SV7ks+6XAxNGMcyieasBVH0WGq 25/Ct7Os2jnFmaSAWN2MG1dFU5ytzSPpj1Cd2S+BYfXYK99MxxKA8xxlEEbCWPKrv+kV ppLr4TbsGrE16EDojH5a17hGNVcUPMIEQx2T6C65i/jL6T891b5uRoJN8qwXlt2qyuez yJCLARuzR7XV/wabbR9fsNDrLVLh+R4MCu1+etlTGbbVT96MxLQd9BnTNdD0uSUM/Qi7 b/Agq22jZWqFeRHA0tgliEhkib+Cl/Ke7oACe16omZjQtdETJ9dZXOq/FMIJV575gMq1 z1Pg== MIME-Version: 1.0 Received: by 10.112.51.228 with SMTP id n4mr2194613lbo.55.1347712403820; Sat, 15 Sep 2012 05:33:23 -0700 (PDT) Sender: barryleiba.mailing.lists@gmail.com Received: by 10.112.91.33 with HTTP; Sat, 15 Sep 2012 05:33:23 -0700 (PDT) In-Reply-To: <20120915020634.9588.76361.idtracker@ietfa.amsl.com> References: <20120915020634.9588.76361.idtracker@ietfa.amsl.com> Date: Sat, 15 Sep 2012 08:33:23 -0400 X-Google-Sender-Auth: CykTLaKMb1jtKMBoaBcQi2_2N6k Message-ID: From: Barry Leiba To: sieve@ietf.org, Pete Resnick Content-Type: text/plain; charset=ISO-8859-1 Cc: Robert Sparks , Stephen Farrell Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-09.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 12:33:26 -0000 It looks like this is the final version that will go to the RFC Editor. It has the following changes over -08: - A paragraph in Security Considerations to address Stephen Farrell's DISCUSS position. - Some changes to address Robert Sparks's DISCUSS position and comments. - Some changes in response to the review of -08 by Stephan. - A factoring out of some common text (into the new Section 2.2.4) from Sections 3.3, 3.4, and 3.5, in response to an informal suggestion from Robert. Stephen and Robert, please check this version and clear your DISCUSSes. Pete, please add the following to the ballot text before giving your final approval: IANA Note IANA should take note of a late change to the Sieve environment names that are registered in Section 7.3. If anyone in the WG would like to give this a final once-over, this is the time. Pete, it's down to you now. Barry On Fri, Sep 14, 2012 at 10:06 PM, 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 > Author(s) : Barry Leiba > Filename : draft-ietf-sieve-imap-sieve-09.txt > Pages : 23 > Date : 2012-09-14 > > Abstract: > Sieve defines an email filtering language that can, in principle, > plug into any point in the processing of an email message. As > defined in the base specification, it plugs into mail delivery. This > document defines how Sieve can plug into points in the IMAP protocol > where messages are created or changed, adding the option of user- > defined or installation-defined filtering (or, with Sieve extensions, > features such as notifications). Because this requires future Sieve > extensions to specify their interactions with this one, this document > updates the base Sieve specification, RFC 5228. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-09 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-sieve-imap-sieve-09 > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > sieve mailing list > sieve@ietf.org > https://www.ietf.org/mailman/listinfo/sieve From rjsparks@nostrum.com Sat Sep 15 14:03:19 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0F4A21F845E for ; Sat, 15 Sep 2012 14:03:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.531 X-Spam-Level: X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yk59yo+YpKbd for ; Sat, 15 Sep 2012 14:03:19 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 350E921F8466 for ; Sat, 15 Sep 2012 14:03:19 -0700 (PDT) Received: from unnumerable.local (pool-173-57-93-208.dllstx.fios.verizon.net [173.57.93.208]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q8FL362o006787 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 15 Sep 2012 16:03:06 -0500 (CDT) (envelope-from rjsparks@nostrum.com) Message-ID: <5054ED0B.8050604@nostrum.com> Date: Sat, 15 Sep 2012 16:03:07 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Barry Leiba References: <20120915020634.9588.76361.idtracker@ietfa.amsl.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 173.57.93.208 is authenticated by a trusted mechanism) Cc: Pete Resnick , sieve@ietf.org, Stephen Farrell Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-09.txt X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Sep 2012 21:03:20 -0000 I've cleared. On 9/15/12 7:33 AM, Barry Leiba wrote: > It looks like this is the final version that will go to the RFC > Editor. It has the following changes over -08: > > - A paragraph in Security Considerations to address Stephen Farrell's > DISCUSS position. > > - Some changes to address Robert Sparks's DISCUSS position and comments. > > - Some changes in response to the review of -08 by Stephan. > > - A factoring out of some common text (into the new Section 2.2.4) > from Sections 3.3, 3.4, and 3.5, in response to an informal suggestion > from Robert. > > Stephen and Robert, please check this version and clear your DISCUSSes. > > Pete, please add the following to the ballot text before giving your > final approval: > > IANA Note > IANA should take note of a late change to the Sieve environment > names that are registered in Section 7.3. > > If anyone in the WG would like to give this a final once-over, this is > the time. Pete, it's down to you now. > > Barry > > On Fri, Sep 14, 2012 at 10:06 PM, 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 >> Author(s) : Barry Leiba >> Filename : draft-ietf-sieve-imap-sieve-09.txt >> Pages : 23 >> Date : 2012-09-14 >> >> Abstract: >> Sieve defines an email filtering language that can, in principle, >> plug into any point in the processing of an email message. As >> defined in the base specification, it plugs into mail delivery. This >> document defines how Sieve can plug into points in the IMAP protocol >> where messages are created or changed, adding the option of user- >> defined or installation-defined filtering (or, with Sieve extensions, >> features such as notifications). Because this requires future Sieve >> extensions to specify their interactions with this one, this document >> updates the base Sieve specification, RFC 5228. >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve >> >> There's also a htmlized version available at: >> http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve-09 >> >> A diff from the previous version is available at: >> http://www.ietf.org/rfcdiff?url2=draft-ietf-sieve-imap-sieve-09 >> >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> sieve mailing list >> sieve@ietf.org >> https://www.ietf.org/mailman/listinfo/sieve From iesg-secretary@ietf.org Thu Sep 20 07:40:28 2012 Return-Path: X-Original-To: sieve@ietfa.amsl.com Delivered-To: sieve@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6CB421F8793; Thu, 20 Sep 2012 07:40:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.536 X-Spam-Level: X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oERvz6v9Vg1q; Thu, 20 Sep 2012 07:40:28 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA4F21F877A; Thu, 20 Sep 2012 07:40:27 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.34 Message-ID: <20120920144027.26560.46362.idtracker@ietfa.amsl.com> Date: Thu, 20 Sep 2012 07:40:27 -0700 Cc: sieve mailing list , sieve chair , RFC Editor Subject: [sieve] Protocol Action: 'Support for Internet Message Access Protocol (IMAP) Events in Sieve' to Proposed Standard (draft-ietf-sieve-imap-sieve-09.txt) X-BeenThere: sieve@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: SIEVE Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2012 14:40:29 -0000 The IESG has approved the following document: - 'Support for Internet Message Access Protocol (IMAP) Events in Sieve' (draft-ietf-sieve-imap-sieve-09.txt) as Proposed Standard This document is the product of the Sieve Mail Filtering Language Working Group. The IESG contact persons are Pete Resnick and Barry Leiba. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-sieve-imap-sieve/ Technical Summary This document defines how the Sieve email filtering language can plug into points in the IMAP protocol where messages are created or changed, adding the option of user-defined or installation-defined filtering (or, with Sieve extensions, features such as notifications). Working Group Summary This document originated from the Lemonade WG and was initially submitted back in 2005. In 2010 it was adopted by the SIEVE WG as Lemonade was closed. Since that time there have been several revision of the document prompted by mailing list discussions and face-to-face meetings. Note that many of the participants in the SIEVE WG are also IMAP "experts" so the interactions between SIEVE and IMAP have been fully covered. Whilst many people have reviewed and contributed to this document over its lifetime, the recent working group last call only garnered a few responses (all positive and supporting publication). That said, there has not been any significant controversy surrounding this document, and in the Chairs' opinion there is consensus to publish it. Document Quality There are no known implementations of this protocol to date. A number of vendors have indicated interest in it, with at least one stating they will start work on that soon. Personnel Document Shepherd: Cyrus Daboo AD: Pete Resnick