Migration guides, engineering notes, and the occasional opinion on European digital sovereignty, written by the people building email.eu.
Client-side filters only work when the app is open, which is why your phone shows an unsorted inbox. Server-side rules run on delivery, once, for every device. A rule builder and a raw Sieve editor in the webmail, rules written in other clients preserved, and the plus-addressing trick that needs no rules at all.
Read the latestSome addresses do not deserve an inbox. Free unlimited forwarding to anywhere, no copy kept, no seat used, plus the honest part most providers leave out: what forwarding does to SPF and DKIM, and when to use an alias instead.
Addresses are not accounts, so we do not bill them like accounts. How aliases work, why you can send from them and not just receive, what a catch-all really costs you, and the alias-domain feature that makes rebrands and acquisitions boring.
Nobody should have to look up an IMAP port. The SRV records, well-known URLs and redirects that let Apple Mail, Thunderbird and a phone set themselves up from an email address alone, and the two places it still asks you to type something.
MX, SPF, DKIM, DMARC, MTA-STS and the discovery records nobody sets up by hand. What each one does, the two families we deliberately leave out of what we recommend, and why our checker merges your existing SPF record instead of telling you to replace it.
What actually happens after you click sign up: why you pay first, the idempotent provisioning checklist that builds your workspace across five systems, and the two-step domain switch that means your mail is never in the air.
An append-only record of who changed what in your workspace, enforced in the database so no one can quietly edit it, including us. It logs every support session email.eu support opens in your workspace, and it records from day one on every plan. A Business feature to read.
Our public status page shows the same numbers we page ourselves on. Outside-in probes, watchdogs for slow-motion failures, surviving cloud maintenance, and the nightly copy that lives hundreds of kilometres away.
One Kubernetes cluster, a handful of standalone VMs, everything in OpenTofu, and deploys that are git commits. Why the unfashionable half of our design is deliberate, and four infrastructure rules that hold with no exceptions.
A workspace is only one product if it has one front door. How Authentik signs one account into seven products, what multi-tenant identity actually takes, and why the login service gets mail-grade paranoia.
Everyone says don't run your own mail server. We do it for a living. Two-node clustering, deliverability as boring correctness, why inbound hygiene is outbound reputation, and monitoring that connects the way a real mail client does.
Seven substantial pieces of software power email.eu and we wrote almost none of them. Stalwart, Bulwark, La Suite Drive, Zulip, La Suite Meet, Authentik and Lago: the four tests every component had to pass, and the choices we got wrong first.
One sentence in our internal docs has decided more arguments than anything else we have written: EU suppliers only, no US vendors anywhere in the product or its dependencies. What that rule ruled out, what it bought, and how we live by it. Part 1 of a series on how we built email.eu.
Your email, files and calendars at email.eu live in open, standard formats you already own, reachable over the same protocols the whole internet runs on. Here is what that means in practice, and why portability is one of the features we are proudest of.
"EU-only" is easy to say and hard to check. Here is our actual list, every subprocessor, where it sits, and what it can see, plus the honest edge cases, including the US dev tooling, that most providers leave out.
The trick to leaving Google Workspace is never having a scary cutover day. Set up and test everything while Google still delivers your mail, then switch one DNS record at the end. Here is the weekend plan.