Twake Mail

What Twake Mail can do

• JMAP email on three platforms Read and manage mail over the JMAP protocol on web, Android, and iOS from one Flutter codebase, with published store apps and Docker web images.[1]

• Any JMAP server support Point the app at your own JMAP server URL; the project FAQ confirms it works with any JMAP server, not only the Twake Mail backend.[1]

• PGP encryption Protect message content with PGP data encryption as presented on the official site, aimed at keeping professional mail private.[1]

• Spam and threat protection Filter spam, phishing, and hacking attempts with the built-in spam shield and threat detection described on the official site.[1]

• Custom filters and search Shape the inbox with custom filters by criteria such as period and keywords, and search by recipient or keyword across all mailboxes or specific folders.[1]

• OIDC and basic login Sign in through an OIDC identity provider with automatic detection on web and mobile, falling back to basic authentication against the JMAP server.[1]

Who Twake Mail fits

• Privacy-minded teams leaving hosted mail Inference: teams that want a self-hosted, AGPL-licensed mailbox with PGP encryption fit Twake Mail's documented security and Docker self-hosting design.[1][2]

• Organizations adopting JMAP Inference: operators running a JMAP server who need modern web and mobile clients fit the app's any-server JMAP compatibility.[1]

• Twake and Linagora workplaces Inference: workplaces already standardizing on Twake services fit the mail app's workspace integration, including the application grid for sister services.[1][2]

Limitations to weigh

• Moderate self-hosting effort Inference: JWT key generation, a JMAP backend, and account provisioning put self-hosting above one-click installs for operators.[1]

• JMAP server required The app is a mail client, not a complete mail server; it needs a JMAP backend such as tmail-backend or another compatible server.[1]

• Unknowns preserved Offline use, data-region lists, enterprise support terms, team-size guidance, and acquisition status are not documented, so they are recorded as unknown rather than assumed.[1][2]

Deployment and compatibility