
From stephan@rename-it.nl  Mon Jul  9 01:34:42 2012
Return-Path: <stephan@rename-it.nl>
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 E27CE21F864E for <sieve@ietfa.amsl.com>; Mon,  9 Jul 2012 01:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.355
X-Spam-Level: *
X-Spam-Status: No, score=1.355 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7uH9PTBj7BGh for <sieve@ietfa.amsl.com>; Mon,  9 Jul 2012 01:34:42 -0700 (PDT)
Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id 560BF21F863C for <sieve@ietf.org>; Mon,  9 Jul 2012 01:34:40 -0700 (PDT)
Received: from klara.student.utwente.nl ([130.89.162.218]:64610 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 <stephan@rename-it.nl>) id 1So9Ql-0006Wh-Lq; Mon, 09 Jul 2012 10:34:57 +0200
Message-ID: <4FFA97A3.1030508@rename-it.nl>
Date: Mon, 09 Jul 2012 10:34:43 +0200
From: Stephan Bosch <stephan@rename-it.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Cyrus Daboo <cyrus@daboo.name>
References: <B5057302A66EA30CEE78BCB9@caldav.corp.apple.com>
In-Reply-To: <B5057302A66EA30CEE78BCB9@caldav.corp.apple.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: sieve@ietf.org
Subject: Re: [sieve] WGLC: draft-ietf-sieve-imap-sieve-04.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 08:34:43 -0000

On 5/30/2012 10:30 PM, Cyrus Daboo wrote:
> Hi folks,
> I am starting a working group last call on 
> draft-ietf-sieve-imap-sieve-04.txt. This is the last document this 
> working group has on its plate and once finished, we intend to shut 
> down the working group.
>
> The last call on draft-ietf-sieve-imap-sieve-04.txt will run for two 
> weeks. Please review this draft and send comments to the list. This 
> document has been around for a while, so if you have done a detailed 
> review before, just checking the changes now should be sufficient. In 
> any case, the chairs want to heard from everyone who has done a review 
> and those who have decided for or against doing an implementation of 
> this in the near future.
>

I hope I'm still somewhat on time with the following small comments:

*) In Section 2.1, the syntax of the new IMAP capability is described. 
It includes a sieveurl-server syntax item. Although I expect anyone on 
this list to know what it is for, I think it would be good to mention 
explicitly that it points to the ManageSieve server the client needs to  
contact for managing Sieve scripts.

*) I wonder what happens if the fileinto action points to the mailbox 
the message currently resides in (call it the 'source mailbox'). Does it 
match 'keep' behavior in that special case, or will it just create a 
copy of the message in the source mailbox (potentially dropping the 
original)? Current text suggests the latter and that is also what I 
prefer: I'd like to be able to create a new version of the message in 
the same mailbox. I think it would be good to mention this special 
situation explicitly either way.

Overall, I really like the quality of this specification. Once our IMAP 
server gains the required METADATA support I intend to implement this 
extension.

Regards,

Stephan.


From cyrus@daboo.name  Mon Jul  9 07:07:05 2012
Return-Path: <cyrus@daboo.name>
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 A5B3D21F85FB for <sieve@ietfa.amsl.com>; Mon,  9 Jul 2012 07:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5UCVUwp-9uY for <sieve@ietfa.amsl.com>; Mon,  9 Jul 2012 07:07:05 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2270021F85EA for <sieve@ietf.org>; Mon,  9 Jul 2012 07:07:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id D3F562ADC9E9; Mon,  9 Jul 2012 10:07:29 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-sYSjZFckdP; Mon,  9 Jul 2012 10:07:26 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 853EE2ADC9DC; Mon,  9 Jul 2012 10:07:25 -0400 (EDT)
Date: Mon, 09 Jul 2012 10:07:22 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Stephan Bosch <stephan@rename-it.nl>
Message-ID: <2F6247FFB7EAFDE07E4052CB@caldav.corp.apple.com>
In-Reply-To: <4FFA97A3.1030508@rename-it.nl>
References: <B5057302A66EA30CEE78BCB9@caldav.corp.apple.com> <4FFA97A3.1030508@rename-it.nl>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1526
Cc: sieve@ietf.org
Subject: Re: [sieve] WGLC: draft-ietf-sieve-imap-sieve-04.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jul 2012 14:07:05 -0000

Hi Stephan,

--On July 9, 2012 10:34:43 AM +0200 Stephan Bosch <stephan@rename-it.nl> 
wrote:

> I hope I'm still somewhat on time with the following small comments:
>
> *) In Section 2.1, the syntax of the new IMAP capability is described. It
> includes a sieveurl-server syntax item. Although I expect anyone on this
> list to know what it is for, I think it would be good to mention
> explicitly that it points to the ManageSieve server the client needs to
> contact for managing Sieve scripts.
>
> *) I wonder what happens if the fileinto action points to the mailbox the
> message currently resides in (call it the 'source mailbox'). Does it
> match 'keep' behavior in that special case, or will it just create a copy
> of the message in the source mailbox (potentially dropping the original)?
> Current text suggests the latter and that is also what I prefer: I'd like
> to be able to create a new version of the message in the same mailbox. I
> think it would be good to mention this special situation explicitly
> either way.
>
> Overall, I really like the quality of this specification. Once our IMAP
> server gains the required METADATA support I intend to implement this
> extension.

Thanks for the feedback. I'll leave Barry to address these points now if he 
wishes. However, I am in the process of putting together a write-up for 
this document so we can move forward with processing it. So we might wait 
until after IETF last call to address your issues in a new draft, depending 
on timing.

-- 
Cyrus Daboo


From barryleiba.mailing.lists@gmail.com  Sat Jul 14 13:11:05 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 A3D3321F8604 for <sieve@ietfa.amsl.com>; Sat, 14 Jul 2012 13:11:05 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cvcF7cleOBmM for <sieve@ietfa.amsl.com>; Sat, 14 Jul 2012 13:11:05 -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 BF3F721F85FD for <sieve@ietf.org>; Sat, 14 Jul 2012 13:11:04 -0700 (PDT)
Received: by lbbgo11 with SMTP id go11so6475736lbb.31 for <sieve@ietf.org>; Sat, 14 Jul 2012 13:11:43 -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=dAsDm2toxiTNPqhjq6ckVbZYNIeyd+7ZdQLif3g1ydo=; b=TtMUfXA2jzRCcjhkk2Jgdz2p9cuqYIyi0Atchyrwepb6gwJaO2jE6MJEcnyVLDyfar 0+Wa/OVd5NQQBC1BIuY0Oxj0JwydG78Nq4mIatBOIKo8bUPy9EHJB5+cNyaFDQ9fzXr6 UFBJ5+QM8UwxvI/uJKRqLQtaMSFkxxGGoOznIEbNr7MDMM8WhFEcjYD5t+FFvLeLUVxW KFH81kox2L8W3M5DWjNh9VQ6DVphTF0wtSGnkOqwDGC7zFzJgXaJQx4uHg6/HyDkgXWj zAjmNyafw6zyiCEI8WOGFh9XeanWmzFbol5A8Trn0flwmsh0fMuLQbsB0+0j3jPrjYYr MyZQ==
MIME-Version: 1.0
Received: by 10.152.112.233 with SMTP id it9mr5839399lab.40.1342296703678; Sat, 14 Jul 2012 13:11:43 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.17.133 with HTTP; Sat, 14 Jul 2012 13:11:43 -0700 (PDT)
In-Reply-To: <4FFA97A3.1030508@rename-it.nl>
References: <B5057302A66EA30CEE78BCB9@caldav.corp.apple.com> <4FFA97A3.1030508@rename-it.nl>
Date: Sat, 14 Jul 2012 16:11:43 -0400
X-Google-Sender-Auth: Pjqajhui_OxsmpmJjNqWVewsddg
Message-ID: <CAC4RtVDmGZk=vSPzjadTDBE_8dtbWE2ZDFeaK3o1xHZH7RaZuA@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Bosch <stephan@rename-it.nl>
Content-Type: text/plain; charset=ISO-8859-1
Cc: sieve@ietf.org
Subject: Re: [sieve] WGLC: draft-ietf-sieve-imap-sieve-04.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2012 20:11:05 -0000

Thanks for the review and comments, Stephan, and for the interest in
implementing this.

> I hope I'm still somewhat on time with the following small comments:

Late is fine, when the comments are useful.  :-)
I'm about to upload an -06 version with the following changes.

> *) In Section 2.1, the syntax of the new IMAP capability is described. It
> includes a sieveurl-server syntax item. Although I expect anyone on this
> list to know what it is for, I think it would be good to mention explicitly
> that it points to the ManageSieve server the client needs to  contact for
> managing Sieve scripts.

I have added a new sentence to the end of this paragraph:

   Only one "imapsieve" capability string, specifying one sieveurl-
   server, can be present.  The sieveurl-server identifies the
   ManageSieve server that clients need to contact for managing Sieve
   scripts associated with this IMAP server.

> *) I wonder what happens if the fileinto action points to the mailbox the
> message currently resides in (call it the 'source mailbox'). Does it match
> 'keep' behavior in that special case, or will it just create a copy of the
> message in the source mailbox (potentially dropping the original)? Current
> text suggests the latter and that is also what I prefer: I'd like to be able
> to create a new version of the message in the same mailbox. I think it would
> be good to mention this special situation explicitly either way.

I have added a new sentence to the end of this paragraph:

   For APPEND, MULTIAPPEND, and COPY, the message is stored into the
   fileinto mailbox IN ADDITION TO the original target mailbox.  For
   flag changes, the message is COPIED into the fileinto mailbox,
   without removing the original.  In all cases, fileinto always creates
   a new message, separate from the original.

Barry

From internet-drafts@ietf.org  Sat Jul 14 13:12:12 2012
Return-Path: <internet-drafts@ietf.org>
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 AB4B721F860F; Sat, 14 Jul 2012 13:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.51
X-Spam-Level: 
X-Spam-Status: No, score=-102.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id htpmjq9mLMgS; Sat, 14 Jul 2012 13:12:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B41921F8618; Sat, 14 Jul 2012 13:12:12 -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.30p3
Message-ID: <20120714201212.30210.12438.idtracker@ietfa.amsl.com>
Date: Sat, 14 Jul 2012 13:12:12 -0700
Cc: sieve@ietf.org
Subject: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-06.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2012 20:12:12 -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-06.txt
	Pages           : 23
	Date            : 2012-07-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).


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-06

A diff from previous version is available at:
http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-sieve-imap-sieve-06


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From stephan@rename-it.nl  Sat Jul 14 16:29:03 2012
Return-Path: <stephan@rename-it.nl>
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 01D2121F84EA for <sieve@ietfa.amsl.com>; Sat, 14 Jul 2012 16:29:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.425
X-Spam-Level: 
X-Spam-Status: No, score=0.425 tagged_above=-999 required=5 tests=[AWL=0.929,  BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ovVcxRYLWJKe for <sieve@ietfa.amsl.com>; Sat, 14 Jul 2012 16:29:02 -0700 (PDT)
Received: from drpepper.rename-it.nl (drpepper.rename-it.nl [217.119.238.16]) by ietfa.amsl.com (Postfix) with ESMTP id 6F83F21F84E1 for <sieve@ietf.org>; Sat, 14 Jul 2012 16:29:00 -0700 (PDT)
Received: from klara.student.utwente.nl ([130.89.162.218]:51474 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 <stephan@rename-it.nl>) id 1SqBlz-0000CC-W1; Sun, 15 Jul 2012 01:29:17 +0200
Message-ID: <500200CA.5080603@rename-it.nl>
Date: Sun, 15 Jul 2012 01:29:14 +0200
From: Stephan Bosch <stephan@rename-it.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <B5057302A66EA30CEE78BCB9@caldav.corp.apple.com> <4FFA97A3.1030508@rename-it.nl> <CAC4RtVDmGZk=vSPzjadTDBE_8dtbWE2ZDFeaK3o1xHZH7RaZuA@mail.gmail.com>
In-Reply-To: <CAC4RtVDmGZk=vSPzjadTDBE_8dtbWE2ZDFeaK3o1xHZH7RaZuA@mail.gmail.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: sieve@ietf.org
Subject: Re: [sieve] WGLC: draft-ietf-sieve-imap-sieve-04.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jul 2012 23:29:03 -0000

On 7/14/2012 10:11 PM, Barry Leiba wrote:
>> *) In Section 2.1, the syntax of the new IMAP capability is described. It
>> includes a sieveurl-server syntax item. Although I expect anyone on this
>> list to know what it is for, I think it would be good to mention explicitly
>> that it points to the ManageSieve server the client needs to  contact for
>> managing Sieve scripts.
> I have added a new sentence to the end of this paragraph:
>
>     Only one "imapsieve" capability string, specifying one sieveurl-
>     server, can be present.  The sieveurl-server identifies the
>     ManageSieve server that clients need to contact for managing Sieve
>     scripts associated with this IMAP server.

Agreed.

>> *) I wonder what happens if the fileinto action points to the mailbox the
>> message currently resides in (call it the 'source mailbox'). Does it match
>> 'keep' behavior in that special case, or will it just create a copy of the
>> message in the source mailbox (potentially dropping the original)? Current
>> text suggests the latter and that is also what I prefer: I'd like to be able
>> to create a new version of the message in the same mailbox. I think it would
>> be good to mention this special situation explicitly either way.
> I have added a new sentence to the end of this paragraph:
>
>     For APPEND, MULTIAPPEND, and COPY, the message is stored into the
>     fileinto mailbox IN ADDITION TO the original target mailbox.  For
>     flag changes, the message is COPIED into the fileinto mailbox,
>     without removing the original.  In all cases, fileinto always creates
>     a new message, separate from the original.

Good.

Regards,

Stephan.


From aaron@serendipity.cx  Mon Jul 23 11:10:37 2012
Return-Path: <aaron@serendipity.cx>
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 2810E11E8093 for <sieve@ietfa.amsl.com>; Mon, 23 Jul 2012 11:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.143
X-Spam-Level: 
X-Spam-Status: No, score=-100.143 tagged_above=-999 required=5 tests=[AWL=-1.100, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZg1VLrLNQmx for <sieve@ietfa.amsl.com>; Mon, 23 Jul 2012 11:10:35 -0700 (PDT)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB0E11E80AE for <sieve@ietf.org>; Mon, 23 Jul 2012 11:10:35 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by slice.serendipity.cx (Postfix) with ESMTPSA id E043930145 for <sieve@ietf.org>; Mon, 23 Jul 2012 11:08:16 -0700 (PDT)
Received: by wibhr14 with SMTP id hr14so2474739wib.13 for <sieve@ietf.org>; Mon, 23 Jul 2012 11:10:28 -0700 (PDT)
Received: by 10.216.4.147 with SMTP id 19mr8341239wej.109.1343067028738; Mon, 23 Jul 2012 11:10:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.187.147 with HTTP; Mon, 23 Jul 2012 11:10:08 -0700 (PDT)
From: Aaron Stone <aaron@serendipity.cx>
Date: Mon, 23 Jul 2012 11:10:08 -0700
Message-ID: <CAEdAYKVm=zK0b=dYpx04Zkpz-3b8rPPVLGiEcxZkMjaSmafbhg@mail.gmail.com>
To: Sieve mailing list <sieve@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [sieve] Unicode regular expressions
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jul 2012 18:10:37 -0000

http://www.unicode.org/reports/tr18/tr18-15.html

Unicode Technical Standard #18, Unicode Regular Expressions, just got
a new draft in July 2012; the previous draft was done in 2008. Who's
ready to update our own Regex draft?

*ducks*

Aaron
