Re: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-01.txt

Stephan Bosch <stephan.bosch@dovecot.fi> Sat, 04 August 2018 10:37 UTC

Return-Path: <stephan.bosch@dovecot.fi>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42CC81294D7 for <extra@ietfa.amsl.com>; Sat, 4 Aug 2018 03:37:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 qmQEVlmWdifg for <extra@ietfa.amsl.com>; Sat, 4 Aug 2018 03:37:19 -0700 (PDT)
Received: from mail.dovecot.fi (wursti.dovecot.fi [94.237.32.243]) by ietfa.amsl.com (Postfix) with ESMTP id B348412F1A5 for <extra@ietf.org>; Sat, 4 Aug 2018 03:37:19 -0700 (PDT)
Received: from [10.168.3.2] (klara.student.utwente.nl [130.89.162.218]) by mail.dovecot.fi (Postfix) with ESMTPSA id 6E1B62A6905; Sat, 4 Aug 2018 13:37:08 +0300 (EEST)
From: Stephan Bosch <stephan.bosch@dovecot.fi>
To: Ned Freed <ned.freed@mrochek.com>
Cc: extra@ietf.org, Bron Gondwana <brong@fastmailteam.com>
References: <151533655607.10858.793231788332492256@ietfa.amsl.com> <ce56fc8f-366a-8e1e-2f00-1ed22da28d15@dovecot.fi> <01QNLYA7BLVQ000051@mauve.mrochek.com> <83ddcadc-b756-91c1-3664-81955cd8f0d8@dovecot.fi> <01QTO3THVZ5I00AI1F@mauve.mrochek.com> <53350c64-d021-7f17-86b8-f1b118791cf5@dovecot.fi>
Message-ID: <67705936-3c03-30cd-bb39-95fa9673dae3@dovecot.fi>
Date: Sat, 04 Aug 2018 12:36:54 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <53350c64-d021-7f17-86b8-f1b118791cf5@dovecot.fi>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/CGYJUZFtc4TP-yHqG_3TsqHXnys>
Subject: Re: [Extra] I-D Action: draft-ietf-extra-sieve-special-use-01.txt
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2018 10:37:21 -0000

Hi Ned,


Op 18/07/2018 om 22:58 schreef Stephan Bosch:
> Op 13/06/2018 om 17:40 schreef Ned Freed:
>> I also reviewed the rest of the revised draft, and it's looking good. 
>> My one
>> remaining concern is with the handling of multiple mailboxes having the
>> same special-use flag assigned. The draft currently says:
>>
>>   More than one mailbox in the user's personal namespace can have a
>>   particular special-use flag assigned.  In case of such ambiguity, the
>>   mailbox that is chosen for delivery is implementation-defined.
>>   However, while the set of mailboxes to which the involved special-use
>>   flags are assigned remains unchanged, implementations MUST ensure
>>   that the mailbox choice is made consistently, so that the same
>>   mailbox is used every time.  Conversely, the chosen mailbox MAY
>>   change once the special-use flag assignments that are relevant for
>>   the mailbox choice are changed (usually by user interaction).
>>
>> I don't see a way I can reasonably implement this MUST via IMAP 
>> unless the IMAP server always returns the list of special-use 
>> mailboxes in the same order.
>> Sure, I can cache the user/special-use-attribute/actual-mailbox-list 
>> tuple
>> somewhere, but caches can always be lost. And mailbox metadata is (a)
>> Potentially much too expensive and (b) Subject to the vagarities of user
>> actions.
>>
>> I'm not happy about it, but I think this needs to become a SHOULD.
>
> Ok. I am not too attached to the MUST anyway.


Addressed here:

https://github.com/ietfextra/draft-ietf-extra-sieve-special-use/commit/024330130d5af6ff29e48ad137844cbe5fbf5243


>> Another possibility is to use the default mailbox name as a means of
>> disambiguating multiple mailboxes with the same special-use attribute:
>> If the default mailbox is one of these deliver to it preferentially,
>> otherwise the behavior is implementation-defined. Not perfect, but it
>> provides a bit more consistent behavior that's easily achievable.
>>
>
> Sounds like a good idea. I'll give this a closer look for the next 
> revision.

Addressed here:

https://github.com/ietfextra/draft-ietf-extra-sieve-special-use/commit/a1b8d4f83109424448b51b65fbc014a73a479997

Regards,

Stephan.