Skip to content
nofeb

Product / Protocols

Standard protocols and a way out

A mailbox your agents depend on should not be one you can only reach through one vendor's API. Every nofeb inbox is reachable over the standard mail protocols, every message can be taken out exactly as it came in, and every route in or out meets the same policy.

Every surface, one mailbox

  • REST, described by a published OpenAPI document that a parity test keeps identical to the served routes, and MCP over streamable HTTP, generated from the same operation table.
  • JMAP Mail, submission and vacation responses, with push over EventSource and WebSocket. Each inbox a key can see is a JMAP account, with extensions for typed metadata on emails and threads and for approving held sends.
  • IMAP4rev2, compatible with IMAP4rev1 clients, with IDLE, CONDSTORE and QRESYNC, SPECIAL-USE folders and MOVE; and POP3 over the inbox. Changes made over IMAP reach JMAP clients, the webmail and the API at once.
  • SMTP submission on ports 587 (STARTTLS required before sign-in) and 465 (TLS), for software that can only send mail one way.
  • CalDAV and JMAP Calendars for every inbox's calendar.
  • Standard inbound mail: point a domain's MX at nofeb and any mail server can deliver to your inboxes directly, with STARTTLS, or keep Cloudflare Email Routing, Postmark, Mailgun or SendGrid and pass mail on.
  • A change log per inbox, shared by the API, JMAP and IMAP: everything that changed since a state you hold, for sync without re-reading.

Signing in a mail client

The username is the inbox address. The password is an API key that covers the inbox, or an app password: a revocable credential for one inbox and one client, holding no more scopes than the person who created it, with its last use, protocol and client address recorded. Sign-in happens only over TLS, and repeated failures are throttled per client address across all three protocols. One call returns the hosts and ports to type in.

Settings for a mail client
POST /v1/inboxes/{inbox_id}/app-passwords
{ "name": "Thunderbird on laptop" }

GET /v1/inboxes/{inbox_id}/mail-client-settings
# IMAP 993 (TLS) or 143 (STARTTLS), POP3 995 or 110,
# SMTP submission 465 (TLS) or 587 (STARTTLS)

One policy, every protocol

Protocols are surfaces on the same engine, not separate systems. A message submitted over SMTP or JMAP goes through the same check as an API send: autonomy tier, approvals, sponsor gating, suppression, allowlists and blocklists, caps and outbound hooks. The sender must be an inbox the credential covers. A message held for approval is accepted and reported as held, with its send id, and its outcome follows on the usual events. A credential that can approve sends still cannot approve its own submission.

Appending a message to Sent over IMAP never sends it, and appending to Drafts files a draft, the same draft the API and the webmail see.

A way out

Export a whole inbox, one folder, one thread or the results of a search, as mbox or as a zip of EML files. Each message comes with a JSON record of its folders, keywords, labels, metadata and decisions, and threads with theirs. Exports are built in the background, in self-contained parts, announced by export.completed, and downloaded through signed links.

Any single message can also be downloaded byte-exact, and raw MIME can be pushed into an inbox for imports and migrations.

Export an inbox
POST /v1/exports
{ "format": "mbox", "inbox_id": "inb_..." }

GET /v1/exports/{export_id}

How long mail is kept

Retention policies delete messages older than a number of days, or move them to Trash or Archive, per organization, pod, inbox or folder, sparing flagged mail unless you say otherwise. A dry run shows what a saved or proposed policy would touch. A legal hold blocks every deletion in its scope, including retention, inbox expiry, inbox deletion and deletes from mail clients, until it is lifted. Each run emits retention.applied with its counts.

Keep a year, hold one inbox
POST /v1/retention-policies
{ "action": "delete", "after_days": 365 }

POST /v1/retention-policies
{ "action": "hold", "inbox_id": "inb_...", "label": "Matter 2026-114" }

Status of everything on this page

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

CapabilityWhat it doesStatus
OpenAPI document A published OpenAPI document kept identical to the served routes by a parity test. Shipped
MCP server A remote MCP server over streamable HTTP whose tools are generated from the same operation table as the REST API and dispatched through the same router, so a tool cannot behave differently from its endpoint. Shipped
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
SMTP submission Authenticated SMTP submission on ports 587 and 465 for tools that only speak SMTP. Every submitted message meets the same autonomy tiers, approvals, lists, caps and hooks as an API send, and a held message is accepted and reported as held. 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
Inbound mail server that checks mail at the door nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. Shipped
Inbound from the provider you already use Receive through Cloudflare Email Routing with an Email Worker on your own zone, a Postmark inbound stream, a Mailgun route, SendGrid Inbound Parse, or any service that can POST a raw message. Each path is authenticated by your organization's inbound token, which you can rotate at any time, and delivers only to your own inboxes and verified domains. Shipped
Byte-exact raw messages Download any stored message exactly as it was received. Shipped
Raw message push Push raw MIME into any of your inboxes for imports and generic inbound webhooks. Shipped
Change log per inbox Every change to an inbox since a state you already hold, for sync without re-reading. Shipped
Full export A whole inbox, a folder, a thread or a search as mbox or a zip of EML files, with every message's folders, keywords, metadata and decisions as JSON, built in the background and downloaded through signed links. Shipped
Retention policies and legal holds Delete messages older than a number of days, or move them to Trash or Archive, per organization, pod, inbox or folder, keeping flagged mail by default, with a dry run that shows what a policy would do. A legal hold blocks every deletion in its scope, including expiry and inbox deletion. Shipped