FairEmail: a privacy-oriented Android email client for people who bring their own address

What FairEmail is for, and who should look elsewhere

FairEmail is an email client for Android, not a mail service. The README states this plainly: "FairEmail is an email client only, so you need to bring your own email address." That single sentence defines the audience. If you already have an address at Gmail, Outlook, Yahoo or a self-hosted server, FairEmail is the reading and writing surface for it. If you are looking for a provider, this is the wrong project.

The same paragraph rules out a second group. The README says FairEmail does not support non-standard protocols such as Microsoft Exchange Web Services and Microsoft ActiveSync. An organisation whose mail is reachable only through those protocols cannot use this app, regardless of how much it likes the privacy features. Standard IMAP, POP3 and SMTP are the supported path, and the README lists those protocols alongside OpenPGP and S/MIME under open standards.

The feature list is aimed at people who value privacy and are willing to trade some convenience for it. Unlimited accounts and addresses, a unified inbox, conversation threading, two-way synchronisation, push notifications and offline storage are the baseline. On top of that sit the privacy behaviours: reformatting messages to prevent phishing, confirming before images or links are opened, attempting to recognise and disable tracking images, and warning when a message could not be authenticated. The README describes the app as deliberately minimalistic by design, so you can concentrate on reading and writing messages.

The mechanism: a foreground service, IMAP IDLE and a safe message view

The architecture visible in the README is conventional for an Android mail client, with two decisions worth noting.

First, synchronisation. FairEmail supports IMAP IDLE, which the README lists under efficiency as the mechanism behind push messages. Rather than polling on a timer, the client holds an IDLE connection so the server can tell it when new mail arrives. The README also claims battery friendliness and low data usage as a consequence of this design. The app starts a foreground service with a low-priority status bar notification, which the README says exists so you never miss new emails. That notification is the price of reliable background delivery on modern Android.

Second, rendering. The README calls the message view "safe": styling, scripting and unsafe HTML are removed. Images are not loaded until you confirm, links are confirmed before opening, and tracking images are recognised and disabled where possible. The stated purpose is to prevent phishing and tracking. This is a rendering decision, not a server-side one, and it changes how mail looks compared with a client that loads remote content by default.

The repository layout reflects the rest of the stack. Top-level directories include openpgp-api for encryption support and oauth for provider authentication, with app/ holding the Android application and its Gradle build files at the root. There is no server component to deploy, because there is no server.

Installing FairEmail and setting up a first account

FairEmail is distributed as an Android APK, not through a package manager on a desktop. The README lists supported download locations: GitHub releases, the Play Store, a Play Store test channel, F-Droid and IzzyOnDroid. Two AppGallery and Amazon entries are struck through, and the README notes that the APK Amazon repackaged is incomplete.

The README is explicit about which builds count: "Only the versions in the Play Store and GitHub are official releases. Support for other releases from alternative app stores, etc. is limited." It also warns that the GitHub version is updated more often than the Play Store version and will check GitHub for updates automatically, a behaviour that can be turned off in the miscellaneous settings. F-Droid, by contrast, builds new versions irregularly and needs the F-Droid client for update notifications; the README advises the GitHub release if you want updates in a timely fashion, and points to a separate FAQ about the F-Droid build.

To install from GitHub you download the APK from the releases page. The README notes you may need to expand the assets section to find it:

# On the GitHub release page, expand "Assets" and download the .apk file

Because the README gives no command-line install path, there is no adb or package-manager snippet to show. Sideloading an APK on Android requires enabling installation from the relevant source in system settings, which is an Android platform behaviour rather than something FairEmail documents.

Once installed, the README describes setup as quick. You add an account with your existing address and the app connects over IMAP, POP3 or SMTP. Providers that use OAuth are handled through the oauth component in the repository. For Gmail accounts there is a constraint worth knowing before you start: the README states that after enrolling in Google's Advanced Protection Program you cannot use third party email apps anymore, and links to an FAQ entry for details.

The first real use is the same as any mail client: add the account, let it synchronise, and open the unified inbox. What differs is what happens when a message contains remote images or links. Expect a confirmation step, and expect the message body to be reformatted. If a message fails authentication, the README says you get a warning.

Where FairEmail gets in the way

The privacy controls are also the friction. Confirming images and links on every message is deliberate, and the README presents it as a defence against tracking and phishing, but it is a click you would not make in a client that loads everything. The same applies to the safe message view: stripping styling and scripting means some newsletters and transactional emails will not render the way the sender intended. That is the trade, and the README does not pretend otherwise.

Protocol support is the harder limitation. Exchange Web Services and ActiveSync are out, per the README. If your employer's mail is Exchange-only, FairEmail is not a candidate. If your provider supports IMAP, you are fine, but the README's claim of working with "virtually all email providers" rests on that assumption.

The pro features are a second boundary. The README describes them as convenience or advanced features, and the list is longer than the word "convenience" suggests: filter rules, automatic message classification, search indexing, S/MIME sign and encrypt, biometric or PIN authentication, per-account notification sounds, snooze, scheduled sending, reply templates, calendar invitation handling and a message list widget. Some of these are things a technical user would consider core. The README does not state a price, so the cost of unlocking them cannot be confirmed from the README alone.

Support scope is a third. The README limits support for non-official releases, and the F-Droid entry carries its own FAQ warning. If you install from an alternative store and something breaks, the README has already told you where you stand.

FairEmail against Thunderbird and K9 Mail

Thunderbird for Android and K9 Mail are the obvious comparisons, and the difference is one of scope rather than protocol. All three speak standard mail protocols; FairEmail's distinguishing choices are the safe message view, the tracking-image handling and the confirmation prompts, which the README presents as the app's reason to exist rather than as optional extras.

FairEmail also positions itself as an original work, stating it is "not a fork or a clone". That matters for how the project is maintained and how its code is structured, but it does not change the protocol surface: IMAP, POP3, SMTP, OpenPGP and S/MIME are the same standards the alternatives implement.

The practical difference for a switcher is the pro tier. FairEmail splits filter rules, search indexing, S/MIME sign and encrypt, and notification customisation into pro features. A client that offers those without a paid unlock has a different cost profile. The README does not compare itself to any specific competitor, so any claim about which is better on a given feature has to come from testing both, not from this documentation.

One thing FairEmail does not do is run on Windows, despite the search interest in that direction. It is an Android app. If you want a desktop client, this is not it.

Licence, maintenance and upgrade cost

FairEmail is licensed GPL-3.0, and the repository carries a LICENSE file at the top level along with an ATTRIBUTION.md. The README links the licence from a badge and lists "100% open source" as a main feature. The GPL-3.0 is a copyleft licence: if you redistribute a modified version, the obligations differ from a permissive licence. That is a general property of the licence, not legal advice, and anyone planning to ship a modified build should read the licence text rather than this paragraph.

The project is not archived and the last push was on 2026-09-22. Releases have come frequently: 1.2337 on 2026-09-17, 1.2336 on 2026-09-16, and 1.2335 on 2026-09-16. That cadence has a direct upgrade cost. The README says the GitHub release checks GitHub for updates automatically, and that this can be turned off in the miscellaneous settings. If you install from F-Droid instead, the README warns that builds happen irregularly and you need the F-Droid client for update notifications, advising the GitHub release for timely updates.

There is no self-hosted component to patch, no database to migrate and no server daemon to restart. Your upgrade work is installing the new APK, and your rollback plan is whatever your Android backup situation allows. The README mentions optional Android backup as a privacy and security property, not as a downgrade mechanism, and does not document rollback.

Editorial conclusion

Adopt FairEmail if you already have an IMAP, POP3 or SMTP mailbox and want an Android client that blocks tracking images, confirms link and image loading, and keeps no data on third-party servers. Do not adopt it if your mail lives on Exchange Web Services or ActiveSync, because the README states those are not supported, and check the download page before installing: only the Play Store and GitHub builds are called official releases, and the F-Droid build carries a separate FAQ note. Verify your provider's IMAP settings and whether you need pro features such as filter rules or S/MIME before you commit.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. M66B/FairEmail on GitHub
3. Project website
4. README
5. Releases