IETF Logo Mail Archive

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

Brandon Long <blong@google.com> Thu, 16 February 2012 22:53 UTC

Return-Path: <blong@google.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 BC0CE21E803D for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 14:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 RefVifWMnqUS for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 14:53:19 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 243C721E801C for <imap5@ietf.org>; Thu, 16 Feb 2012 14:53:18 -0800 (PST)
Received: by qan41 with SMTP id 41so2970224qan.10 for <imap5@ietf.org>; Thu, 16 Feb 2012 14:53:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-system-of-record; bh=g7WnbzcYe1i9yJWrtmpggZO/8sfoDu/MTchRIC4AwVI=; b=miwmnb8o8pdij0nY44KxdpZqJqPmXqyUIU824EqNsB54Op6Ane6VF4C/MzRysEQbOo 5XPy0yRIDi4Gfxj2cvfN1RimrC4zgjqOn5cIomuPwsypIIYm69EElCuJMfnd1ekCYOxs z7Tb+d9aEqr517kvdRByrDkZ6TYUVi7BUTJTY=
Received: by 10.229.135.11 with SMTP id l11mr3097062qct.140.1329432798570; Thu, 16 Feb 2012 14:53:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.135.11 with SMTP id l11mr3097051qct.140.1329432798430; Thu, 16 Feb 2012 14:53:18 -0800 (PST)
Received: by 10.229.216.201 with HTTP; Thu, 16 Feb 2012 14:53:18 -0800 (PST)
In-Reply-To: <20120216223724.GD24183@launde.brong.net>
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>
Date: Thu, 16 Feb 2012 14:53:18 -0800
Message-ID: <CABa8R6uKP+i=N0tZq1fwTB_ACsRjpQiN62az0h626jBrAVHrtQ@mail.gmail.com>
From: Brandon Long <blong@google.com>
To: Bron Gondwana <brong@fastmail.fm>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQnCoMOFJ4//zcy0bPL1hm7XQX9kfyV6QM6EqBo3rDC3Vn+Ndzr+PO5TeJSnEwd9cZgUcGZcOIS5dfbFMysP73Muws3hJt6ihd+WTGsq73rg8JfLOfWxP0ps0JO407VHXAK8TQga
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, "Discussion on drastically slimming-down IMAP." <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: Thu, 16 Feb 2012 22:53:19 -0000

On Thu, Feb 16, 2012 at 2:37 PM, Bron Gondwana <brong@fastmail.fm> wrote:
> On Fri, Feb 17, 2012 at 10:00:07AM +1300, Adrien de Croy wrote:
>>
>>
>> On 17/02/2012 5:40 a.m., Tony Finch wrote:
>> >Adrien de Croy<adrien@qbik.com>  wrote:
>> >>>With XSEND, you upload the message to IMAP first, then you say:
>> >>>
>> >>>TAG XSEND UID
>> >>how do you provide the SMTP forward path?  Is that scraped from the headers?
>> >That's the right thing to do. You also need to do BCC: processing.
>> >(sendmail -t does the right thing.)
>>
>> 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.
> It's not like SMTP would disappear if you need something more complex.

mutt comes to mind, though its not doing it through SMTP but via
arguments to sendmail.  Well, maybe it does support them with the
newer built-in smtp submission.

Brandon

v2.23.0 | Report a Bug | By Email