Re: [sieve] SPECIAL-USE in Sieve (RFC 6154) Sat, 02 April 2016 07:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1516612D558 for <>; Sat, 2 Apr 2016 00:46:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.912
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UVCTBxv_kC5Y for <>; Sat, 2 Apr 2016 00:46:28 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B561512D575 for <>; Sat, 2 Apr 2016 00:46:28 -0700 (PDT)
Received: from by (PMDF V6.1-1 #35243) id <> for; 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 by (PMDF V6.1-1 #35243) id <> (original mail from for; Sat, 02 Apr 2016 00:41:23 -0700 (PDT)
Message-id: <>
Date: Sat, 02 Apr 2016 00:28:43 -0700 (PDT)
In-reply-to: "Your message dated Tue, 29 Mar 2016 00:44:40 +0200" <>
References: <>
To: Stephan Bosch <>
Archived-At: <>
Cc: Sieve mailing list <>
Subject: Re: [sieve] SPECIAL-USE in Sieve (RFC 6154)
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SIEVE Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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

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.