mail
mail copied to clipboard
nextcloud
JMAP support
https://jmap.io/ https://tools.ietf.org/html/rfc8620 https://tools.ietf.org/html/rfc8621
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
![no-response[bot] avatar](https://avatars.githubusercontent.com/u/26350515?v=4 "Published by a pub.dev verified publisher"){kind=small}
Came here from a search, going to comment here so there isn't a duplicate opened. I believe what OP was suggesting, and what I would like to see too, is to Nextcloud Mail support JMAP protocol communication for external mail accounts (esp. Fastmail accounts), as overall it is a much nicer and cleaner protocol.
There is also the possibility they wished to see mail-in-a-box support JMAP protocol for self-hosted email servers, but as this is not a Nextcloud tool, ~~I think this would go to their issue tracker instead.~~
EDIT: Correction - it appear hosting support for JMAP would go towards Dovecot. I mmay open it myself, but I would suggest OP open a ticket over at @dovecot. Maybe core repo?
EDIT2: Dovecot has no issue tracker. Unfortunately this means it would not be possible to request hostable JMAP be implemented anywhere in the Nextcloud tooling chain.
Well and even then it's just two provider that support this, right?
We'll limit ourselves to IMAP for now. If we reach the state where we have other useful things done that 90% of our users will actually use, we can reconsider JMAP support.
Of note, a Thunderbird ticket for JMAP support exists, with 25 upvotes (an unusually significant amount) at bugzilla.mozilla.org/show_bug.cgi?id=1322991, ^1 so ecosystem interest exists.
In this blogpost https://nextcloud.com/blog/press_releases/nextcloud-stalwart-partnership/ you announced a partnership with Stalwart, which is supporting JMAP. Are there plans to support the protocol now? It would be nice to have SSO and JAMP support when using Stalwart as an IdP (OAuth) for Nextcloud.
Well and even then it's just two provider that support this, right?
This is the story of the egg and the chick: servers don't wanna work on it because there's too few clients supporting it. clients don't wanna work on it because there's too few servers supporting it.
IMAP is getting old and doesn't work well with mobility (along with new usages like tags, contacts, calendars and tasks sync, etc.). From the look of it, there's will from end-user to use it, even with not so much publicity, so i believe there's worth working on it.
In this blogpost https://nextcloud.com/blog/press_releases/nextcloud-stalwart-partnership/ you announced a partnership with Stalwart, which is supporting JMAP. Are there plans to support the protocol now? It would be nice to have SSO and JAMP support when using Stalwart as an IdP (OAuth) for Nextcloud.
Maybe an additional hint: https://stalw.art/blog/jmap-collaboration/
After four years of development, we’re thrilled to announce a major milestone in the evolution of Stalwart — the full implementation of JMAP for Calendars, Contacts, Address Books, File Storage, and Sharing. With this release, Stalwart becomes the first JMAP server to fully support the entire family of JMAP collaboration protocols, marking a new era for open, efficient, and elegant groupware.
Looking into plans for JMAP-support in other projects I think it might make sense to think about JMAP-support in two directions. One is Nextcloud connecting to a JMAP-server and the other might be exposing services over JMAP again. For Roundcube there is work-in-progress to expose an API for calendars and contacts. And with JMAP in both directions I think Nextcloud could also work as a hub, where for example some calendars are hosted locally, others synced from somewhere and all are (besides existing protocols) exposed via JMAP. Maybe exposing email over JMAP to clients would be one of the bigger steps. But exposing the other protocols/use-cases over JMAP as a first step?
