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

Bron Gondwana <brong@fastmail.fm> Fri, 17 February 2012 21:35 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 A130521F85CF for <imap5@ietfa.amsl.com>; Fri, 17 Feb 2012 13:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.546
X-Spam-Level:
X-Spam-Status: No, score=-3.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 fjFGygun-bJT for <imap5@ietfa.amsl.com>; Fri, 17 Feb 2012 13:35:26 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id BBAF421F85CD for <imap5@ietf.org>; Fri, 17 Feb 2012 13:35:26 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6AFAD210E3 for <imap5@ietf.org>; Fri, 17 Feb 2012 16:35:26 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 17 Feb 2012 16:35:26 -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=2wVIKiCOPX8GxQs47yHCVJNF Npk=; b=QafcBJxl/ReTGtBik//Zu4io95DykKiiuw4aD+uSByTgk2B3rYDvtu5T a+rzf6zDCfue71I/C0bxROkEsjvCJwe4JuS9G1onA9YmWQRcT3uYJLoChwGT35TL EyftfL8yVQ+qBoFmSZiI2i1GcpfxV4Ys4GOg4rNe8mcI/Y89JCo=
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=2wVIKiCOPX8GxQs47yHCVJNFNpk=; b=EQTwO9ALQezaBKDtVfZg+IR6+6t0 v2XxmZ4lA+moRKmyA9teTIRPqSKrrI/S+YyzaK/jv9C/Q4vsBqzhcphal/S9Bzl4 Ef54cdqJtGrnKdWlqMqMr0/kP6YmSzuXU4KTlTRr3ACnMFmbgKgumVoFCspxkeYW QNSbj0Xyu2pc5CM=
X-Sasl-enc: HMLSBKzD2IWDd/HjS1k9uEAFP2FXM/Im7ql3xigGXCSe 1329514526
Received: from localhost (99.249.9.46.customer.cdi.no [46.9.249.99]) by mail.messagingengine.com (Postfix) with ESMTPSA id 209178E00D5; Fri, 17 Feb 2012 16:35:26 -0500 (EST)
Received: by localhost (Postfix, from userid 1000) id B26DA2260D2; Fri, 17 Feb 2012 22:35:24 +0100 (CET)
Date: Fri, 17 Feb 2012 22:35:24 +0100
From: Bron Gondwana <brong@fastmail.fm>
To: Mark Crispin <mrc+ietf@panda.com>
Message-ID: <20120217213524.GB1084@launde.brong.net>
References: <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> <alpine.OSX.2.00.1202171214230.38441@hsinghsing.panda.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.OSX.2.00.1202171214230.38441@hsinghsing.panda.com>
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: Fri, 17 Feb 2012 21:35:27 -0000

On Fri, Feb 17, 2012 at 01:10:37PM -0800, Mark Crispin wrote:
> 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).

Sounds pretty easy to do with a nice proxyable protocol, they just block
it, and you need to use a client which supports sending to an SMTP server.

Hopefully a relatively rare case.

Rarely enough, I agree with the rest of what you said, so I won't leave
it inline with a bunch of m3t00.

Bron.