Skip to content

Support JMAP using JSON APIs over HTTP #7314

Description

@eakteam

Summary

Unlike older protocols that require complicated parsing or persistent TCP connections, JMAP modernizes email handling with several key advantages:

Efficient Synchronization: Instead of downloading entire mailboxes, JMAP allows clients to sync only the changes that have occurred since their last connection.

Web-Friendly API: It operates over standard HTTP POST requests, making it incredibly easy for third-party developers to build and integrate email apps using languages that support REST APIs.

Batched Operations: Clients can combine multiple requests (like searching, fetching, and flagging messages) into a single call, reducing loading times and mobile data usage.

Real-Time Push Notifications: JMAP uses built-in event streaming (via EventSource) to instantly notify all your devices the moment a new message arrives.

Consolidated Standard: Beyond email, the protocol extends to contacts and calendars, acting as a single, unified replacement for older standards like CardDAV and CalDAV.

Motivation

Since MailCow is the leader of Email Servers is should be the best to support JMAP, since it is the open protocol that replaces IMAP (and CardDAV and CalDAV). It's faster, simpler, more powerful, and built for how email works today.

Additional context

It is a modern, open standard created by the IETF (RFC 8620) to replace legacy email protocols like IMAP and SMTP. It allows clients to sync email, calendars, and contacts over HTTPS using lightweight JSON payloads.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions