Best Email Client for Fastmail (2026): Ranked for JMAP, Server Rules and Masked Aliases

Fastmail users tend to be deliberate about tooling. If you picked a paid, standards-first mail host on purpose, you probably want a client that inherits what Fastmail already does well — server-side rules written in Sieve, JMAP as a first-class protocol, masked aliases you can spin up per site — rather than a client that quietly rebuilds those things on top and puts you a step out of sync with your own inbox.

That is the axis most "best email client for Fastmail" roundups skip. They compare features in the abstract — search speed, keyboard shortcuts, snooze — as if Fastmail were just another IMAP endpoint. The real decision here is how much of the work stays on Fastmail's servers and how much you hand to a client-side layer, because a client-side rule and a Sieve rule doing the same job in different order is how a Fastmail inbox turns messy.

Top pick for most people: Fastmail's own web and mobile apps — they use JMAP end to end, they render server-side rules and masked aliases exactly as designed, and they need no setup. If you want a native desktop client: Apple Mail on macOS/iOS is the easiest and most reliable IMAP fit. If you want a JMAP-native third-party client: Mailmate on macOS is closer to the protocol than anything else on this list. If you want AI triage and drafting on top of the account: AI Emaily connects to Fastmail over IMAP and leaves your Sieve rules in place — we build it, and we're honest below about where we are and are not the right answer.

How we compared#

We checked each client against Fastmail's own live documentation and each vendor's current setup page, not old forum threads. Fastmail publishes its own third-party setup instructions per client family, and we treated a client as "documented by Fastmail" only when Fastmail's help centre still lists it as of this writing, dated August 2026.

We ranked on four things a Fastmail user actually feels day to day, not on speed benchmarks or UI polish. First: does the client speak JMAP, or does it use IMAP over Fastmail's JMAP-first stack? Second: does the client honour Fastmail's server-side rules and folders as they are, or does it re-file mail with a second parallel ruleset? Third: does the account support masked aliases in the compose flow, or do you have to leave the client to generate one? Fourth: what does app-password setup look like when two-factor is on — is it a link the client sends you to, or a manual copy-paste from Fastmail's settings.

We did not compare on Fastmail-agnostic things — search algorithm, keyboard shortcut density, calendar UI — because those apply the same whether the mail comes from Fastmail or Gmail. The whole point of picking a client for Fastmail specifically is the four things above.

• Protocol fit — JMAP-native, IMAP-only, or JMAP-with-IMAP-fallback
• Whether the client preserves or duplicates Fastmail's server-side Sieve rules
• How masked aliases behave in the composer — first-class, awkward, or unavailable
• App-password and 2FA setup — Fastmail-guided or manual

Fastmail client options, compared#

One pattern before the table: the JMAP column is short for a reason. Fastmail co-authored JMAP and its own apps use it end to end, but adoption in third-party clients is still thin — most "Fastmail-compatible" clients are speaking generic IMAP against an endpoint that also happens to speak JMAP. That is not the same thing, and it matters for how Fastmail-specific features (labels vs folders, masked email, snooze) round-trip.

How Fastmail's server-side layer changes the picture#

Most email clients assume they are the smartest thing in the pipeline — client rules, client-side filters, client-side categorisation. Fastmail is the case where that assumption is wrong. Fastmail runs Sieve on its own servers, applies your rules before any client sees the message, and hands the already-sorted mail out over IMAP or JMAP. That is why a Sieve rule and a client filter that look identical on paper will collide in practice: the Sieve rule has already moved the mail to a folder your client's filter can no longer see arrive in the Inbox.

The practical consequence is a small design choice, and it is worth making on purpose. Either you keep the intelligence server-side — write your triage in Sieve, keep the client's own rules empty, and let every client you use inherit the same sort — or you keep it client-side, in which case any second client sees an unsorted Inbox because the client that did the sorting is elsewhere. Mixing the two is what produces the classic Fastmail complaint: "my rules work on the web but not on my phone," which is almost always a client-side rule masquerading as a server one.

This is also why AI clients that promise to "learn your triage patterns" need careful placement on a Fastmail account. If the AI layer is client-side and Sieve is server-side, they have to divide the work — Sieve for the deterministic filing you already know you want (newsletters, receipts, calendar invites, everything from the domain of a specific vendor), the AI layer for the shades of grey Sieve is bad at ("this looks like a real prospect," "this reply is waiting on me"). Any client that tries to own both usually ends up fighting Sieve rather than complementing it.

The tools#

**1. AI Emaily — AI triage and drafting on top of your Fastmail account, with Sieve intact.** We build AI Emaily and are naming that up front. We connect to Fastmail the same way any well-behaved IMAP client does: you generate an app password in Fastmail's settings, add the account, and Fastmail applies your Sieve rules before we ever see the mail. That is the point: AI Emaily's Rules Brain and Copilot run *after* Sieve has already filed the obvious things, so they focus on the judgement calls that server-side rules are bad at — "this reply is waiting on you," "this looks like a real prospect," "this newsletter never gets read." We are approve-before-send by default, we do not train on your mail, and BYOK is available if you want to route AI through your own provider key. The honest limits: we speak IMAP to Fastmail, not JMAP, so a Fastmail-authored primitive like masked aliases has to be generated on fastmail.com rather than in our composer, and Fastmail-specific snooze does not round-trip because IMAP does not carry it. If you want an AI layer that respects Sieve rather than replacing it, we are a good fit. If what you want is a JMAP-native mail client with no AI at all, we are the wrong answer and Mailmate below is closer. AI Emaily is a paid subscription with a 7-day free trial on Pro/Autopilot; there is no permanent free tier.

**2. Fastmail's own apps — the top pick for most Fastmail users.** Web, iOS, and Android. These are the only clients on this list that speak JMAP to Fastmail end to end, which is what Fastmail authored the protocol for. Masked Email is a first-class composer action, snooze round-trips because it is a Fastmail primitive rather than an IMAP one, and your Sieve rules are the source of truth for everything — there is no second ruleset to keep in sync. Packaging is a paid subscription across Individual, Duo, and Family plans with a 30-day trial; there is no free tier, so if you were expecting one, that is not how Fastmail is sold. The trade-off is what you would expect: Fastmail's apps are excellent as mail clients, and they are not trying to be an AI-native inbox — no agent, no auto-drafting, no semantic search across everything you have ever received.

**3. Apple Mail — the easiest native desktop and mobile client.** Fastmail publishes a Mail configuration profile that sets Apple Mail up on macOS and iOS in one download, and after that it is just IMAP and SMTP with your Fastmail app password. Sieve rules keep running server-side, Spotlight indexes the local cache, and the whole thing feels like Apple's built-in mail because that is what it is. What you give up: masked aliases and snooze are Fastmail primitives that IMAP does not carry, so the composer will not offer them and you generate them on fastmail.com when you need them. If your workflow is "open the Mail app on my Mac, hit reply, move on," this is the shortest path that keeps Fastmail's server rules intact.

**4. Mozilla Thunderbird — the free, cross-platform default.** Thunderbird speaks generic IMAP, connects to Fastmail with an app password, and works on Windows, macOS, and Linux. It is the only credible answer on this list for anyone on Linux, which alone can decide it. Sieve rules keep running server-side and Thunderbird's own message filters can layer on top for local-only things (archive to a local folder, mark as read after a week) without stepping on them, as long as you resist the urge to duplicate a Sieve rule client-side. Thunderbird's add-on ecosystem includes Sieve editors that let you write Sieve directly from inside Thunderbird, which is worth knowing about if you like your rules editor and your mail reader in the same window.

**5. Mailmate — the sharpest JMAP-native fit on macOS.** Mailmate is a small independent macOS mail client that has taken JMAP seriously for years — it has a JMAP transport mode explicitly designed for Fastmail, alongside its regular IMAP support. That matters for the Fastmail-authored primitives IMAP flattens: labels behave more like labels than like folders, Fastmail's server-side threading is honoured natively, and the account state stays closer to what the Fastmail web UI shows. **Mailmate speaks JMAP to Fastmail natively in a way AI Emaily does not — for someone who wants the sharpest standards fit, Mailmate is the more accurate answer, and this is the one place we are conceding a dimension outright.** The trade-offs: macOS only, single-developer independent product, no AI layer, and the interface is unapologetically power-user (rules use IMAP search expressions, key bindings assume you like key bindings). If that description sounds like a feature, it will be one.

**6. eM Client — full-featured Windows/macOS IMAP client.** eM Client connects to Fastmail with a standard IMAP + SMTP + app-password setup and covers most of the desktop mail-plus-calendar-plus-contacts territory. Sieve rules stay server-side, and eM Client's own rules layer on top after the fact — which is fine so long as you keep the two rulesets doing different jobs rather than the same one twice. Packaging is a free tier for personal use with paid tiers above; check emclient.com for current limits and any changes to what the free tier includes. Fits someone who wants a mature, feature-dense desktop client on Windows or macOS and does not need AI drafting.

**7. Canary Mail — cross-platform with a client-side AI layer.** Canary connects to Fastmail over IMAP, runs on Windows, macOS, iOS, and Android, and adds its own AI triage and drafting on top of whatever account you give it, Fastmail included. That is exactly the case where the server-side vs client-side conflict warning above matters: Sieve has already done its filing before Canary sees the mail, and Canary's AI triage runs on the same messages a second time. It can work well — a lot of Fastmail users run this stack — but it is worth thinking about which layer owns which decisions before you turn everything on. Packaging is tiered with a free option and paid tiers; check canarymail.io for current shape.

**8. Spark by Readdle — polished cross-platform client with a caveat.** Spark connects to Fastmail with an app password and is one of the smoother-looking clients on iOS and macOS in particular, with team features layered on top of personal mailboxes. The caveat is architectural: Spark historically routes mail through Readdle's own servers to power features like push notifications and shared conversations, so your Fastmail tokens are held server-side by Readdle rather than living only on your device the way they would with Apple Mail or Thunderbird. Read Readdle's current privacy documentation and decide whether that fits how you picked Fastmail in the first place — for some Fastmail users this is a dealbreaker, for others it is unremarkable, and the honest thing is to name it rather than skip it.

Server-side rules or client-side AI — how to divide the work#

This is the section most Fastmail-and-AI-client roundups avoid because it does not have a clean answer, and it is the section that decides whether the client you pick makes your inbox better or noisier.

Server-side Sieve is where the deterministic decisions belong. If you can name the rule out loud — "everything from Stripe goes to the Receipts folder," "anything from my domain's calendar system skips the Inbox and goes to Invites," "newsletters from these ten senders go to the Reading folder" — Sieve is the right layer for it. It runs before delivery, it applies to every client you use, and it will still be there in five years regardless of which mail client is fashionable.

Client-side AI is where the judgement calls belong. "This reply is waiting on me," "this looks like a real prospect and not a template blast," "this newsletter I subscribed to six months ago is one I never open" — Sieve is bad at all of these, because they are pattern recognition, not rule matching. An AI layer that runs after Sieve has already handled the deterministic filing has room to do the interesting work without stepping on the boring work.

The failure mode to avoid is a client-side layer that tries to own the whole triage, because that puts it in direct conflict with rules Fastmail has already applied. If you turn on aggressive client-side auto-categorisation in Canary, eM Client, or Spark alongside a full Sieve setup, expect at least one thing to be wrong at any given moment, and expect it to be very hard to tell which layer misfiled it. Pick one owner per class of decision.

Setting up any of these — the parts that are always the same#

1. 1

   Turn on two-factor and generate an app password

   In Fastmail settings, enable two-step verification if it is not already on, then generate an app password specifically for the client you are adding. Give it a name you will recognise later so you can revoke that one client's access without touching the others.

2. 2

   Use the app password, not your Fastmail login password

   Third-party clients need the app password, not the one you use on fastmail.com. If your client keeps rejecting the login, this is almost always the reason — Fastmail deliberately does not accept your web password over IMAP/SMTP once two-factor is on.

3. 3

   Point the client at Fastmail's servers

   IMAP: imap.fastmail.com on port 993 with SSL. SMTP: smtp.fastmail.com on port 465 with SSL. Auto-discovery works in most modern clients, so you usually only enter the email address and app password and the rest fills in.

4. 4

   Do not import your Sieve rules as client rules

   This is the mistake that turns Fastmail into a mess. The rules you already have in Fastmail keep running on the server for every client you connect. If you also copy them into the client, both layers act on the same mail — leave the client's own rules empty (or reserved for genuinely client-local things) and let Sieve stay the single source of truth.

5. 5

   Decide where masked aliases will live in your flow

   Masked Email is a Fastmail-authored feature and only Fastmail's own apps expose it in the composer. On every third-party client you will generate masks on fastmail.com or through the 1Password integration, and paste the resulting address into the site or form. This is fine — it just needs to be a habit, not a surprise.

How to choose for your situation#

If you use Fastmail mostly through a browser and a phone and want the least setup: stay on Fastmail's own web, iOS, and Android apps. They are the only clients that speak JMAP end to end and the only ones where masked aliases, snooze, and labels behave the way Fastmail designed them. You lose nothing worth losing.

If you are on macOS or iOS and want a native mail client with no third-party layer in the middle: Apple Mail. Fastmail publishes a configuration profile that sets it up in a click, Sieve rules stay intact, and the whole thing feels like the built-in mail app because it is.

If you are on Linux, or you want a fully open-source client across every desktop: Thunderbird. It will not be the prettiest option on any of these platforms, and it will be the only real option on Linux.

If you care about JMAP and standards fidelity more than about any other feature, and you are on a Mac: Mailmate. This is where we are the wrong answer and Mailmate is the right one, and it is worth saying directly.

If you want AI triage, semantic search, and an agent that drafts replies in your Personal Context — layered on top of a Fastmail account whose Sieve rules and masked aliases keep working exactly as they do now: AI Emaily. Connect over IMAP with an app password, keep Sieve as the source of truth for the deterministic filing you already have, and let the AI layer own the judgement calls. We are approve-before-send by default and do not train on your mail. See the Fastmail connection notes in our docs for the exact steps.

If you are on a Fastmail Business plan, note the packaging catch: Fastmail's own Basic business tier does not include third-party app access at all — you need Standard or Professional for any of the clients above to connect. That is on Fastmail's live pricing page and worth checking against current wording before you commit.