james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Baechler (JIRA)" <server-...@james.apache.org>
Subject [jira] [Closed] (JAMES-1644) Support Jmap specification
Date Fri, 11 Dec 2015 10:11:11 GMT

     [ https://issues.apache.org/jira/browse/JAMES-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Matthieu Baechler closed JAMES-1644.
    Resolution: Fixed

merged on trunk.

> 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
> 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
> {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

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

View raw message