jmap

jmap
Name	jmap
Developer	Apache Software Foundation, FastMail, Cyrus IMAP contributors
Initial release	2014
Latest release	ongoing
Written in	JavaScript, C, Rust, OCaml, Python
Operating system	Cross-platform
Genre	Application layer protocol
License	MIT, Apache License 2.0

jmap

jmap is an application-layer protocol designed to synchronize email, calendars, contacts, and related data between servers and clients. It was developed to replace older protocols by providing a JSON-based, HTTP-friendly API with support for push notifications, batch operations, and granular state management. The design emphasizes interoperability with existing standards and systems used by providers such as FastMail, Apple Inc., Mozilla Foundation, University of Cambridge and Cyrus IMAP Project contributors.

Overview

jmap emerged from efforts to modernize interactions formerly handled by Internet Message Access Protocol and Post Office Protocol 3 style systems. Its specification defines a coherent set of methods for mailbox, message, contact, and calendar management and integrates with push infrastructures like WebSocket and HTTP/2 pathways. Major stakeholders included implementers from FastMail, maintainers connected to the IETF community, and developers familiar with server projects such as Dovecot and Cyrus IMAP. Use cases span consumer mail services run by companies like Yahoo! and Microsoft Corporation to institutional deployments at universities and enterprises using OpenStack and other cloud stacks.

Protocol and Architecture

At the core, the protocol specifies JSON-encoded requests and responses transmitted over HTTP(S) endpoints, aligning with web platforms created by organizations such as Google LLC and Cloudflare. Architectural elements borrow concepts from RESTful APIs used by Facebook and Twitter (X) but introduce batch semantics and state tokens similar to synchronization techniques used in CalDAV and CardDAV. jmap accommodates push via technologies standardized or promoted by bodies like the IETF HTTP Working Group and leverages HTTP authentication and session management methods compatible with OAuth 2.0 and TLS deployments endorsed by Let's Encrypt and Internet Engineering Task Force participants. The protocol also defines extensions for attachments, filtering, and server-side search influenced by indexing systems from Elasticsearch and Apache Lucene.

Implementations and Servers

Several server-side implementations exist, including projects maintained by organizations such as FastMail, the Cyrus IMAP Project, and experimental work in repositories associated with Apache Software Foundation projects. Open-source servers integrate jmap support into established mailstores like Dovecot and backend platforms used by Zimbra and Kolab Project ecosystems. Commercial providers including FastMail and certain hosted offerings from Rackspace and cloud vendors have deployed jmap-compatible endpoints for production use. Community implementations in languages and runtimes include efforts in Rust, Go (programming language), Python (programming language), and OCaml often hosted on platforms like GitHub.

Client Support and Integrations

Client-side libraries and mail clients have incorporated jmap support to various degrees. Client projects undertaken by organizations such as Mozilla Foundation (through Thunderbird experimental work) and application developers at Apple Inc. for macOS and iOS clients demonstrate interest in native integration. Webmail front-ends and Progressive Web Apps built by teams influenced by Google and Microsoft Corporation engineers exploit jmap’s HTTP-friendly model to integrate with single-page app architectures common in React (JavaScript library), AngularJS, and Vue.js ecosystems. Synchronization libraries and SDKs provided by community contributors enable integration with CRM systems like Salesforce and groupware suites such as SOGo and Zimbra.

Security and Authentication

jmap deployments rely on transport-layer security provided by Transport Layer Security implementations and certificate authorities including Let’s Encrypt and long-established vendors. For authentication, jmap interoperates with standards such as OAuth 2.0 and can use mechanisms compatible with SASL frameworks found in Dovecot and Cyrus IMAP Project ecosystems. Authorization and scope management practices reflect patterns used by GitHub and Google APIs to permit fine-grained access to mailboxes, calendars, and contacts. Server operators often integrate with identity providers like Okta, Microsoft Azure Active Directory, or Google Identity Platform to centralize credentials and apply enterprise policy. Security considerations also cover rate-limiting, anti-spam frameworks pioneered by organizations like SpamAssassin and abuse detection techniques employed by large providers such as Yahoo!.

Performance and Scalability

jmap’s batch-oriented design reduces round trips compared with legacy protocols, enabling high-throughput synchronization strategies similar to those used by large-scale services at Google and Facebook. Implementations can cache state tokens and leverage search backends like Apache Lucene or Elasticsearch to serve queries efficiently. Scalability patterns draw on load-balancing and microservice topologies popularized by Netflix and Amazon Web Services, with deployments often using reverse proxies and edge delivery from Cloudflare or Akamai Technologies. Real-world deployments report improvements in sync latency and resource utilization when compared to IMAP in mobile and web scenarios, particularly when combined with HTTP/2 or QUIC transports.

Category:Internet protocols