
From nobody Fri Apr  1 05:20:26 2016
Return-Path: <alexey.melnikov@isode.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 4918512D58F for <sieve@ietfa.amsl.com>; Fri,  1 Apr 2016 05:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u1JHwWx-uGeb for <sieve@ietfa.amsl.com>; Fri,  1 Apr 2016 05:20:16 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 440BF12D123 for <sieve@ietf.org>; Fri,  1 Apr 2016 05:20:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1459513213; d=isode.com; s=selector; i=@isode.com; bh=uTYB3X66hTJOeLEjJ7Lxolhhnb6Ae++G+50iIloGyvs=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=i66JjaZqqr18ZTm4SZSJi0d/Q9C0q3soqWAO68RfTMnMrPmk9NiwcAkSFlW5tuyFiRUvAo 5CEdUVzBXBdMAJmkqlaxD+g9/Ae0ywtyXwr8kZTWHc6iDfRtMfgLs9TGcchGseozAf2kdE omYXV1kc044AQAg+J+Bw9VUPanEhoyA=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <Vv5nfAB25pfp@statler.isode.com>; Fri, 1 Apr 2016 13:20:13 +0100
To: Stephan Bosch <stephan@rename-it.nl>
References: <56F9B3D8.8080104@rename-it.nl> <CAC4RtVC=WWvNGNKrJticQfc=eo7Vo_ZBDGArf6Bp8q5dfck6+w@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <56FE6750.50301@isode.com>
Date: Fri, 1 Apr 2016 13:19:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
In-Reply-To: <CAC4RtVC=WWvNGNKrJticQfc=eo7Vo_ZBDGArf6Bp8q5dfck6+w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/sieve/dlHh-EP_9jQr4k5sDBza_RQmQ18>
Cc: Barry Leiba <barryleiba@computer.org>, Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] SPECIAL-USE in Sieve (RFC 6154)
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 01 Apr 2016 12:20:24 -0000

Stephan,

On 31/03/2016 03:36, Barry Leiba wrote:
>> Please tell me what you think. I aim to submit this to appsawg soon, but
>> I think most Sieve people are still concentrated here, so I post it here
>> first.
> It sounds reasonable, yes.  But not to appsawg: appsawg is closing
> soon, and not accepting new documents.
I think emailing apps-discuss mailing list is fine though.
> You should bring it to the
> DISPATCH working group for consideration, and they will decide whether
> it should go to a working group or should be recommended to an AD to
> sponsor.

If there is enough interest in this, I can AD-sponsor it without DISPATCH.


From nobody Sat Apr  2 00:46:31 2016
Return-Path: <NED+mta-filters@mauve.mrochek.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 1516612D558 for <sieve@ietfa.amsl.com>; Sat,  2 Apr 2016 00:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVCTBxv_kC5Y for <sieve@ietfa.amsl.com>; Sat,  2 Apr 2016 00:46:28 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B561512D575 for <sieve@ietf.org>; Sat,  2 Apr 2016 00:46:28 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PYIO7J6BRK00C69N@mauve.mrochek.com> for sieve@ietf.org; Sat, 2 Apr 2016 00:41:29 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PY1MT70XR400005M@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Sat, 02 Apr 2016 00:41:23 -0700 (PDT)
From: NED+mta-filters@mauve.mrochek.com
Message-id: <01PYIO7I2RPQ00005M@mauve.mrochek.com>
Date: Sat, 02 Apr 2016 00:28:43 -0700 (PDT)
In-reply-to: "Your message dated Tue, 29 Mar 2016 00:44:40 +0200" <56F9B3D8.8080104@rename-it.nl>
References: <56F9B3D8.8080104@rename-it.nl>
To: Stephan Bosch <stephan@rename-it.nl>
Archived-At: <http://mailarchive.ietf.org/arch/msg/sieve/xlLfwdle8gdbk5PxsWuDnF616kE>
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] SPECIAL-USE in Sieve (RFC 6154)
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Apr 2016 07:46:30 -0000

> Currently, the Sieve language lacks the means of freely accessing the
> IMAP special-use mailbox attributes (RFC 6154). For example, it would be
> nice to be able to determine what the Junk mailbox is during Sieve
> processing at delivery, based on which mailbox has the "\Junk"
> special-use attribute assigned. I believe I have coined this idea before
> several years ago, but the incentive to actually build or document
> anything was never very high.

> Recently, I found the motivation to design a proper Sieve extension for
> this; I finished implementing IMAPSIEVE and in that context such
> functionality can also be very useful.  The draft specification is
> attached, since the IETF draft submission is currently blocked.

> Please tell me what you think. I aim to submit this to appsawg soon, but
> I think most Sieve people are still concentrated here, so I post it here
> first.

This looks like a useful addition to sieve to me. I support its adoption as a
draft.

One thing you'll need to address is the ability for the same special use
attribute to be attached to multiple mailboxes. Since the ability to have the
same special-use attribute on multiple mailboxes is implementation-specific, my
suggestion would be to make the behavior in this case implementation-specific
as well.

				Ned


From nobody Sun Apr  3 04:16:58 2016
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 C634412D5C6 for <sieve@ietfa.amsl.com>; Sun,  3 Apr 2016 04:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ex8iABdXDUrw for <sieve@ietfa.amsl.com>; Sun,  3 Apr 2016 04:16:55 -0700 (PDT)
Received: from sogo.guto.nl (guto.nl [178.21.117.49]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA24112D5C5 for <sieve@ietf.org>; Sun,  3 Apr 2016 04:16:54 -0700 (PDT)
Received: from lab.inertia-technology.com ([217.119.239.130] helo=[192.168.1.103]) by sogo.guto.nl with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <stephan@rename-it.nl>) id 1amg1P-0001oE-QT; Sun, 03 Apr 2016 13:16:50 +0200
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <56F9B3D8.8080104@rename-it.nl> <CAC4RtVC=WWvNGNKrJticQfc=eo7Vo_ZBDGArf6Bp8q5dfck6+w@mail.gmail.com> <56FE6750.50301@isode.com>
From: Stephan Bosch <stephan@rename-it.nl>
Message-ID: <5700FBA5.40305@rename-it.nl>
Date: Sun, 3 Apr 2016 13:16:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <56FE6750.50301@isode.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 217.119.239.130
X-SA-Exim-Mail-From: stephan@rename-it.nl
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on sogo.guto.nl)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sieve/mNUwSkRbvASV3jSefRXF_P7ah5A>
Cc: Barry Leiba <barryleiba@computer.org>, Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] SPECIAL-USE in Sieve (RFC 6154)
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 03 Apr 2016 11:16:57 -0000

Op 1-4-2016 om 14:19 schreef Alexey Melnikov:
> Stephan,
>
> On 31/03/2016 03:36, Barry Leiba wrote:
>>> Please tell me what you think. I aim to submit this to appsawg soon, 
>>> but
>>> I think most Sieve people are still concentrated here, so I post it 
>>> here
>>> first.
>> It sounds reasonable, yes.  But not to appsawg: appsawg is closing
>> soon, and not accepting new documents.
> I think emailing apps-discuss mailing list is fine though.

OK, I will do that.

>> You should bring it to the
>> DISPATCH working group for consideration, and they will decide whether
>> it should go to a working group or should be recommended to an AD to
>> sponsor.
>
> If there is enough interest in this, I can AD-sponsor it without 
> DISPATCH.

Thanks!

Regards,

Stephan.


From nobody Sun Apr  3 04:28:02 2016
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 E554B12D5CA for <sieve@ietfa.amsl.com>; Sun,  3 Apr 2016 04:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUoAx2GVbQN3 for <sieve@ietfa.amsl.com>; Sun,  3 Apr 2016 04:27:55 -0700 (PDT)
Received: from sogo.guto.nl (guto.nl [178.21.117.49]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AB3712D5D5 for <sieve@ietf.org>; Sun,  3 Apr 2016 04:27:53 -0700 (PDT)
Received: from lab.inertia-technology.com ([217.119.239.130] helo=[192.168.1.103]) by sogo.guto.nl with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <stephan@rename-it.nl>) id 1amgC6-0001qS-Cg; Sun, 03 Apr 2016 13:27:51 +0200
To: Ned Freed <ned.freed@mrochek.com>
References: <56F9B3D8.8080104@rename-it.nl> <01PYIO7I2RPQ00005M@mauve.mrochek.com>
From: Stephan Bosch <stephan@rename-it.nl>
Message-ID: <5700FE3B.1000302@rename-it.nl>
Date: Sun, 3 Apr 2016 13:27:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <01PYIO7I2RPQ00005M@mauve.mrochek.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 217.119.239.130
X-SA-Exim-Mail-From: stephan@rename-it.nl
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on sogo.guto.nl)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sieve/gOx-nvtDJsTqBX0-mOF96CDKAuM>
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] SPECIAL-USE in Sieve (RFC 6154)
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 03 Apr 2016 11:28:02 -0000

Op 2-4-2016 om 9:28 schreef Ned Freed:
>> Please tell me what you think. I aim to submit this to appsawg soon, but
>> I think most Sieve people are still concentrated here, so I post it here
>> first.
> This looks like a useful addition to sieve to me. I support its adoption as a
> draft.

Thanks!

> One thing you'll need to address is the ability for the same special use
> attribute to be attached to multiple mailboxes. Since the ability to have the
> same special-use attribute on multiple mailboxes is implementation-specific, my
> suggestion would be to make the behavior in this case implementation-specific
> as well.

Section 4 states the following:

"More than one mailbox can have a particular special-use flag assigned. 
In that case, the mailbox that is chosen for delivery is 
implementation-defined. However, implementations MUST ensure that this 
choice is made consistently, so that the same mailbox is used every time."

Isn't that what you mean? What is missing?

Regards,

Stephan.


From nobody Sun Apr  3 09:14:58 2016
Return-Path: <NED+mta-filters@mauve.mrochek.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 1126212D608 for <sieve@ietfa.amsl.com>; Sun,  3 Apr 2016 09:14:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RkoI7Clzw51t for <sieve@ietfa.amsl.com>; Sun,  3 Apr 2016 09:14:56 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C828B12D605 for <sieve@ietf.org>; Sun,  3 Apr 2016 09:14:56 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PYKK95XZQ800BKCP@mauve.mrochek.com> for sieve@ietf.org; Sun, 3 Apr 2016 09:09:55 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01PY1MT70XR400005M@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Sun, 03 Apr 2016 09:09:39 -0700 (PDT)
From: NED+mta-filters@mauve.mrochek.com
Message-id: <01PYKK8YKZBE00005M@mauve.mrochek.com>
Date: Sun, 03 Apr 2016 09:09:03 -0700 (PDT)
In-reply-to: "Your message dated Sun, 03 Apr 2016 13:27:55 +0200" <5700FE3B.1000302@rename-it.nl>
References: <56F9B3D8.8080104@rename-it.nl> <01PYIO7I2RPQ00005M@mauve.mrochek.com> <5700FE3B.1000302@rename-it.nl>
To: Stephan Bosch <stephan@rename-it.nl>
Archived-At: <http://mailarchive.ietf.org/arch/msg/sieve/iHmEhRd9PzydDqX9p2PuH2f9uWQ>
Cc: Sieve mailing list <sieve@ietf.org>, Ned Freed <ned.freed@mrochek.com>
Subject: Re: [sieve] SPECIAL-USE in Sieve (RFC 6154)
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Sun, 03 Apr 2016 16:14:58 -0000

> Op 2-4-2016 om 9:28 schreef Ned Freed:
> >> Please tell me what you think. I aim to submit this to appsawg soon, but
> >> I think most Sieve people are still concentrated here, so I post it here
> >> first.
> > This looks like a useful addition to sieve to me. I support its adoption as a
> > draft.

> Thanks!

> > One thing you'll need to address is the ability for the same special use
> > attribute to be attached to multiple mailboxes. Since the ability to have the
> > same special-use attribute on multiple mailboxes is implementation-specific, my
> > suggestion would be to make the behavior in this case implementation-specific
> > as well.

> Section 4 states the following:

> "More than one mailbox can have a particular special-use flag assigned.
> In that case, the mailbox that is chosen for delivery is
> implementation-defined. However, implementations MUST ensure that this
> choice is made consistently, so that the same mailbox is used every time."

Missed that, sorry.

> Isn't that what you mean? What is missing?

Yes, that addresses the issue.

				Ned

