User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0 Build ID: 20161129173726 Steps to reproduce: Learned about the existence of the new JMAP protocol. Also learned that the Dovecot author is working on adding support for it in 2.3 (current version is 2.2.27, so 2.3 can't be all that far away): http://www.dovecot.org/list/dovecot-news/2016-March/000313.html So, it (the new JMAP protocol) has legs. Actual results: Checked, didn't find an open bug/enhancement request for Thunderbird to add support for it, so here I am.
Severity: normal → enhancement
OS: Unspecified → All
Hardware: Unspecified → All
One issue here has been that JMAP is supposedly internally implemented at Fastmail, but they have not actually exposed the protocol fully yet to their actual accounts. There is a bit of a chicken and egg problem here, but it would be hard to develop the protocol without a working target. In anyone knows of an actual working target that would be good to hear about.
The question was just asked on 11/27, and Aki confirmed it is still targetd (but no firm commitment) for 2.3. I just asked if there is a git branch that someone can follow the WIP, will respond again if/when I get an answer.
(In reply to Kent James (:rkent) from comment #1) > One issue here has been that JMAP is supposedly internally implemented at > Fastmail, but they have not actually exposed the protocol fully yet to their > actual accounts. There is a bit of a chicken and egg problem here, but it > would be hard to develop the protocol without a working target. > > In anyone knows of an actual working target that would be good to hear about. Maybe someone knows someone at Fastmail and can ask them if they could expose a test account with full support for their JMAP implementation that TB devs could use for testing?
(In reply to Charles from comment #2) > The question was just asked on 11/27, and Aki confirmed it is still targetd > (but no firm commitment) for 2.3. > > I just asked if there is a git branch that someone can follow the WIP, will > respond again if/when I get an answer. Aki responded that they don't have anything available for beta testing yet, but hopefully will early next year...
There are more complete implementations than Dovecot, and so far the most complete one is the JMAP Proxy by Fastmail, placeable in front of an IMAP/CalDAV/CardDAV support and produces JMAP output, and currently supports the full specification. Fastmail are also working towards enabling JMAP support, so this may likely happen before Dovecot hits 2.3, and Cyrus is more likely to gain a full implementation as it is already a WIP before Dovecot does. I'd really recommend talking a look at this thread where all things JMAP are discussed: https://groups.google.com/forum/#!forum/jmap-discuss
Excellent, thanks. Does Fastmail offer a way for clients to test against their implementation? If not, maybe they would make an exception for Thunderbird. Although that would of course require someone to actually be working on the implementation. And thanks for the link to the discussion group.
My pleasure. I don't believe they do, currently - but they have said they are actively working on getting JMAP support enabled, and in the meantime the next best thing is the Proxy. I don't think it's a case of 'making an exception' but that they are still trying to get JMAP fully into production - if they did, it would be in their best interest to enable access for all, of course (to enable client-side testing etc). Your best bet is to reach out to Bron Gondwana at Fastmail (email@example.com) and I'm sure he will be able to update you with more details. Perhaps you could even ask them if they would consider part/fully funding the work of a developer to enable JMAP, they very may well say yes and if you don't ask, you don't get. It is their interest for JMAP to take off, and they are doing a great job into getting into the main servers, but the client-side implementations are a bit behind, with the guys at Kolab taking their sweet time with Roundcube Next. Atmail however are working on a mobile app with JMAP support, and Kolab/KDE have said they will put JMAP into Kube after they have finished with IMAP/CardDAV/CalDAV support, but that is of course a while away.
In https://dovecot.org/list/dovecot/2016-December/106553.html Brong writes "We are actually pretty close to a complete implementation in Cyrus now, and there's the proxy of course. We'll be doing a release candidate of Cyrus 3.0 with JMAP support on January 13th." Note, k9mail has listed jmap as a GSOC2017 idea https://github.com/k9mail/k-9/wiki/Google-Summer-of-Code-2017
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to Wayne Mery (:wsmwk) from comment #8) > In https://dovecot.org/list/dovecot/2016-December/106553.html Brong writes > "We are actually pretty close to a complete implementation in Cyrus now, and > there's the proxy of course. We'll be doing a release candidate of Cyrus > 3.0 with JMAP support on January 13th." doesn't appear to have happened, unless I missed something > Note, k9mail has listed jmap as a GSOC2017 idea > https://github.com/k9mail/k-9/wiki/Google-Summer-of-Code-2017 looks like nothing came of that. A tb-planning thread from 2015 https://groups.google.com/d/msg/tb-planning/qHxi9KqIoU8/N5sNHnylDAAJ Other latest info - https://datatracker.ietf.org/doc/draft-ietf-jmap-mail/ - https://github.com/linagora/jmap-client (code) - https://blog.fastmail.com/2017/12/08/fastmail-at-ietf/
See Also: → bug 288514
https://medium.com/linagora-engineering/why-jmap-is-the-future-of-emails-c63cd9106499 https://www.atmail.com/blog/how-does-jmap-make-email-better/ https://cyrusimap.org/imap/developer/jmap.html (Cyrus versions 3.0 to 3.0.5 included experimental JMAP support) https://github.com/RainLoop/rainloop-webmail/issues/1378
Cyrus 3.0 had limited JMAP support (old drafts) - cyrus master has the most current draft on it, and I expect we'll cut a 3.1.x pre-release version with that pretty soon. The JMAP proxy (https://github.com/jmapio/jmap-perl) is also close to current draft. There are a couple of small holes, but it's been ported to the new style objects and we're preparing it for testing at the Hackathon in London. https://trac.ietf.org/trac/ietf/meeting/wiki/101hackathon Obviously if there's anything from Thunderbird, or anybody from Thunderbird will be around and can join us in London, we'd love to see you!
Cyrus 3.1.4 just go released with up-to-date (for now!) JMAP support :) We're starting to deploy testing infrastructure on top of that at FastMail too.
There is a lot of activity around JMAP. What would be the current status or future plans for this support in Thunderbird?
How would a JMAP-compliant release of Thunderbird choose a protocol to communicate as client with a server offering a full choice of JMAP, IMAP, and SMTP? IMAP with IDLE results in mostly simultaneous updates to various connected devices as the ones showed in the movie at https://jmap.io/. Speed obviously depends on implementations. The "Reinventing IMAP" article, https://lwn.net/Articles/680057/, mentions contacts database and calendaring as the relevant advantages of JMAP over IMAP4. So bug #86405 and bugs about Lightning calendar synchronization would be involved too. Just mumbling...
I'd very much like to see this. https://fastmail.blog/2018/12/27/jmap-is-on-the-home-straight/
Thanks Tylera, Definitely a good time to be looking at adding JMAP support again, given that the protocol is now unlikely to have more changes. Regards, Bron.
You need to log in before you can comment on or make changes to this bug.