Re: [imap5] ERASE command as part of MOVE

Bron Gondwana <brong@fastmail.fm> Sat, 02 June 2012 04:12 UTC

Return-Path: <brong@fastmail.fm>
X-Original-To: imap5@ietfa.amsl.com
Delivered-To: imap5@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7DB221F889A for <imap5@ietfa.amsl.com>; Fri, 1 Jun 2012 21:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level:
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BS9K3rjgdDcL for <imap5@ietfa.amsl.com>; Fri, 1 Jun 2012 21:12:22 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 1568B21F8895 for <imap5@ietf.org>; Fri, 1 Jun 2012 21:12:22 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BFC2C20D69; Sat, 2 Jun 2012 00:12:21 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Sat, 02 Jun 2012 00:12:21 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=mesmtp; bh=ws7rSEWamvltyQslD3pNdBYq JOw=; b=OyUdZ0GNzDN22Bk32dz66wxXjbua/AwVAOSPNSkCqKBWt+affbPyU40y RXq3S/PutPZW1c4o0rK8lPw5uxSNsJHX9UbD6JssZ9O6DpboqlJYkN/8j28VF6be wmeOXkps+JIIxaJSW7BShCy2OX8VmDLvGP8Ic0l4EL+qneGMFzw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=smtpout; bh=ws7rSEWamvltyQslD3pNdBYqJOw=; b=EZf/DQIUFnuzz22vp8C5/db6yhSP dE77ZUnp3npqe09YnEYYmk1AvEuFSbXQkqSVSqZdNKuYIyizyOsLw0tUnDXgL4bJ gPYsy+62ajW5VE9GivrDRHSVr73QOKmmRCrAVN9WF0ytvqKLBtWxuHg8Ihgl2gCE Nus3C110Lm4qIqA=
X-Sasl-enc: ovw66/M8ERbZGujDiLiz5gDziFTW8G5e+kFR1Owxix81 1338610341
Received: from localhost (unknown [31.45.20.151]) by mail.messagingengine.com (Postfix) with ESMTPA id 73A5A8E012F; Sat, 2 Jun 2012 00:12:21 -0400 (EDT)
Received: by localhost (Postfix, from userid 1000) id EC4A17E00BD; Sat, 2 Jun 2012 06:12:21 +0200 (CEST)
Date: Sat, 02 Jun 2012 06:12:21 +0200
From: Bron Gondwana <brong@fastmail.fm>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <20120602041221.GB2654@launde.brong.net>
References: <20120601222311.GB598@launde.brong.net> <CAC4RtVBrM2fY7GGM1s-NRhKMU48NSOMMtkMVqnQ_zbbLnBtM_A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAC4RtVBrM2fY7GGM1s-NRhKMU48NSOMMtkMVqnQ_zbbLnBtM_A@mail.gmail.com>
Organization: brong.net
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, imap5@ietf.org
Subject: Re: [imap5] ERASE command as part of MOVE
X-BeenThere: imap5@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion on drastically slimming-down IMAP." <imap5.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imap5>, <mailto:imap5-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imap5>
List-Post: <mailto:imap5@ietf.org>
List-Help: <mailto:imap5-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imap5>, <mailto:imap5-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Jun 2012 04:12:23 -0000

On Fri, Jun 01, 2012 at 09:54:54PM -0400, Barry Leiba wrote:
> But more to the point: you'll note that the proposed charter is VERY
> tight on this, and will not be changed... there is exactly ONE thing
> chartered here, and an ERASE command is not it.  This is quite
> intentional, to head off tangents and feature creep, and to keep us to
> the thing that's being demanded by, we're told, a significant number
> of implementors.

It just happens to include an ERASE command.
 
> Please do not try to add anything more to this very tightly focused effort.

Fair enough.  I'm sure there's a good reason for being this hard-assed
about not changing things.  It's hardly the first time MOVE has been
suggested, and somehow it's managed to not make the difference every
other time (which is probably why there's an incompatible AOL one
already.  I'm kinda suprised gmail didn't do one as well - though I
guess they work around it with keyword fiddling instead if they know
they're talking to their own server)

I'm still going to write it locally because it's a single instruction
which describes the exact intention to the server.

Bron.