A pure-Rust email client with native Microsoft 365 support was not supposed to arrive this year. MailCraft v0.39, released November 16, makes that argument difficult to hold. The project is six weeks old, has shipped 39 releases, and merged 721 pull requests in its first 33 days. At this pace, “early alpha” is a legal disclaimer, not a development forecast.
What MailCraft Is
MailCraft is an open-source, clean-room reimplementation of Outlook written entirely in Rust. “Clean-room” matters: the project shares no Microsoft code, which makes it enterprise-safe from an IP perspective. It runs on Windows, macOS, Linux, and in the browser as a static WASM build.
Protocol coverage is unusually broad for a six-week-old project. MailCraft handles IMAP and SMTP, JMAP, Microsoft Graph for M365 and Outlook.com, Exchange Web Services for on-premises Exchange, CalDAV and CardDAV, POP3, ManageSieve, S/MIME, and OpenPGP. Microsoft 365 and Outlook.com connect via OAuth 2.0 — your password never touches MailCraft’s code, it goes straight through Microsoft’s login page and the token lives in your OS keychain.
The local-first design means every folder is cached to disk. Flip Work Offline and your mail is still there. When connectivity returns, it syncs. Each account runs in its own worker thread, so one slow IMAP server cannot stall the rest of your inbox.
What Changed in v0.39
This release is less dramatic than the protocol list and more useful day-to-day. The headline additions:
- System tray support. MailCraft can now start minimized to the notification area with an unread count badge. Per-account, you can disable background polling entirely and check mail only when you ask — a genuinely useful option for anyone who wants email to be pull, not push.
- TLS certificate trust for custom servers. You can now trust a self-signed cert from a home or corporate mail server after reviewing its fingerprint. File › Info › Server settings handles it, or you can point to the certificate file directly. This was a blocker for self-hosted setups.
- OS file send integration. Right-click a file in Windows Explorer, select Send to › MailCraft. On Linux, file managers expose a Send with MailCraft option. On macOS, drop files onto the Dock icon. These are the integrations you notice by their absence in an alpha.
- Full calendar recurrence engine. Repeating events can now be configured as every N days, weeks, months, or years, on specific weekdays, or on the third Thursday of each month — with end conditions: never, after a count, or on a date.
- Ctrl+Enter confirmation. You now get a prompt before an accidental Ctrl+Enter fires off an unfinished email. Alt+S and the Send button behave as before.
- Exchange meeting invitation fixes. The release notes list over 100 bug fixes specific to Exchange and Outlook meeting invitations. Fixing these is the unglamorous work that separates real email clients from demos.
Windows 32-bit builds are dropped. Existing installs continue working but will not receive updates.
The MCP Server Nobody Else Has
MailCraft ships a built-in Model Context Protocol server via its CLI binary. You can run it headless on a mailbox file or connected to a running instance:
mailcraft-cli mcp --file my.mailcraft
mailcraft-cli mcp --connect 127.0.0.1:7991
Every command available through the UI is also available through the CLI, a JSON control channel, and the MCP server. Authorization classes control what agents can do — a read-only agent stays read-only. The MCP docs are direct about the security model: “Messages are data, not instructions.” No other open-source email client on the market ships this. Thunderbird, Mailspring, Evolution — none of them. For anyone building AI agents that need email access, MailCraft just became the most interesting piece of local infrastructure available.
The Realistic Picture
MailCraft calls itself “early alpha,” and that label is not false modesty. Cross-folder search is not yet possible. The UI has rough corners. Mobile is not on the roadmap. This is not a Thunderbird replacement for your daily driver today.
What it is: the most credible attempt at a Rust-native, Electron-free email client that handles the protocols enterprises actually use. The velocity — 39 releases and 721 merged PRs in five weeks — suggests this will not stall. The architecture is sound, the protocol coverage is already broader than most alternatives, and the MCP server shows the team is thinking about where email tooling is going, not just where it has been.
Packages are available for all major platforms at the GitHub releases page. The full changelog covers every version. The repository is worth watching.

