Tags give the ability to mark specific points in history as being important
-
-
-
-
-
-
-
-
-
-
-
-
-
v0.3.0
3058813f · ·docker-mailbox v0.3.0 — reader mode `?reader=true` on message fetch (HTTP + MCP) adds a `body_reader` field — the HTML body flattened to clean markdown via html2text. Drops styles, scripts, tracking pixels, and table chrome; keeps headings, inline links, bold/italic. Built for LLMs that don't want to parse raw HTML. Original body_text/body_html still returned; reader is additive. Off by default to keep payload size sane on bulk reads.
-
v0.2.0
f5e19b7d · ·docker-mailbox v0.2.0 — flat MCP tool set MCP now exposes one flat tool catalog. Per-mailbox tools take `mailbox` as a parameter (name or address) instead of being namespaced. Tool count is now O(1) instead of O(N) in mailbox count — agents can scale to 100+ inboxes without drowning in tool definitions. BREAKING for MCP clients: `<name>__list_messages` → `list_messages(mailbox=...)`.
-
v0.1.0
123e107c · ·docker-mailbox v0.1.0 — first release REST + MCP control plane over IMAP/SMTP. One process, one port, one bearer-auth gate. Configure mailboxes in config.yaml, mount read-only, ship. Highlights: - /mailboxes, /inbox, per-mailbox IMAP + SMTP endpoints - /mcp streamable-HTTP transport for agent integration - Multi-token bearer auth with constant-time comparison - Thunderbird MUA masquerade for self-send deliverability