wasm-demo/demo/ermis-f/imap-protocol/cur/1600095128.22772.mbox:2,S

36 lines
1.5 KiB
Plaintext

MBOX-Line: From brong at fastmail.fm Fri May 27 04:37:47 2011
To: imap-protocol@u.washington.edu
From: Bron Gondwana <brong@fastmail.fm>
Date: Fri Jun 8 12:34:46 2018
Subject: [Imap-protocol] History question.
In-Reply-To: <alpine.DEB.2.00.1105271149090.7253@pckoug1.intranet.GR>
References: <4DDEA412.6030305@aol.com> <4DDEDDD6.1040507@logicprobe.org>
<alpine.BSO.2.00.1105261628370.892@morgaine.smi.sendmail.com>
<2CB073A1-B421-4CFB-AE30-B17005C876A0@iki.fi>
<alpine.DEB.2.00.1105271149090.7253@pckoug1.intranet.GR>
Message-ID: <20110527133747.058ae231@arbre.eng.oslo.osa>
On Fri, 27 May 2011 11:53:40 +0300 (EEST)
John Kougoulos <koug@intracom.gr> wrote:
> On Fri, 27 May 2011, Timo Sirainen wrote:
>
> > I've noticed there are many people who want web 2.0 kind of interface to
> > emails (xml/ajax/dunno), and I've been thinking maybe I might just as
> > well do something like that. I'm sure the protocol will suck, but if it
> > gets us better email clients maybe it's a good thing overall. (And why
> > aren't they just using IMAP? Because they're scared of even trying to
> > use it. Hmm. IMAP over XML maybe?..)
> >
>
> Communigate has done something similar, see:
> http://www.communigate.com/cgatepro/XMLAPI.html#Mailbox
We have a JSON API that may get polished up into something releasable
at some point. I tried to keep it mirroring QRESYNC as closely as
possible, but unfortunately message sequence numbers are pretty useless
when your basic unit isn't a message, it's a cross-folder conversation.
Bron.