IETF Logo Mail Archive

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

Tony Hansen <tony@att.com> Thu, 23 February 2012 15:44 UTC

Return-Path: <tony@att.com>
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 62FA521F8823 for <imap5@ietfa.amsl.com>; Thu, 23 Feb 2012 07:44:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.152
X-Spam-Level:
X-Spam-Status: No, score=-106.152 tagged_above=-999 required=5 tests=[AWL=0.447, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 awrGHB3yi7C7 for <imap5@ietfa.amsl.com>; Thu, 23 Feb 2012 07:44:08 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEE621F8820 for <imap5@ietf.org>; Thu, 23 Feb 2012 07:44:08 -0800 (PST)
X-Env-Sender: tony@att.com
X-Msg-Ref: server-6.tower-119.messagelabs.com!1330011847!17019378!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.5.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10971 invoked from network); 23 Feb 2012 15:44:07 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-6.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 23 Feb 2012 15:44:07 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q1NFibeU010310 for <imap5@ietf.org>; Thu, 23 Feb 2012 10:44:37 -0500
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q1NFiWe4010174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <imap5@ietf.org>; Thu, 23 Feb 2012 10:44:33 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <imap5@ietf.org>; Thu, 23 Feb 2012 10:44:00 -0500
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q1NFhxl3023684 for <imap5@ietf.org>; Thu, 23 Feb 2012 10:43:59 -0500
Received: from dns.maillennium.att.com (mailgw1.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q1NFhvAA023647 for <imap5@ietf.org>; Thu, 23 Feb 2012 10:43:58 -0500
Received: from [135.70.166.212] (vpn-135-70-166-212.vpn.mwst.att.com[135.70.166.212]) by maillennium.att.com (mailgw1) with ESMTP id <20120223154136gw100e4lm0e> (Authid: tony); Thu, 23 Feb 2012 15:41:36 +0000
X-Originating-IP: [135.70.166.212]
Message-ID: <4F465EBC.7090206@att.com>
Date: Thu, 23 Feb 2012 10:43:56 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: imap5@ietf.org
References: <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> <alpine.LSU.2.00.1202171127330.30682@hermes-2.csi.cam.ac.uk> <4F3F4F8F.3040601@qbik.com> <1329550573.30138.140661038121885@webmail.messagingengine.com> <alpine.LSU.2.00.1202191832430.12769@hermes-2.csi.cam.ac.uk> <20120219192604.GA11323@launde.brong.net> <alpine.LSU.2.00.1202201048480.31357@hermes-2.csi.cam.ac.uk> <4F465269.1040901@flaska.net>
In-Reply-To: <4F465269.1040901@flaska.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
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: Thu, 23 Feb 2012 15:44:09 -0000

Totally off topic: I wish I knew how to get them to fix that. I get bit 
by it regularly.

On topic: because gmail messes up in this area doesn't mean that we 
should also mess things up in the same way.

I am a firm believer in the use of message/rfc822 attachments.

     Tony Hansen

On 2/23/2012 9:51 AM, Jan Kundrát wrote:
> On 02/20/12 11:52, Tony Finch wrote:
>> message/rfc822 is also good. IMO every message that is forwarded or
>> top-post replied should use message/rfc822 attachments rather than doing
>> some fucked up redaction of the original message.
> GMail still breaks [1] on such messages -- the web interface shows the
> message source and the IMAP server returns invalid BODYSTRUCTURE which
> doesn't allow accessing the attached message.
>
> Cheers,
> Jan
>
> [1] http://permalink.gmane.org/gmane.mail.imap.general/2637

v2.23.0 | Report a Bug | By Email