Skip to content
nofeb

What is JMAP?

Also called JSON Meta Application Protocol

JMAP (JSON Meta Application Protocol) is an IETF standard for reading and writing email, and now calendars, over HTTPS with JSON. A client fetches a session document, sends batches of method calls such as Email/query and Email/get in one request, and asks only for what changed since a state string it already holds.

Checked against the engine on .

Shipped nofeb's support for JMAP

How does JMAP work?

JMAP replaces the long-lived connection and line protocol of IMAP with stateless HTTP requests. One request can chain calls with back-references (query for the newest ten emails, then fetch exactly those) so a client needs one round trip where IMAP needs several. Every object type has a /changes method, so sync is a question of what changed since state X, and push arrives over EventSource or a WebSocket.

The core is RFC 8620. Mail, submission and vacation responses are RFC 8621, and the WebSocket transport is RFC 8887. Sending is an EmailSubmission that refers to a stored email rather than a raw stream of bytes, which lets a server check a send against policy before anything leaves and report the outcome as an object the client can watch.

Unlike a vendor's REST API, JMAP is a protocol: a JMAP client works against any JMAP server, and extensions are announced as capability URNs in the session, so a client knows exactly which features a server offers before it uses them.

Newest ten emails in one request
POST /jmap/api
{ "using": ["urn:ietf:params:jmap:core", "urn:ietf:params:jmap:mail"],
  "methodCalls": [
    ["Email/query", { "accountId": "inb_…", "sort": [{ "property": "receivedAt", "isAscending": false }], "limit": 10 }, "q"],
    ["Email/get", { "accountId": "inb_…", "#ids": { "resultOf": "q", "name": "Email/query", "path": "/ids" },
                    "properties": ["subject", "from", "preview"] }, "g"]
  ] }

How does nofeb use JMAP?

  • Every inbox a credential can see is a JMAP account whose id is the inbox id. The session is at /.well-known/jmap and the API at /jmap/api, with an API key or an OAuth access token as the bearer. Mailbox, Thread, Email, SearchSnippet, Identity, EmailSubmission, VacationResponse and blob upload and download are supported, with push over EventSource and WebSocket.
  • JMAP shares one change history with the REST API, IMAP and the webmail, so a client syncing with /changes sees an agent's work and a person's work in one order. States older than the retained history (90 days) get cannotCalculateChanges, and the client resyncs.
  • Two extensions carry the agent features: urn:nofeb:jmap:metadata exposes typed metadata on Email and Thread, validated against your schema, and urn:nofeb:jmap:approval shows whether a submission is waiting for a person and lets someone holding send:approve decide it.
  • An EmailSubmission meets the same autonomy tiers, approvals, lists, caps and hooks as an API send; a held send appears with undoStatus: pending, and setting it to canceled withdraws it. Vacation responses answer each sender at most once a week and never answer automated mail.
  • JMAP Calendars (urn:ietf:params:jmap:calendars) serves the same calendars as CalDAV and the API, with push for calendar changes.

Frequently asked questions

Is JMAP a replacement for IMAP?

It is designed for the same job, over HTTPS and JSON, with cheaper sync and built-in push. Many desktop clients still speak only IMAP, so nofeb serves both on the same mailboxes.

Can I use JMAP as an email API for an agent?

Yes. A JMAP client library works against nofeb unchanged. The REST API and MCP add calls JMAP does not have, such as wait_for_email, thread context ready for a model and the approval queue.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
JMAP JMAP Mail, submission, vacation responses and push, one account per inbox a key can see, sharing one change history with the API and IMAP, with extensions for typed metadata and approvals. A send over JMAP meets the same autonomy tiers as any other. Shipped
IMAP and POP3 IMAP4rev2 (with IMAP4rev1 compatibility, IDLE, CONDSTORE and QRESYNC) and POP3 on every inbox, over TLS only, signed in with the inbox address and an API key or a revocable per-inbox app password. Shipped
Typed metadata on messages, threads and inboxes Merge-patch keys onto a message, a thread or an inbox, and declare a key's type so every write to it is validated. Shipped
Human approval of held sends A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. Shipped
Calendar per inbox A calendar on every inbox: events with recurrence and time zones, invitations, updates, cancellations and replies by email, auto-accept rules, free/busy, availability and booking that sends the invitations, MCP tools for scheduling, and CalDAV and JMAP Calendars for standard clients. Invitations an agent sends follow its inbox's autonomy tier. Shipped
MCP sign-in with OAuth MCP clients connect by signing in instead of pasting a key: OAuth 2.1 with discovery, dynamic client registration, client ID metadata documents, PKCE, tokens bound to the MCP server, refresh-token rotation and immediate revocation. A person approves the scopes, and optionally one inbox, in the console, and can disconnect the app at any time. API keys keep working beside it. Shipped