EXTENSIONS

Cloudflare email infrastructure models

listmonk (v6.2.0) REST API behavior — a typed swamp primitive for driving a

Non-destructive administration of a Stalwart mail server (0.16 and v1) over its JMAP-over-HTTP management API, authenticated with a scoped admin API key. Reads domains, accounts, aliases, groups, DMARC/TLS reports, the outbound queue and server health. Creates or updates accounts and aliases, groups, mailing lists and roles (idempotent); changes server settings; installs and reloads certificates; reloads config; and deactivates or reactivates domains and accounts. No hard deletes: the reversible set-state methods are the only way to disable anything. Secrets (account passwords, certificate keys) are sent once and never read back.

Yandex Mail over IMAP (read, search, organise) and SMTP (send). Yandex has

Cloudflare Email Routing — rules, addresses, catch-all, DNS setup

Provider-agnostic ManageSieve (RFC 5804) client built directly on Deno's native TCP/TLS primitives -- no third-party ManageSieve library exists on npm with any real maintenance signal, so the small line protocol (STARTTLS, SASL PLAIN, and the literal/quoted string framing for LISTSCRIPTS/GETSCRIPT/PUTSCRIPT/SETACTIVE/DELETESCRIPT/CHECKSCRIPT) is implemented in-repo behind a single injectable transport seam. Read-only methods: listScripts, getScript, getActive, checkScript (CHECKSCRIPT without installing). Gated write methods: putScript, setActive, deleteScript -- dryRun defaults true, every write validates via CHECKSCRIPT first (putScript) or a live LISTSCRIPTS snapshot (setActive/deleteScript), and deleteScript refuses to remove the currently-active script. Script names/text are always sent as RFC 5804 non-synchronizing literals ({n+}), which are purely length-prefixed, so no caller-supplied content can ever be interpreted as a protocol boundary.

Provider-agnostic IMAP inspection + gated-write model built on imapflow. Phase 1 (read-only): listFolders enumerates the folder tree with per-folder message counts and sizes; sync snapshots message envelopes plus a fixed header set (From, To, Cc, Subject, Date, Message-ID, In-Reply-To, References, List-ID, List-Unsubscribe, List-Post, Reply-To, Auto-Submitted, Precedence) with flags and size into versioned data -- HEADERS ONLY, never bodies. fetchMessage (read-only, EXAMINE) is the one method that pulls FULL bodies, for ONE folder per call (an IMAP UID is unique only within one folder+UIDVALIDITY): it uses a pre-fetch size gate (one {uid,size} fetch to partition the UID set against MAX_BODY_BYTES, then one source fetch for the under-cap UIDs only, never a per-UID loop), decodes with postal-mime, and writes one messageBody record per UID (text/html, attachment metadata only, extracted http/https links, an error field). An over-cap body is deliberately NOT pulled (truncated=true, sourceBytes=server size, null bodies) so oversized sources are never buffered; a no-server-size body over the cap is byte-truncated; each decode is isolated so one malformed message cannot abort the batch; a null-UID or absent UID is skipped. html is stored UNSANITIZED. messageBody records have a FINITE (30d) lifetime. It performs ZERO mutation and is structurally read-only like sync (EXAMINE; no peek knob). Mailboxes are opened read-only (EXAMINE) for these methods. Phase 3 (gated write): addKeywords/removeKeywords/move fan out one STORE/MOVE command over a UID set, dryRun-gated, uidValidity-guarded, verified by a post-mutation re-FETCH. applyTagPlan (Reconcile-B) reads the latest tagPlan record from a @shrug/mail-ontology instance and applies it over the same safety core, fanned out by (folder,keyword) and (folder,destination) group. createFolder (imap-create-folder) ensures a LIST of mailbox paths exist in one call (imapflow mailboxCreate), idempotent on ALREADYEXISTS, verified by a post-creation re-LIST; it is mailbox-level and needs no UID/uidValidity machinery. The mailbox credential is resolved from a swamp vault via CEL; it is never inlined.

Migadu mailbox-admin REST API (v1) client for swamp. The third mail primitive

Manage a Scaleway Transactional Email (TEM) sending domain — sync state, create, and delete domains, discover domains, and list sent emails in a region, via the TEM API with X-Auth-Token auth.

Fastmail email-organization pipeline over JMAP — scan every sender (flagging bulk/newsletter mail via RFC 2369/8058 List-* headers), generate ready-to-paste Sieve scripts that sort senders into nested folders, and plan/apply message moves — with audit, rule-coverage, apply-plan, and inbox-analysis reports.

Read-only Mailgun models — GET requests only, no write capability

Mailgun email delivery models

Comprehensive Resend integration: emails, domains, API keys, audiences, contacts, broadcasts. Markdown templates with themable cyberpunk shell.

Customer.io App API — snapshot segments and transactional messages, and run an idempotent per-brand readiness audit (segments + transactional messages) for a shared workspace.

JMAP model for email triage — search, refile, mark, frequency analysis, attachment download