IETF Logo Mail Archive

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

Sebastian Hagedorn <Hagedorn@uni-koeln.de> Sun, 19 February 2012 19:36 UTC

Return-Path: <Hagedorn@uni-koeln.de>
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 6F56521F8540 for <imap5@ietfa.amsl.com>; Sun, 19 Feb 2012 11:36:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.853
X-Spam-Level:
X-Spam-Status: No, score=-0.853 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_QP_LONG_LINE=1.396]
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 Vom8PHfhOa4V for <imap5@ietfa.amsl.com>; Sun, 19 Feb 2012 11:36:10 -0800 (PST)
Received: from smtp-out.rrz.uni-koeln.de (smtp-out.rrz.uni-koeln.de [134.95.19.53]) by ietfa.amsl.com (Postfix) with ESMTP id 7385521F84F8 for <imap5@ietf.org>; Sun, 19 Feb 2012 11:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at uni-koeln.de
Received: from smtp-auth.rrz.uni-koeln.de (smtp-auth.rrz.uni-koeln.de [134.95.19.93]) by smtp-out.rrz.uni-koeln.de (8.13.8/8.13.8) with ESMTP id q1JJa51F032005; Sun, 19 Feb 2012 20:36:05 +0100
X-AUTH-SIP: a0620@vpn83-106.vpn.uni-koeln.de [134.95.83.106]
Received: from vpn83-106.vpn.uni-koeln.de (vpn83-106.vpn.uni-koeln.de [134.95.83.106]) (authenticated as user a0620 using DIGEST-MD5 bits=0) by smtp-auth.uni-koeln.de (8.13.8/8.13.8) with ESMTP id q1JJa3J3013067; Sun, 19 Feb 2012 20:36:04 +0100
Date: Sun, 19 Feb 2012 20:35:57 +0100
From: Sebastian Hagedorn <Hagedorn@uni-koeln.de>
To: Bron Gondwana <brong@fastmail.fm>
Message-ID: <23AD106590F87A8C01A33FE4@vpn83-106.vpn.uni-koeln.de>
In-Reply-To: <20120219192604.GA11323@launde.brong.net>
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>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
Message-Context: text-message
X-Spook: nuclear nuke spy secret assassination cia fbi nsa president
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="sha1"; protocol="application/pkcs7-signature"; boundary="==========4D97E95B55BF97F17D17=========="
X-Scanned-By: MIMEDefang 2.71 on 134.95.19.53
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 19:36:11 -0000

> 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.

>  You're
> much better off forming a new message.

No, because the idea is precisely to preserve the original headers.

> 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...".
--
Sebastian Hagedorn - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10
Regionales Rechenzentrum (RRZK)
Universität zu Köln / Cologne University - Tel. +49-221-478-5587

v2.23.0 | Report a Bug | By Email