You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "René Cordier (Jira)" <se...@james.apache.org> on 2020/12/17 07:43:00 UTC

[jira] [Commented] (JAMES-1644) Support Jmap specification

    [ https://issues.apache.org/jira/browse/JAMES-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250866#comment-17250866 ] 

René Cordier commented on JAMES-1644:
-------------------------------------

https://github.com/linagora/james-project/pull/4140 adds a better optimized handling on AccessTokenAuthenticationStrategy data read

> Support Jmap specification
> --------------------------
>
>                 Key: JAMES-1644
>                 URL: https://issues.apache.org/jira/browse/JAMES-1644
>             Project: James Server
>          Issue Type: New Feature
>            Reporter: Matthieu Baechler
>            Priority: Major
>
> As stated by jmap.io website :
> {quote}
> JMAP is a transport-agnostic, stateless JSON-based API for synchronising a mail client with a mail server. It is intended as a replacement for IMAP. [...] It aims to be compatible with the IMAP data model, so that it can be easily implemented on a server that currently supports IMAP, but also allows for reduced data usage and more efficient synchronisation, bundling of requests for latency mitigation and is generally much easier to work with than IMAP.
> {quote}
> We think that is a decent protocol to use for a webmail implementation and we would like to add it to James as James goal is to serve emails with various protocols.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org