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

Mark Crispin <mrc+ietf@panda.com> Fri, 17 February 2012 21:11 UTC

Return-Path: <mrc+ietf@panda.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 3767321F85FD for <imap5@ietfa.amsl.com>; Fri, 17 Feb 2012 13:11:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 EOEphH0FwxpL for <imap5@ietfa.amsl.com>; Fri, 17 Feb 2012 13:10:56 -0800 (PST)
Received: from Panda.COM (panda.com [206.124.149.114]) by ietfa.amsl.com (Postfix) with ESMTP id 0233621F85F6 for <imap5@ietf.org>; Fri, 17 Feb 2012 13:10:50 -0800 (PST)
Received: from hsinghsing.panda.com ([206.124.149.116]) by Panda.COM ([192.107.14.50]) with ESMTP via TCP; Fri, 17 Feb 2012 13:10:39 -0800
X-MailFrom: mrc+ietf@panda.com
Date: Fri, 17 Feb 2012 13:10:37 -0800
From: Mark Crispin <mrc+ietf@panda.com>
Sender: mrc@hsinghsing.panda.com
To: Dan White <dwhite@olp.net>
In-Reply-To: <20120217200547.GB6908@dan.olp.net>
Message-ID: <alpine.OSX.2.00.1202171214230.38441@hsinghsing.panda.com>
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> <20120216224124.GC4578@dan.olp.net> <CABa8R6uxeFVSDQzzSS6ziV8b2roYdw38GMpjEm+1DGkhD3MdVg@mail.gmail.com> <20120216232954.GB5356@dan.olp.net> <4F3DA4A6.5020304@qbik.com> <20120217171457.GB4503@dan.olp.net> <20120217194059.GC32490@launde.brong.net> <20120217200547.GB6908@dan.olp.net>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
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: Fri, 17 Feb 2012 21:11:09 -0000

On Fri, 17 Feb 2012, Dan White wrote:
> I don't think the disconnected state really matters. The email could just
> sit in a local queue until it's reconnected to the network, at which point
> it could be send directly to the recipient's lmtp server (which makes
> better sense than direct imap, now that I think about it).

What if the network you are on requires you to use their servers, and
enforces that requirement through various evil means? Their policy may
allow external traffic going in, even from a remote IMAP server, but not
out. They even put themselves as a MITM on SSL/TLS (not that anyone pays
attention to cert validation messages anyway).

Outgoing email security: it's not just for totalitarian dictatorships any
more.

> Are the younger folks coming up today going to use email if the spam
> problem isn't solved? I doubt it. SMS and Facebook seem to suit most folks
> under age X (where X will continue to increase linearly over time).

I doubt that they will use email in any case. There is simply no
compelling reason for them to do so.

> imap, smtp, and even exchange are pretty much doomed to role of legacy
> enterprise application if that continues.

I agree with this statement other than the word "legacy". Email originated
as an enterprise application and was designed as to be an enterprise
application. To date, nothing has filled that niche.

Attempts to create FB-style applications for the enterprise have not done
well. One problem is that enterprises are reluctant to turn internal data
over to "the cloud". Those that have done so (primarily academia) are in
the process of learning some hard lessons.

> I don't really even think there needs to be a change to the basic imap/lmtp
> specifications to support my grandios plan for eradicating spam (although
> I'm far from the first to have such a light bulb go off).

This is a definite "well, duh!" statement. You are correct; eliminating
spam is not a correct motivation.

> As soon as the
> appropriate sasl mechanisms are in place to support some federated
> authentication (think authentication against Facebook), then all that's
> left is to improve ACL support in servers and clients. Simple matter...

"Small matter of programming".

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.