Re: [imap5] Designing a new replacement protocol for IMAP

Cyrus Daboo <cyrus@daboo.name> Fri, 10 February 2012 15:48 UTC

Return-Path: <cyrus@daboo.name>
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 35FD911E8088 for <imap5@ietfa.amsl.com>; Fri, 10 Feb 2012 07:48:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.072
X-Spam-Level:
X-Spam-Status: No, score=-102.072 tagged_above=-999 required=5 tests=[AWL=-0.869, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 0iUmmhlcfoXZ for <imap5@ietfa.amsl.com>; Fri, 10 Feb 2012 07:48:42 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0A83B11E8076 for <imap5@ietf.org>; Fri, 10 Feb 2012 07:48:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 3A5EE21BAFB3; Fri, 10 Feb 2012 10:48:41 -0500 (EST)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oxIAOBnwqUNq; Fri, 10 Feb 2012 10:48:38 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id B1E4D21BAFA8; Fri, 10 Feb 2012 10:48:36 -0500 (EST)
Date: Fri, 10 Feb 2012 10:48:32 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Filip Navara <filip.navara@gmail.com>
Message-ID: <13042F851E6093B120D14B34@caldav.corp.apple.com>
In-Reply-To: <CAD8HnzyRuQ7xiwtSArk+WohnwKhG13-kAY3Gob_Bc6J5Z=zCBA@mail.gmail.com>
References: <1328732126.32086.140661033971485@webmail.messagingengine.com> <201202090820.28260.thomas@koch.ro> <4F337E61.5040702@qbik.com> <201202101544.51364.thomas@koch.ro> <833EE8EEE88E4ADE5CDDDADB@caldav.corp.apple.com> <CAD8HnzyRuQ7xiwtSArk+WohnwKhG13-kAY3Gob_Bc6J5Z=zCBA@mail.gmail.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline; size="864"
Cc: imap5@ietf.org
Subject: Re: [imap5] 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, 10 Feb 2012 15:48:44 -0000

Hi Filip,

--On February 10, 2012 4:29:25 PM +0100 Filip Navara 
<filip.navara@gmail.com> wrote:

> There already exists a standardized way to implement XMPP notifications
> on IMAP, although it is a bit cumbersome and I doubt anyone ever
> implemented it. 
>
>
> http://tools.ietf.org/html/rfc5435 (Sieve Notify)
> http://tools.ietf.org/html/rfc5550 (Lemonade IMAP profile)
>

The SIEVE notify solution only covers the case of message delivery into a 
mailstore (be it IMAP or POP). It won't cover the case of changes made 
directly to that store (e.g. and IMAP APPEND). Now there is the IMAP-SIEVE 
draft (<http://tools.ietf.org/id/draft-ietf-sieve-imap-sieve-02.txt>) which 
in theory allows notifications to be added to IMAP. That may be overboard 
for what is required here and it does not cover what needs to be done in 
other protocols.

-- 
Cyrus Daboo