IETF Logo Mail Archive

Re: [Extra] imap4rev2: disallow "RENAME INBOX"

"Bron Gondwana" <brong@fastmailteam.com> Thu, 08 November 2018 14:53 UTC

Return-Path: <brong@fastmailteam.com>
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 832F0128BCC for <extra@ietfa.amsl.com>; Thu, 8 Nov 2018 06:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.982
X-Spam-Level:
X-Spam-Status: No, score=-1.982 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_HEADER_CTYPE_ONLY=0.717, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=x6tCdXac; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=sfg2Oyrt
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 qzGQZA1bmamn for <extra@ietfa.amsl.com>; Thu, 8 Nov 2018 06:53:53 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96C8512872C for <extra@ietf.org>; Thu, 8 Nov 2018 06:53:53 -0800 (PST)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id BE2192218B for <extra@ietf.org>; Thu, 8 Nov 2018 09:53:51 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute6.internal (MEProxy); Thu, 08 Nov 2018 09:53:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=message-id:in-reply-to:references:date:from :to:subject:content-type; s=fm1; bh=WBKxsbPGpQ65mjkZLMIKdl/nbGyh D2Nsoj5wVckcNqo=; b=x6tCdXacod1LNwJH/CJbGFrlOrk9GfoYeHdCTZQ6pMGq GkOC/jPxiBo7uUt7Us3p5feCkoihHxu3Y3R1HCDflXGnkG5mRIeIBhwhaMyGAwgg ydmKF4mAX+2Q3vxPgJICwvlUOQGDjcxFOGQiNIJACAs9d2RUPeMFTIerkGjLZEMa uZDRS2pnTU3xGBeTrGduLMsPV15xeZmdYqveEfrHneU+6UjkBZPsjXamun6daUoP 8p9rRY27pRe1YELk9EALtOcdPj/nMPJoCQ9RmKn2YjBUl5ZUneA2kRaLQu9TrrJC Fhnk+7K8PFqqM/6PB2nXjQZzLGEBGw2ABi7MjT94FQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=WBKxsbPGpQ65mjkZL MIKdl/nbGyhD2Nsoj5wVckcNqo=; b=sfg2OyrtKySKRZCytUty6d8QVwTtozZlg PbvFdM9cKtaOdtlqN/I/ewptFqeg3LMa5Hk1YVn02pxDRhjOb658gbhcYPbzTEqF VWP+o4xHys7GDLdpFGBLQ6v5L1KYdUsePCWPRFGPePh0ERl9prSCK+42GdiwMOG4 mSw+mXn9XnL0pkw5d0domXVuEm/pTZ8wRBeXiPAjTv8JWWD0jktSSh/V+artmZVr 82Tf41orMQkcIZtjCweUqhcPhYXeZxG1+pyjIAdl1uYdSGMTAUwywbQZJqLmvTuA 02YBrZVluHmnCuRzGXlEsZYsPueM0/2yab1qx63oWqQ4mglFLMrxw==
X-ME-Sender: <xms:_03kW4rfXDTJznp3L5kN8-eQIFCoVkaK-2bRVXwR7zhi1ZzG1q9fzA>
X-ME-Proxy: <xmx:_03kWxf4olCsUAZMVj8lXkMVaKntEg_O3luZLvP8SQ2nKlRG5KpqWA> <xmx:_03kW8BbKsrZm1ouVw_fhgu0TyTeB0FBqhCucJA_DZMzJGobhGFvbw> <xmx:_03kW-sVIQCKuQCp5xlgt9LzqkCrqHO0uITz6w_6jSsY7W8RnhoGbQ> <xmx:_03kW5HgCvMyqLDryFvodFWtRmGqsUHcPruPzTtgf9mWwejz2DFg9Q> <xmx:_03kWx2Z5zqaTuXyV7zczED9glCP7WYNe3HP5_9hDV_htftPhN3xdA> <xmx:_03kW--R0J0Uy8UgfWco08BG6449EX3pd2GbMORHWsj4mZKVf2p0HA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4400A2030B; Thu, 8 Nov 2018 09:53:51 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
Message-Id: <e9d5c860-937c-44e5-805e-0d1d7373d32a@sloti7d1t02>
User-Agent: Cyrus-JMAP/3.1.5-610-gd7ceb27-fmstable-20181026v1
X-Me-Personality: 56629417
In-Reply-To: <B43C5178-C640-44B9-9FEA-C5FF14DBD538@iki.fi>
References: <b8dc4684-e911-43b8-966e-fc845f2a515f@sloti7d1t02> <B43C5178-C640-44B9-9FEA-C5FF14DBD538@iki.fi>
Date: Thu, 08 Nov 2018 09:53:50 -0500
From: Bron Gondwana <brong@fastmailteam.com>
To: extra@ietf.org
Content-Type: multipart/alternative; boundary="30ea17d16b3f494c924612197b2e8506"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/i11Dgak6zMSkF-LKXRjgAAl9OhE>
Subject: Re: [Extra] imap4rev2: disallow "RENAME INBOX"
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 08 Nov 2018 14:53:56 -0000

I'm tempted to see what Gmail does too. 
 
. OK brongondwana@gmail.com authenticated (Success) 
. rename INBOX oldinbox 
. OK Success 
 
Well, what do you know. They implemented it! 
 
ha... 
 
. select oldinbox 
. move 1:* INBOX 
 
...  
 
. OK [COPYUID 2 1:15214 16312:31525] (Success) 
 
So it looks like it didn't reset the UID counter on the INBOX. I didn't get the UIDVALIDITY of the INBOX at the start to compare. 
 Bron. 
 
On Fri, Nov 9, 2018, at 01:02, Timo Sirainen wrote: 
> On 8 Nov 2018, at 13.37, Bron Gondwana <brong@fastmailteam.com> wrote: 
>>  
>> This is one of the open issues from imap4rev2 - which extensions should be part of the mandatory baseline. 
>>  
>> This one came from me. I dislike the weirdness of "RENAME INBOX Archive-foo" because of its special behaviour regarding sub mailboxes, and the auto-recreation of the source mailbox, and all that jazz. 
>>  
>> Argument in favour of keeping it - it's easier for clients, which is part of the point of IMAP4rev2 - servers have already suffered through this the first time, and will need to keep IMAP4rev1 support for a while anyway probably. 
>>  
>> Arguments for and against in response to this please. Also arguments about the suggested middleground saying that clients "SHOULD NOT" use it, or something like that - with the flip side that servers MAY reject rename of INBOX. 
>>  
>> We're particularly interested in "I use this, and want to keep it" from either servers that see their clients doing it, client authors, or even users! 
> Dovecot has always been rejecting this when used with Maildir format (other formats allow it): 
>  
> a rename inbox plop 
> a NO [CANNOT] Renaming INBOX isn't supported (0.001 + 0.000 secs). 
>  
> I've never heard anyone complain about it. 
>  
> I've a feeling Courier is rejecting it as well, but can't check now easily. 
>  
> _______________________________________________ 
> Extra mailing list 
> Extra@ietf.org 
> https://www.ietf.org/mailman/listinfo/extra 
>  
 
-- 
 Bron Gondwana, CEO, FastMail Pty Ltd 
 brong@fastmailteam.com

v2.23.0 | Report a Bug | By Email