Re: [Extra] imap4rev2: disallow "RENAME INBOX"
"Chris Newman" <chris.newman@oracle.com> Tue, 20 November 2018 22:00 UTC
Return-Path: <chris.newman@oracle.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 8DAFD130E16 for <extra@ietfa.amsl.com>; Tue, 20 Nov 2018 14:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.77
X-Spam-Level:
X-Spam-Status: No, score=-4.77 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=oracle.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 o0kYNpQau63y for <extra@ietfa.amsl.com>; Tue, 20 Nov 2018 14:00:29 -0800 (PST)
Received: from userp2130.oracle.com (userp2130.oracle.com [156.151.31.86]) (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 CAFE5130DEB for <extra@ietf.org>; Tue, 20 Nov 2018 14:00:29 -0800 (PST)
Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id wAKLreNc153563; Tue, 20 Nov 2018 22:00:11 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=from : to : cc : subject : date : message-id : in-reply-to : references : mime-version : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=YP7VNDpJfiSPJx5FFqBclB5sUnNBYOCVIawuEIz31Dc=; b=JOdj4vijRxcx2d5C8ZiIx64qBS925A02A7GjtD/w/LfENxQcnnUjN98bjN44X+94b2gR 2nJSbDZs/IJgz+J9nFTNf4eehcuhBj8xI9GPfm850GErRphGUuNMnXKdITVT3UoFTmQJ PMdUUhoC231Ci5E9+AjiXavkKLMxE3EN4tN/hH/9aTs92BMhmcUmz+RirkDsuiYnwBqA rPrP8OxHOtnoLidkp1KYea0U/kNiqI8+DlQBZM2TbTqjihnZrWdSiiUb1aqdoaVRQoO9 TIwGH/Y/XNkr4pAoMcWu57eUqn+U9fNqirfLGaKgt30V4g0LLofEcID8W0LXsAsZkp5d 5w==
Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp2130.oracle.com with ESMTP id 2ntadtxdrx-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 20 Nov 2018 22:00:10 +0000
Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by userv0021.oracle.com (8.14.4/8.14.4) with ESMTP id wAKM09Bh005082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 20 Nov 2018 22:00:10 GMT
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id wAKM09kX031064; Tue, 20 Nov 2018 22:00:09 GMT
Received: from [192.168.15.59] (/47.41.1.180) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 20 Nov 2018 14:00:09 -0800
From: Chris Newman <chris.newman@oracle.com>
To: extra@ietf.org
Cc: Bron Gondwana <brong@fastmailteam.com>
Date: Tue, 20 Nov 2018 14:00:07 -0800
X-Mailer: MailMate (1.12.1r5552)
Message-ID: <74E8A9EC-3569-443B-B6D9-CD76F0D3FA34@oracle.com>
In-Reply-To: <CABa8R6tVNxB0POhCoMX8jJuFysfP1=PAPiHfys=G=g01vfWLpg@mail.gmail.com>
References: <b8dc4684-e911-43b8-966e-fc845f2a515f@sloti7d1t02> <B43C5178-C640-44B9-9FEA-C5FF14DBD538@iki.fi> <e9d5c860-937c-44e5-805e-0d1d7373d32a@sloti7d1t02> <CABa8R6tVNxB0POhCoMX8jJuFysfP1=PAPiHfys=G=g01vfWLpg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9083 signatures=668683
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811200192
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/M0tuyur2MQO3EQpbZOQPYbsXJY8>
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: Tue, 20 Nov 2018 22:00:33 -0000
On 9 Nov 2018, at 11:25, Brandon Long wrote: > The things we didn't implement were things that were much harder > (substring > searching is probably the main one) A very good point. For IMAP4rev2, can we loosen the specified requirements for searching? At a minimum, I'd like to see word-based searching for message content to be considered valid by the standard (that is, a search for "ood" won't necessarily match a message containing the word "good"). - Chris > yes, we didn't reset the UID counter, I guess we could do that and the > uidvalidity, but the initial impl didn't have a good way to change the > underlying uidvalidity, so easier to leave the uid space the same. > > Brandon > > On Thu, Nov 8, 2018 at 6:54 AM Bron Gondwana <brong@fastmailteam.com> > wrote: > >> 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_extra&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=K_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=oP5PJjpDZQDR4dtwrheZ_EnhR-XlvT9UB5wDPKQ5Jko&s=Dh9CwBxeKEF6SBLq7LW_42yNKCwMt7jRk44kDdIx7J0&e= >> >> >> -- >> Bron Gondwana, CEO, FastMail Pty Ltd >> brong@fastmailteam.com >> >> >> _______________________________________________ >> Extra mailing list >> Extra@ietf.org >> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_extra&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=K_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=oP5PJjpDZQDR4dtwrheZ_EnhR-XlvT9UB5wDPKQ5Jko&s=Dh9CwBxeKEF6SBLq7LW_42yNKCwMt7jRk44kDdIx7J0&e= >> > _______________________________________________ > Extra mailing list > Extra@ietf.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_extra&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=K_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=oP5PJjpDZQDR4dtwrheZ_EnhR-XlvT9UB5wDPKQ5Jko&s=Dh9CwBxeKEF6SBLq7LW_42yNKCwMt7jRk44kDdIx7J0&e=
- [Extra] imap4rev2: disallow "RENAME INBOX" Bron Gondwana
- Re: [Extra] imap4rev2: disallow "RENAME INBOX" Timo Sirainen
- Re: [Extra] imap4rev2: disallow "RENAME INBOX" Bron Gondwana
- Re: [Extra] imap4rev2: disallow "RENAME INBOX" Brandon Long
- Re: [Extra] imap4rev2: disallow "RENAME INBOX" Chris Newman