Fastmail vs iCloud Mail for Apple Users: Custom Domains and Rules

Fastmail vs iCloud Mail for Apple users is not really a fight about which service handles mail better. Both deliver reliably, both work in Apple Mail on Mac, iPhone and iPad, and both let you send from a custom domain. The difference shows up once your setup gets more demanding than one address and a handful of folders.

iCloud Mail is built into the operating system you already use, and Apple has quietly made it capable — custom domains, aliases, Hide My Email, server-side rules. What it hasn't done is remove the ceilings. Fastmail costs money and needs twenty minutes of DNS work, and in exchange removes almost every ceiling iCloud leaves in place.

This post compares them on the six dimensions that actually decide it: custom domains, aliases and masked addresses, server-side rules, search, Apple Mail integration, and what happens the day you want to leave. Every capability below was checked against Apple's and Fastmail's own live pages in September 2026 — recheck before you commit, since both vendors change limits without announcing them.

The verdict up front#

For most Apple users with simple needs, iCloud Mail is the right answer and switching would waste money. One address, a few folders, mail that syncs everywhere without configuration — iCloud already does that, included with the Apple Account you have.

Fastmail earns its price the moment you need one of four things: more than three addresses at your own domain, a catch-all address, rules more complex than a pop-up menu allows, or the ability to leave without your addresses dying with the subscription. If none of those describe you, stay on iCloud.

• Custom domains — Fastmail wins clearly. iCloud allows up to five domains but only three addresses per domain, and no catch-all.
• Aliases — Fastmail wins. iCloud caps you at three @icloud.com aliases and makes you wait seven days after deleting one.
• Server-side rules — Fastmail wins. iCloud's rules are real and server-side, but editable only on iCloud.com.
• OS integration and setup effort — iCloud wins outright. Nothing else is one toggle in Settings.
• Hide My Email / masked addresses — a genuine draw, with different strengths.
• Portability — Fastmail wins, and this is the one people regret ignoring.

Fastmail vs iCloud Mail at a glance#

Can iCloud Mail use a custom domain? Yes, with three ceilings#

This is the question most people arrive with, and the short answer is yes. Apple's Custom Email Domain feature lets you point a domain you own at iCloud Mail and send and receive from it in Apple Mail on every device. It needs an iCloud+ subscription, an Apple Account with two-factor authentication on, and iCloud Mail switched on.

The ceilings are where it gets interesting. Apple documents support for "up to five custom domains, with up to three personalized email addresses per domain." Three — not per person, three addresses total on that domain.

For a household that's often fine: you, your partner, and one shared address. For a small business or side project on its own domain, three is the number you hit in the first month. There's also no catch-all, so a message to an address you never created simply bounces.

Where Fastmail wins: addressing you can actually design#

Fastmail treats addresses as something you generate freely rather than ration. Aliases are included with the account — Fastmail documents a limit of 600 aliases plus 15 per user, a cap in name only.

The two features that actually change how you use email are catch-all and subdomain addressing. A catchall or wildcard alias sends every message addressed to anything at your domain into one mailbox, so you can invent an address on the spot at a checkout page and it works without creating anything first.

Subdomain addressing goes further. Instead of the familiar plus-addressing form, Fastmail lets you receive at addresses shaped like [email protected], configurable per domain in Settings — the same idea as plus addressing, minus the well-known problem that many signup forms reject a plus sign.

None of this exists on iCloud Mail: plus addressing and three named addresses per domain is the whole shape of the system. If you want a different address for every vendor so you can see who leaked it, Fastmail is built for that and iCloud is not.

iCloud Mail server-side rules: limitations that matter#

Credit to Apple first — iCloud Mail rules are genuinely server-side. They run on Apple's infrastructure whether or not any of your devices are awake, more than several paid providers offer. Apple documents a limit of 500 rules and warns it can take "up to 15 minutes for new or changed rules to take effect on incoming emails."

The limitation isn't the count, it's that you can only create and edit them in one place: Mail settings on iCloud.com. Apple Mail on macOS has no editor that writes server-side iCloud rules — its own rules are local to that Mac and stop working when the lid closes.

So the everyday reality is a browser and pop-up menus over a text field. Simple sorting works fine. Anything conditional, time-based, or dependent on more than one test at once has nowhere to live.

Fastmail's answer: rules first, Sieve underneath#

Fastmail gives you the same point-and-click rules for ordinary cases, then puts a real filtering language underneath for the rest. In Settings under Filters & Rules there's an option to edit custom Sieve code, and Fastmail is upfront that "Sieve can be difficult to use, and is generally suitable for users with a high technical ability."

Most people never open it. But if you want a rule that behaves differently outside working hours, or checks three headers and a list membership before filing anything, Sieve is where that lives — and you can import and export those scripts as files, so your filtering setup is something you can back up and move.

Sieve is also a published standard rather than a vendor feature: logic you wrote once isn't stranded if you change your mind about the provider.

Search, and why it is hard to compare honestly#

Fastmail markets search heavily — the feature page's line is "Search that really finds stuff." In practice, search quality is the hardest dimension here to state as fact: neither vendor publishes what its index does, and your experience depends enormously on whether you're searching in the web app or in Apple Mail.

That last part is the useful insight. Searching inside Apple Mail largely searches the local index Spotlight built on that device, whichever provider hosts the mail. Provider-side search only becomes the deciding factor in the web interface or a client that queries the server directly.

So if Apple Mail is your only client, treat search as close to a draw and don't pay a subscription for it. If you regularly work in a browser, Fastmail's web search is the stronger of the two.

The JMAP catch nobody mentions#

Fastmail's technical differentiator is JMAP — an open IETF standard, specified in RFC 8620 and RFC 8621, that the project describes as "the open protocol that replaces IMAP (and CardDAV and CalDAV)." The claims are concrete: far less bandwidth on resync, measurably lower power use than IMAP, push instead of polling.

Here's the part every comparison aimed at Apple users skips: Apple Mail does not speak JMAP. On Mac, iPhone and iPad, your Fastmail account connects over IMAP, and the protocol advantage you're reading about does not reach you.

You get JMAP in Fastmail's own web and mobile apps, and in third-party clients that implement it — a real benefit, just not one you get while staying in Apple Mail.

Where iCloud Mail wins, and it is not close#

Integration. This is the dimension we concede outright to Apple. iCloud Mail is a toggle in Settings, already signed in, and never asks for an app-specific password or a DNS record. Fastmail in Apple Mail requires generating an app password, and Apple caps you at 25 active ones and revokes them all when you change your Apple Account password.

Hide My Email is the second. It's wired into Sign in with Apple and appears the moment an app asks for your address — a placement no third-party masked-address service can match on Apple's own platforms. Fastmail's Masked Email is excellent and integrates with 1Password and Bitwarden, but it's a step you have to remember to take.

Third: cost shape. iCloud Mail's included tier is free, and if you already pay for iCloud+ storage, custom domains come with it rather than as a new bill. For a lot of people that ends the argument correctly.

One iCloud limit that catches people out#

iCloud Mail shares your single iCloud storage allowance with photos, device backups, iCloud Drive and everything else. Apple is explicit that running out of iCloud storage stops new mail arriving at your iCloud address until you free some up.

That's a different failure mode from a mail-only quota. A weekend of video and a full device backup can, in principle, cost you inbound mail. Fastmail's mail storage is its own quota, so a full photo library has nothing to do with whether an invoice arrives.

It's not a reason on its own to switch — it's a reason to check your storage headroom before putting a business domain on iCloud Mail.

Pricing model — and why there are no numbers here#

We don't print competitor prices, because they go stale and a stale number in a comparison is worse than no number. Check both vendors' own pricing pages before you decide.

What's worth knowing is the shape. iCloud Mail has a free included tier tied to your Apple Account, with custom domains gated behind the paid iCloud+ subscription that also buys storage — mail is bundled, not sold separately. Fastmail is a paid subscription in tiers, and custom domains require at least one admin on a plan above its entry tier.

Fastmail offers a trial of up to 30 days with no card required, though trial accounts are limited to five addresses and a daily send cap — use it to test rules, import and Apple Mail setup rather than to judge throughput.

Who each one is genuinely for#

• Stay on iCloud Mail if: one or two addresses covers you, your rules are simple sorting, you want zero setup, and you value Hide My Email being everywhere in the OS.
• Stay on iCloud Mail if: you already pay for iCloud+ storage and a custom domain with three addresses is all you need — you are effectively getting domain hosting for nothing extra.
• Move to Fastmail if: you run a business or project on your own domain and three addresses is already tight, or you want a catch-all.
• Move to Fastmail if: you have a list of filtering rules you cannot express, especially conditional or time-based ones.
• Move to Fastmail if: you use Windows, Android or Linux alongside Apple devices, where iCloud Mail's client story thins out fast.
• Move to Fastmail if: portability matters to you — your domain, your Sieve scripts, your exportable data, none of it tied to one hardware ecosystem.

How to move from iCloud Mail to Fastmail without losing anything#

1. 1

   Start the trial and import before you change any DNS

   Fastmail's import tool copies existing mail, contacts and calendar events from another provider. Run it first, while iCloud is still live and nothing is at risk.

2. 2

   Add your domain and pick a DNS approach

   Fastmail documents three routes: hosting your nameservers with Fastmail (its recommended option), pointing MX records only, or redirecting mail. Pick MX-only if your DNS is already somewhere you like.

3. 3

   Rebuild rules before you cut over, not after

   Open iCloud.com, screenshot your rules list, and recreate it in Fastmail. Do this while both accounts receive mail so you can compare where a message lands.

4. 4

   Keep the iCloud address alive and forwarding

   Do not delete anything. Your Apple Account address is used by services you have forgotten about. Leave iCloud Mail on and set it to forward while you update logins.

5. 5

   Change the MX records last

   Only after import, rules and forwarding are verified. Expect a period where mail arrives in both places as DNS propagates, which is normal and not a fault.

6. 6

   Update the addresses that matter over the next month

   Bank, tax, domain registrar, password manager, two-factor recovery. Work from your password manager's list rather than memory.

A third option, honestly#

Both services above are mail hosts — they own the mailbox, the domain records and the delivery. There's a second decision underneath that one, which is what you actually read and reply in, and it's the decision this comparison doesn't settle. We build AI Emaily, and that's the layer we work on: a client that connects to an existing mailbox rather than replacing it.

That distinction is the honest limit. AI Emaily won't give you a custom domain, an alias, a catch-all or a masked address — those are your provider's job, and picking between Fastmail and iCloud Mail on the criteria above is still the right first step. What we add sits on top: triage that files and summarises, drafting from a Personal Context brain and per-client profiles you set rather than anything scraped from your old mail, and an agent that can act on a thread with approval required before anything sends, plus undo and an audit log.

It connects to iCloud Mail and Fastmail over IMAP, alongside Gmail, Outlook and any other IMAP account, which is useful if you end up running both during a migration. The limits are real too: our Mac app is a downloadable Electron shell around the web interface, Apple Silicon only, so it won't match Apple Mail on memory footprint or deep OS integration. There's a native iOS app. There's no permanent free tier — a 7-day free trial on Pro and Autopilot, card required, $0 if you cancel before day seven.