From: David Engster <deng@randomsample.de>
To: Tassilo Horn <tsdh@gnu.org>
Cc: ding@gnus.org
Subject: Re: A new open email standard: https://jmap.io/
Date: Fri, 27 Dec 2019 20:46:08 +0100 [thread overview]
Message-ID: <878smxft6n.fsf@randomsample> (raw)
In-Reply-To: <87fth5ixyr.fsf@gnu.org> (Tassilo Horn's message of "Fri, 27 Dec 2019 16:34:36 +0100")
>>> https://fastmail.blog/2019/08/16/jmap-new-email-open-standard/
>>> https://jmap.io/
>>
>> They try to establish this for many years now, but I don't see it
>> taking off. It surely has nice features for mobile users, but people
>> use messengers there anyway. For Gnus, I don't think you'd notice much
>> difference over IMAP. But first they would have to get this into an
>> actual popular IMAP server (meaning: Dovecot). Until then, this is
>> pretty much a Fastmail-only thing.
>
> Cyrus 3.0.0 to 3.0.5 supported some earlier draft but the support was
> removed with 3.0.6 because the spec evolved too rapidly for a stable
> version. But the docs say that the development version supports the
> current JMAP version.
>
> https://cyrusimap.org/imap/developer/jmap.html
I know. FastMail uses Cyrus and they have also pretty much adopted the
whole project since Carnegie Mellon Uni switched to Exchange and GMail,
so it's pretty much given that it always supports latest JMAP. But if
you need a pure IMAP server, Dovecot is usually the first choice
nowadays, so if they want JMAP to succeed, they *really* need to get
this in there. I know they're working on this, but I'm guessing it's not
easy getting code into Dovecot.
-David
prev parent reply other threads:[~2019-12-27 19:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 21:20 Tassilo Horn
2019-12-27 3:15 ` 황병희
2019-12-27 11:56 ` David Engster
2019-12-27 15:34 ` Tassilo Horn
2019-12-27 19:46 ` David Engster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878smxft6n.fsf@randomsample \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=tsdh@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).