Notion Mail is gone. The reason they gave is the interesting part.
Notion Mail's inbox shut down on 22 September 2026. Notion's own explanation is the part worth sitting with: more than half of its email users never opened the inbox at all — they handed the whole thing to agents. Notion read that and concluded the inbox was obsolete. I read the same fact and conclude something else, and I'll argue for it below. First, the practical part, because some of you are landing here with a dead app.
What happened, from the official notice
Notion announced the shutdown on 25 June 2026 and closed the inbox on 22 September 2026. The last day to export Notion Mail-only data was 21 September. The details are in Notion's help page; the reporting is at TechCrunch.
What you still have, and what is actually gone
The good news is bigger than the bad news, and it is worth reading before you panic about your archive.
| Thing | Status |
|---|---|
| Your email — every message sent and received | Safe, in Gmail. Notion Mail always synced two ways, so the mail itself never only lived there. |
| Drafts, scheduled sends, snippets, auto-label instructions | Gone if you did not export by 21 September. These were Notion Mail-only data. |
| Custom views and sorting | Gone. Notion states these do not transfer to Gmail. |
| Synced email databases in your workspace | Still readable; they stop receiving new mail. |
If you missed the export window, the honest answer is that the snippets and label instructions are not coming back, and no third-party tool can recover them — they lived in Notion's service, not in your mailbox. What you rebuild, you rebuild from scratch. That is the real cost of this shutdown, and it is small only because the mail itself was mirrored.
The sentence Notion said out loud
Vendors rarely tell you why a product died in a way that is useful to anyone else. Notion did: most of the people paying for an inbox were not using the inbox. Agents were reading, triaging, and replying, and the human opened the app to check on the agent, if at all.
Notion's conclusion was that the destination is obsolete — put the mail in front of agents and stop maintaining a place for people to look. I think that reads the fact correctly and then draws exactly the wrong line from it. If an agent is handling your mail, the interesting question stops being "what does my inbox look like" and becomes "what did it do while I wasn't looking, and how would I know if it got one wrong?" Deleting the inbox does not answer that question. It removes the only place the answer could have been displayed.
That is the bet Klorn is built on, so treat this as a disclosed interest rather than a neutral survey. The wager is that when software acts on your mail, two properties stop being nice-to-haves: a measured floor on what it is allowed to hide from you, and a record of what it did that you can check afterwards. Neither is a UI feature. Both have to be in the part that decides.
Where to go now — honestly
No benchmark was run across these products; I have not measured anyone's classifier but my own, and I am not going to pretend otherwise. Prices below were read from each vendor's own pricing page on 14 September 2026.
| Option | Best at | The catch |
|---|---|---|
| Gmail as-is + filters and labels | Free, nothing to migrate, rules you can read and edit forever. | Rules cannot generalize. Every new sender is a new rule you write by hand. |
| Gemini in Gmail (Google AI Plus, $9.99/mo) | Cheapest AI path and the deepest possible Gmail integration — it is the platform owner. | Gmail only, and nothing about the decision is inspectable. No published miss rate, no record you can audit. |
| Superhuman Mail ($25/user/mo annual in the Starter suite, $33 Business) | The fastest keyboard-driven mail client there is. If speed of handling is your bottleneck, it is genuinely the best product here. | Sold only inside a suite, and closed — same audit problem. |
| Shortwave ($30/seat/mo Business) | The strongest AI search and assistant over your own mail history. | Closed, and priced per seat at the top of this band. |
| Inbox Zero (AGPL, open source) | The closest open-source analogue, and more mature than us at bulk cleanup and unsubscribing. If that is your problem, start there. | Different shape: it optimizes for emptying an inbox, not for deciding what may interrupt you. |
| Klorn (AGPL, this site) | Five lanes with only one allowed to notify you, a CI-enforced floor on urgent recall, a receipt for every action taken for you, a hard spend cap, and a self-host path. | Younger and smaller. Gmail and IMAP today; Microsoft 365 is written but not switched on. Fewer people have used it than any other row in this table. |
If the lesson you took was "never again"
The migration you just did was cheap because the mail was mirrored in Gmail. The next one might not be. The version of this that cannot happen to you is the one where the software runs on your own box:
git clone https://github.com/k08200/klorn.git
cd klorn
cp .env.selfhost.example .env.selfhost
# fill in: postgres password, JWT secret, encryption key,
# your own Google OAuth client, one LLM provider key
docker compose --env-file .env.selfhost -f docker-compose.selfhost.yml up -d
Images are prebuilt, so there is no toolchain to install. The full walkthrough, including what self-hosting does not remove, is at klorn.ai/self-host.
What to actually do this week
- Confirm your mail is intact in Gmail. It should be — the sync was two-way — but check a thread you remember from Notion Mail.
- Rewrite the handful of snippets you used daily. Most people have three or four, not thirty.
- Write down what your auto-labels were doing before you pick a replacement. That list is your requirements document, and it is the only artifact from Notion Mail you can still reconstruct from memory.
- When you evaluate the replacement, ask it one question the closed products cannot answer: how often do you hide something urgent, and how would I check?
For our part, that number is published and gated in CI: on a committed 56-email set, a change to the judge does not merge unless it holds at least 90% recall on urgent mail and at least 90% precision on the silent lane. The last full sweep ran ten models three times each; across the 23 clean runs, the count of urgent emails sent to the hide-forever lane was zero. Details, including the models that failed the gate, are in the bake-off writeup. Every number re-runs from the repository with one command.
Try Klorn free