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

Bron Gondwana <brong@fastmail.fm> Sun, 19 February 2012 22:01 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 4BDCA21F8523 for <imap5@ietfa.amsl.com>; Sun, 19 Feb 2012 14:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.55
X-Spam-Level:
X-Spam-Status: No, score=-3.55 tagged_above=-999 required=5 tests=[AWL=0.049, 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 kwD1xTy9YJPv for <imap5@ietfa.amsl.com>; Sun, 19 Feb 2012 14:01:15 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 956A021F84D4 for <imap5@ietf.org>; Sun, 19 Feb 2012 14:01:15 -0800 (PST)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 377C32166F for <imap5@ietf.org>; Sun, 19 Feb 2012 17:01:15 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Sun, 19 Feb 2012 17:01:15 -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=/RYXKWkp0JYIIlpx5D5jret7 7UA=; b=c7gQhoXs6fON+L0N8mT2P443PPXWA4CJ//C+QD/UZO6SB5QG3VoYr5Qq 5pKAiUbxPs0OPprMihbpUXSWYsqvR+urbyNJLDCOagY+pIb6nnEmGFfmrSx0Q4VF +TzYLAGipZ2KCyL8dW5kMyqqRVKRjXX4sjdqubILZDcqaesMLQQ=
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=/RYXKWkp0JYIIlpx5D5jret77UA=; b=q65ApB+dgP4uXkHeWemjh5WdBur7 aMmjrWfyfINZs4C7MxURrY+XviJXIjXcx5CYYYYFxXJKCa1MaVmwp4+J+H5sH1NF 0jIoc7g89njvCS8pkX9Du9Ke34ATxGBRBM65Y2isEM0nPwqSHmwKNJBzJOGjSrG2 rK/hpo1tNJxDwGI=
X-Sasl-enc: IRSi9L4WF16GH+iSKm9kaqrSIzSeczcTjFkSos9YBftB 1329688874
Received: from localhost (99.249.9.46.customer.cdi.no [46.9.249.99]) by mail.messagingengine.com (Postfix) with ESMTPSA id E6BF448250B; Sun, 19 Feb 2012 17:01:14 -0500 (EST)
Received: by localhost (Postfix, from userid 1000) id 634AA316B81; Sun, 19 Feb 2012 23:01:13 +0100 (CET)
Date: Sun, 19 Feb 2012 23:01:13 +0100
From: Bron Gondwana <brong@fastmail.fm>
To: Sebastian Hagedorn <Hagedorn@uni-koeln.de>
Message-ID: <20120219220113.GA12549@launde.brong.net>
References: <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> <23AD106590F87A8C01A33FE4@vpn83-106.vpn.uni-koeln.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <23AD106590F87A8C01A33FE4@vpn83-106.vpn.uni-koeln.de>
Organization: brong.net
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: "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: Sun, 19 Feb 2012 22:01:17 -0000

On Sun, Feb 19, 2012 at 08:35:57PM +0100, Sebastian Hagedorn wrote:
> >I've seen the argument of "what if you want to forward a copy on to
> >someone else for inspection, whatever" - without forming a new copy
> >of the message.  That's actually really hard to do in the current
> >universe, because the headers will make it look extra spammy.
> 
> Not necessarily. I just resent your message to myself. Mulberry, IMO
> still the best email client, adds the following headers:
                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^

> Resent-Date: Sun, 19 Feb 2012 20:30:30 +0100
> Resent-From: Sebastian Hagedorn <Hagedorn@uni-koeln.de>
> Resent-To: Sebastian Hagedorn <Hagedorn@spinfo.uni-koeln.de>
> Resent-Message-ID: <54B00D8CBCD7BCEB1191BE44@vpn83-106.vpn.uni-koeln.de>
> X-Resent-Mailer: Mulberry/4.1.0a1 (Mac OS X)
> 
> Doesn't look spammy at all, because it's completely clear what has
> happened. I use that feature all the time.

Doesn't sound like it's the same IMAP UID to me.

So it looks like using "Resent-To" rather than "To" if Resent-To
exists handily covers your usecase.

> > You're
> >much better off forming a new message.
> 
> No, because the idea is precisely to preserve the original headers.

Sounds like you're forming a new RFC822 message stored on the server
rather than redirecting the actual original bytes...

> >Again, I really think it's the rare case.  I'd rather not complicate
> >message sending (and knowing which recipients had the message sent
> >to them) for this case.  There will still be SMTP.  Most clients
> >don't provide it for good reason - it's weird, advanced,
> >non-intuative stuff.  Do Exchange or Facebook provide such interfaces?
> 
> Facebook not, but Outlook/Exchange does ... it's called "Resend This
> Message...".

Do they attach the original?  Is the destination address stored in
a header somewhere in the saved copy so that you can see it?  Assuming
that information is stored somewhere, requiring it to be so and
parsing from that rather than extending the command is much cleaner.
It provides an audit trail of sorts.

Bron.