Skip to content

3.1.0 — Zimbra and mail reliability

Choose a tag to compare

@1amSheldon 1amSheldon released this 14 Oct 18:05
48f1e8b

Zimbra and mail reliability

Mail MCP 3.1.0 adds Zimbra as an optional provider alongside IMAP/SMTP, Apple Mail, Microsoft and Mailtrap. Existing accounts do not need a Zimbra server.

  • Native Zimbra SOAP/REST supports mail search and reads, MIME attachments, draft creation/editing/sending, folders, flags, tags, contacts, groups and directory lookup.
  • Zimbra also supports identities, signatures, preferences, incoming/outgoing rules, sharing, Briefcase files and revisions, calendars, tasks, recurring events, invitations, iCalendar and native scheduled delivery.
  • Authenticate locally with a password and required second factor. Trusted-device login and password storage are optional and disabled by default. Credentials are not MCP arguments.
  • Persist Zimbra send attempts and report uncertain outcomes without automatically resending. Guard edits against reviewed revisions and check configured recipient and attachment policies.
  • Integrate bounded IMAP paging, mailbox-generation checks, message previews, MIME reads and caches; improve threaded reply drafts and attachment-aware replies/forwards.
  • Improve SMTP/OAuth lifecycle, TLS verification, provider pagination, EWS attachment sends and uncertain save/send results.
  • Keep three MCP tools. Load the core workflow and only the required provider/topic instructions, through resources or prompts, instead of loading the entire documentation set.
  • Preserve the public npm update channel and windowless shared Windows service. Codex and Claude receive the same packaged instruction references.

Upgrade notes

Accounts and credentials remain outside the package. Keep persistent draft/send records when moving an installation; an unknown delivery outcome is not permission to resend. Zimbra capabilities depend on the server version, edition, authentication extensions and account permissions. Native scheduling can use later webmail edits, and clearing its metadata cannot recall an already-started send.

Older nonempty IMAP draft journals lack a mailbox-identity binding. The local migration command uses a retained pre-upgrade accounts snapshot, preserves all records and attempts, and writes a backup. Do not delete journals or bind them to an unverified replacement mailbox. See the README for the command and upgrade procedure.

Verification

Release checks cover TypeScript/build, generated documentation, English-only text, unit and loopback integration tests, stdio/HTTP/import/installed-package smoke checks and dependency audit. Dedicated regressions cover cancellation during credential lookup, shutdown during provider creation, persistent draft migration and on-demand documentation. Credential-gated external IMAP integration cases remain skipped without test credentials. Real Zimbra login, delivery and server compatibility are not established by the fixture suite; use a dedicated test account to qualify the target server.

Thanks to starychenko for the Zimbra implementation and mail hardening work. This release integrates the final source across its branches, retains contributor attribution, and adds lifecycle, documentation and public-distribution fixes after review.