Apple Mail is fine inside Apple. Epistles is for the rest.

Apple Mail is pre-installed, free, and good enough for a single iCloud mailbox on a Mac and an iPhone. If that’s the shape of your email life, close this page; we’re not going to talk you out of an app you already have. This page is for the readers whose inbox crossed Apple’s boundary years ago, a Gmail for the day job, a Microsoft 365 from the consulting client, an old Fastmail that has outlasted three jobs, a ProtonMail for the political work, a Linux desktop at home, an Android phone in the pocket, a Galaxy Watch on a wrist. Apple Mail can’t help with any of that. Epistles can, with iCloud included, on every device you use.

What Apple Mail does well

Apple Mail is integrated into the operating system in a way no third-party client can be. Spotlight indexes your mail without asking. The dock badge and menu bar count work without configuration. Handoff continues a draft from Mac to iPhone in mid-sentence. Hide My Email and iCloud+ aliases land in the right place because Apple wrote both ends of that pipe. The app is local-first: messages live on the device, search runs against the local store, attachments cache automatically. Quick Look, Markup, and Continuity Camera aren’t features bolted on; they’re the surfaces every Apple app gets, and the texture of reading mail on a Mac benefits from that. None of this is in dispute.

Where Apple Mail stops

The first wall is the platform. Apple Mail ships on macOS and iOS, and nowhere else. There is no Linux build, no Windows build, no Android build, no standalone web client; iCloud.com is a webmail surface for iCloud only, not a client you can point at Gmail or Microsoft. If your desktop runs Linux, your work laptop runs Windows, or your phone is Android, Apple Mail isn’t part of the conversation. The watch story rhymes: Apple Watch has a Mail app, but only Apple Watch does. A Galaxy Watch or a Pixel Watch sees nothing.

The second wall is the protocol. iCloud Mail is fine in Apple Mail because iCloud is Apple’s own provider. Add a Gmail and the experience quietly degrades: Gmail labels arrive flattened to IMAP folders, the categories Gmail sorts mail into on the web aren’t respected, server-side filters aren’t editable from the client, and the unified inbox is more a stack of mailboxes than a single timeline. Microsoft 365 mailboxes are IMAP-flat too, no native categories, no OWA push, none of what Outlook on the web treats as table stakes. ProtonMail doesn’t work at all without Proton Bridge running as a separate daemon. None of these are bugs in Apple Mail; they’re the cost of IMAP-as-the-lowest- common-denominator on every account that isn’t iCloud.

The third wall is the maintenance cadence. Apple Mail’s release schedule is the OS release schedule, which means a year or two between notable updates and long stretches where the team is clearly working on something else. There’s no roadmap you can read. Bugs filed against one macOS minor version sit until the next major. The app you can use today is the app you’ll be using next year.

What Epistles ships that Apple Mail does not

Six platforms, one codebase. macOS, Linux (signed APT, DNF, and Flatpak repos at repo.epistles.com), Windows (NSIS installers, x86_64 and aarch64), iOS, Android, and a web app at app.epistles.com. The protocol adapters, the local SQLite cache, and the Cloud Vault are one engine across every device.

Apple Watch and Wear OS, the same feature set on both. Archive, snooze, voice or template reply, the Reply & Done composite action, pin, forward, and agenda RSVP, on Apple Watch (every model running watchOS 10) and on Galaxy Watch and Pixel Watch (any Wear OS 3+ device). WidgetKit complications on the Apple side; Tile previews on Wear OS. The watch is companion-only, no credentials live on it. If your phone is on the table, your wrist can triage.

iCloud as a first-class provider. One wizard collects your Apple ID and an app-specific password and provisions Mail (over IMAP) plus Calendar and Contacts (over CalDAV and CardDAV) in one step. Apple has no public OAuth program for iCloud data; Sign in with Apple is identity-only and useless for reading mail. The app-specific-password path is the only one that works for a third-party client, and Epistles wires it through cleanly.

Native protocols on every other provider. Gmail through the Gmail API (labels are labels, not folders pretending to be labels), Microsoft 365 through OWA (the same private API the Outlook web client uses, with native push and real categories, not Graph), Fastmail through JMAP, ProtonMail through Proton’s API with OpenPGP decryption on device (no Bridge, no localhost daemon), and generic IMAP/SMTP as the fallback. Each adapter ships independently, so an iCloud-only mailbox never downloads Gmail code, and a Gmail-only mailbox never downloads Proton’s crypto.

Zero-knowledge Cloud Vault. Connected-account credentials, IMAP passwords (including iCloud’s app-specific password), OAuth refresh tokens, JMAP session blobs, are wrapped on the device with a key derived from your Epistles password and stored on our servers as opaque ciphertext we cannot decrypt. Sign in on a second Mac or a new phone, type the password once, and your iCloud, Gmail, Microsoft, and Fastmail accounts are there. Proton is carved out: its mailbox passphrase and OpenPGP material stay in the OS keychain only, by design.

Pricing that doesn’t creep. Free for three connected accounts. Pro is $35 a year for unlimited, with a 15-day trial that asks for no card up front. No per-seat tier, no enterprise edition, no analytics layer to feed.

Where Apple Mail wins

Apple Mail wins some things outright, and we’re going to be honest about them. Spotlight indexing that picks up your mail without a setting is a feature only the OS vendor can ship; we can’t match it, and we won’t pretend our local search is a substitute. Handoff between Mac and iPhone is the same story. Hide My Email and iCloud+ aliases land natively in Apple Mail because Apple wrote both ends of that pipe; in Epistles those aliases work as send-from identities you configure, but the system-wide “Hide My Email” affordance in Safari doesn’t flow through. If you live entirely in Apple, those are the things you give up.

Apple Mail also ships Send Later as a system-level feature, with no dependency on the device staying awake, because Apple owns the queue. Epistles ships Send Later too, but it’s client-driven by design, the device holding the unlocked vault schedules and sends, which means the machine you scheduled on has to be reachable when the time arrives. That’s the cost of the zero-knowledge model. If system-managed deferred send is a hard requirement, Apple Mail wins on that one axis.

The matrix, plainly

Platforms shipping today

Apple Mail: macOS, iOS. Epistles: macOS, Linux, Windows, iOS, Android, web.

Watch app

Apple Mail: Apple Watch only, via the system Mail app. Epistles: Apple Watch and Wear OS (Galaxy Watch, Pixel Watch, any Wear OS 3+ device), with the full triage feature set on both.

iCloud Mail

Both clients support iCloud Mail. Epistles uses the app-specific-password flow Apple offers third-party clients, since Apple has no public OAuth program for iCloud data.

iCloud Calendar and Contacts

Both clients support iCloud Calendar and Contacts. Epistles provisions CalDAV and CardDAV from the same wizard as Mail, in a single step.

Gmail

Apple Mail: IMAP-flat, labels collapse to folders, no Gmail categories. Epistles: native Gmail API, labels are labels, categories preserved.

Microsoft 365

Apple Mail: IMAP-flat, no native categories, no OWA push. Epistles: native OWA, native categories, OWA SignalR push.

Fastmail

Apple Mail: IMAP. Epistles: native JMAP, instant push, server-side identities.

ProtonMail

Apple Mail: requires Proton Bridge running as a separate daemon. Epistles: native, OpenPGP runs on device, no Bridge.

Generic IMAP / SMTP

Both clients support arbitrary IMAP and SMTP hosts.

Multi-account unified inbox

Apple Mail: a per-account list with a stacked “All Inboxes” view. Epistles: one client, one keyboard, one set of shortcuts across every account, with each thread chipped to the account it belongs to.

Local-first storage

Both store mail on the device, work offline, and rely on OS disk encryption (FileVault, Data Protection) at rest.

Snooze

Apple Mail: yes on iOS/iPadOS 16+ and macOS 13+, scoped to the system Remind Me feature. Epistles: yes on every platform, including the watch, with custom snooze targets and a server-side wake.

Send Later

Both support it. Apple Mail’s queue is system-managed; Epistles is client-driven (the device with the unlocked vault sends).

Read receipts and link tracking

Apple Mail: not supported. Epistles: opt-in, per-message, with the privacy carve-outs documented on the security page.

Open source

Neither. Apple Mail is closed-source bundled with the OS; Epistles is closed-source proprietary. If “read the code” is your trust model, Thunderbird is a good open-source client and we recommend it without irony.

Cross-device account sync

Apple Mail: per-device sign-in (iCloud Keychain helps within Apple). Epistles: a zero-knowledge Cloud Vault carries connected-account credentials between devices, encrypted under your Epistles password.

Pricing

Apple Mail: free, bundled with macOS and iOS. Epistles: free for 3 accounts; $35/yr Pro for unlimited; 15-day trial, no card.

Who should pick which

If your inbox is one iCloud address, your only computer is a Mac, your only phone is an iPhone, and your only watch is an Apple Watch, Apple Mail is a fine answer. The integration rewards a single-vendor life, and the price (free, bundled) is hard to beat. Use it.

If you carry more than one provider, an iCloud alongside a Gmail alongside a Microsoft 365, Apple Mail’s IMAP-flat treatment of everything that isn’t iCloud will keep nudging you back to the web. Epistles speaks each provider’s native protocol, and iCloud sits among them as a peer rather than the only first-class citizen.

If your devices cross Apple’s boundary at all, a Linux desktop, a Windows laptop at work, an Android phone in the household, a Galaxy or Pixel Watch on a wrist, the choice is forced. Apple Mail isn’t there. Epistles is, today, from the same codebase, with the same shortcuts and the same Cloud Vault carrying your connected accounts between devices.

If you do switch

Switching from Apple Mail is unusually painless because IMAP is the protocol underneath every account Apple Mail can reach. Your messages live on Apple’s servers (for iCloud) or your provider’s servers (for everything else), not in a local Apple Mail mailbox you’d have to migrate. Reconnect your iCloud account in Epistles with an app-specific password (one wizard, Mail plus Calendar plus Contacts), add the other providers, and the same mail you were just reading shows up. Read state syncs back through IMAP, so a message read in Epistles shows as read in Apple Mail if you keep both installed during the transition.

Common questions

Will Epistles work with my @icloud.com address?

Yes. Add an iCloud account in Epistles, sign in with your Apple ID, and paste an app-specific password generated at appleid.apple.com. The single wizard provisions IMAP for Mail and CalDAV/CardDAV for iCloud Calendar and Contacts at once. Apple does not publish a public OAuth program for iCloud data, so an app-specific password is the only path that actually works for a third-party client.

Why can’t I just sign in with Apple?

Sign in with Apple is identity-only. It can prove you own an Apple ID to a third-party site, but it does not grant access to your iCloud mailbox, calendar, or contacts. Apple has no public OAuth program that does. The app-specific-password flow is the only mechanism Apple offers third-party clients, and it is the same mechanism every desktop email client uses to read iCloud Mail.

Will my iCloud calendar and contacts work too?

Yes. The same app-specific password unlocks Mail (over IMAP), Calendar (over CalDAV), and Contacts (over CardDAV) in one wizard. Two providers are wired up under the hood from a single sign-in step, so you don’t have to repeat the credential entry for each surface.

Will I lose anything by switching from Apple Mail?

No mail. Your messages live on Apple’s servers, not in Apple Mail’s local store. Reconnecting your iCloud account in Epistles fetches the same mailboxes, threads, and flags. Read state syncs back through IMAP, so a message read in Epistles shows as read in Apple Mail if you keep both installed. What doesn’t carry over is the system-vendor polish, Spotlight indexing, Handoff, the system Hide My Email surface; everything else does.

Does Epistles work on Apple Watch?

Yes, with the full triage feature set: archive, snooze, voice or template reply, the Reply & Done composite action, pin, forward, and agenda RSVP. WidgetKit complications surface unread counts on watch faces that support them. The same feature set runs on Wear OS for Galaxy Watch, Pixel Watch, and any Wear OS 3+ device, so a household on mixed phones doesn’t lose the watch story.

A line at the end

Apple Mail is a good email client for the inbox shape Apple designed it for: one iCloud address, one ecosystem, one set of devices all stamped with the same logo. If that’s the shape your life takes, keep it. If your inbox crossed the boundary, the front door for Epistles is here, and iCloud sits inside as a first-class provider alongside everything else.