IETF Logo Mail Archive

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

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Fri, 17 February 2012 09:10 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 0EA4321F868C for <imap5@ietfa.amsl.com>; Fri, 17 Feb 2012 01:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.462
X-Spam-Level:
X-Spam-Status: No, score=-2.462 tagged_above=-999 required=5 tests=[AWL=0.137, BAYES_00=-2.599]
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 BRr+AYGuPpoD for <imap5@ietfa.amsl.com>; Fri, 17 Feb 2012 01:10:17 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) by ietfa.amsl.com (Postfix) with ESMTP id BA23421F8828 for <imap5@ietf.org>; Fri, 17 Feb 2012 01:10:17 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (unknown [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 4B7E5F8C967; Fri, 17 Feb 2012 09:10:13 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.4) with esmtpsa id 1329469812-12558-12558/10/25; Fri, 17 Feb 2012 09:10:12 +0000
Message-Id: <4F3E1999.4050703@gulbrandsen.priv.no>
Date: Fri, 17 Feb 2012 10:10:49 +0100
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111229 Thunderbird/9.0
Mime-Version: 1.0
To: imap5@ietf.org
References: <3077.1329386263.642278@puncture> <4F3CD728.3010203@qbik.com> <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>
In-Reply-To: <20120216223724.GD24183@launde.brong.net>
Content-Type: text/plain; charset="iso-8859-1"
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 09:10:19 -0000

On 02/16/2012 11:37 PM, 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.

Some remove Bcc themselves, or never add it. That is, even though the
word 'Bcc' may be visible onscreen, it does not occur in the submitted
message.

Arnt

v2.23.0 | Report a Bug | By Email