IETF Logo Mail Archive

Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP

Bron Gondwana <brong@fastmail.fm> Fri, 17 February 2012 03:58 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 2837D21E804E for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 19:58:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.567
X-Spam-Level:
X-Spam-Status: No, score=-3.567 tagged_above=-999 required=5 tests=[AWL=0.032, 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 B8vFxAY5iHt4 for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 19:58:03 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1C521E8056 for <imap5@ietf.org>; Thu, 16 Feb 2012 19:58:03 -0800 (PST)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id ACCCE2069C for <imap5@ietf.org>; Thu, 16 Feb 2012 22:58:02 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 16 Feb 2012 22:58:02 -0500
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=ywanNmnWevoFJBbRcHDzRg1f NVg=; b=bUmsxi9CLP+Nou5h+kuD27KT2CqwF5HHG3ayIw6A/MaN1kEkH6ddTAUq 3Ur+rOsQLyuptFONBpAd3/JbnuY7d66ggOCQbb2Uxch4h+TBtyHcGwdGQ2w5E7er KX8mrlyqO9mZcUTIEX6ypNWVWC6zyhzia/ldVVIdZYA9SrqoeB8=
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=ywanNmnWevoFJBbRcHDzRg1fNVg=; b=ucCsscvFNoj/b0vOq79Q3Kmn7sRm uHlI/BRIpuT2bqX4A95s+Xztkw/GJNUKCYxBckzfzuxWVss3LD34JtgkDLp18yqD 68YzFBJ1zZzkOrzxPOn8EIYG8qj/zgO/5AJcySYZsa5gsz/QqWskGYp0/bw8mZrM yU+npzEcMIrd9bo=
X-Sasl-enc: ZvufP4P3TlQSgh98A7T0hjF0y9LqA7h7vJcvY1+TharZ 1329451082
Received: from localhost (99.249.9.46.customer.cdi.no [46.9.249.99]) by mail.messagingengine.com (Postfix) with ESMTPSA id 32BE08E0162; Thu, 16 Feb 2012 22:58:02 -0500 (EST)
Received: by localhost (Postfix, from userid 1000) id B40F82260C2; Fri, 17 Feb 2012 04:58:00 +0100 (CET)
Date: Fri, 17 Feb 2012 04:58:00 +0100
From: Bron Gondwana <brong@fastmail.fm>
To: Mark Crispin <mrcrispin@panda.com>
Message-ID: <20120217035800.GA25362@launde.brong.net>
References: <3077.1329388899.383165@puncture> <4F3CE16B.3060603@qbik.com> <3077.1329391344.173214@puncture> <4F3CEB35.9080200@qbik.com> <1329394296.953.140661037317197@webmail.messagingengine.com> <4F3CFD35.10501@qbik.com> <alpine.LSU.2.00.1202161626400.30682@hermes-2.csi.cam.ac.uk> <4F3D6E57.8010301@qbik.com> <20120216223724.GD24183@launde.brong.net> <alpine.OSX.2.00.1202161440010.38441@hsinghsing.panda.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.00.1202161440010.38441@hsinghsing.panda.com>
Organization: brong.net
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: imap5@ietf.org
Subject: Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP
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: Fri, 17 Feb 2012 03:58:08 -0000

On Thu, Feb 16, 2012 at 02:48:41PM -0800, Mark Crispin wrote:
> On Thu, 16 Feb 2012, Bron Gondwana wrote:
> >>I think the guys that developed SMTP would disagree with you.  The
> >>reason the envelope is even specified in SMTP rather than the
> >>receiver simply scraping them out of the message, is that sometimes
> >>you need to deliver a message somewhere other than the To: / bcc:
> >>headers.
> >Rarely.  I don't even know an IMAP client which supports doing that.
> 
> HAHAHAHAHAHAHAHAHAHAHAHAHAHA.

I have not heard of this IMAP client.  Please provide usage stats
to help a determination if it's a significant player that we need
to plan around.

Thanks,

Bron.

v2.23.0 | Report a Bug | By Email