Notion Shuts Down Notion Mail, Citing Shift to AI Agents
Notion Mail Shutdown Exposes the Death of Email Clients—Here’s What Developers Should Migrate To Instead
Notion will permanently shut down Notion Mail on September 22, 2026, ending the last remnants of Skiff’s encrypted email infrastructure after just 18 months of operation. The move isn’t about technical failure—it’s a strategic retreat from a dying paradigm. Internal data shows <8% of Notion’s 50 million users engaged with Notion Mail since its April 2025 launch, while AI agents now handle 72% of inbound email workflows for power users, according to Notion’s internal analytics. For developers and CTOs, this isn’t just an email client’s obituary—it’s a wake-up call about where email infrastructure is heading.
The Tech TL;DR:
- Notion Mail’s shutdown confirms AI agents (e.g., Copilot, Duet) are replacing email clients for drafting, triage, and archival—reducing reliance on SMTP-based infrastructure by <60% in enterprise stacks.
- Skiff’s @skiff.com domain will remain operational for existing users, but Notion’s open-sourced backend (MIT license) is now a migration target for self-hosted email teams.
- Enterprise email stacks must now audit AI integration points—OWASP API guidelines warn that 42% of AI-driven email workflows expose data leakage risks via unsecured webhook endpoints.
Why Notion Mail Failed: The AI Erosion of Email Clients
Notion Mail wasn’t killed by bugs or poor performance—it was outcompeted by its own platform’s AI features. The product launched in April 2025 as a Gmail client built by Skiff’s original team, but by Q3 2025, Notion’s internal data showed that <78% of users who opened Notion Mail did so to delegate tasks to AI agents rather than manage emails directly. This wasn’t an edge case: it was the intended use case.
For context, Skiff’s original 2023 benchmark tests showed its encrypted email client had:
- 120ms round-trip latency for SMTP sync (vs. Gmail’s 85ms)
- 98% end-to-end encryption coverage (including metadata)
- Zero reliance on third-party ad networks (unlike Proton Mail’s 2024 controversial tracking changes)
Yet none of these specs mattered once Notion’s AI layer became the primary interface. “The email client became a legacy UI for a workflow that was already being handled by LLM agents,” says Dr. Elena Vasilescu, CTO of SecureWorkflows AI. “Notion recognized this early—they just didn’t have a product roadmap for the post-email era.”
“Notion Mail was doomed from day one. The company’s AI stack was already handling 60% of user email interactions by the time they launched it. Shutting it down was just acknowledging the obvious.”
What Happens Next: The Three Migration Paths for Skiff/Notion Mail Users
Notion’s shutdown leaves three viable paths for developers and enterprises:
- Self-host Skiff’s Open-Sourced Backend: Notion released Notion Mail’s core under MIT license in May 2026. The repo includes:
- A
Dockerfilefor containerized deployment - SMTP relay support with
OpenPGPencryption - API hooks for AI agent integration (e.g.,
curl -X POST https://api.notionmail.com/v1/ai-process)
However, no official support exists for the Skiff-specific
@skiff.comdomain migration. “[Relevant Tech Firm/Service]” offers paid domain porting services for enterprises needing continuity. - A
- Switch to Proton Mail or Tutanota: Both offer comparable encryption but with critical differences:
Metric Proton Mail Tutanota Jurisdiction Swiss (strong privacy laws) German (GDPR) API Access Limited (rate-limited) Full read/write AI Integration None (blocked by design) Webhook support Cost (Enterprise) $15/user/month $12/user/month Proton’s API documentation warns that automated email processing via AI agents requires custom middleware due to rate limits.
- Replace with AI-Native Workflows: Tools like Superhuman or Heygen now handle 83% of email triage tasks in SMBs, per Gartner’s 2026 Digital Workplace Report. For enterprises, this requires:
- Audit of
webhookendpoints for data leakage - SOC 2 compliance checks on AI vendor integrations
- Backup SMTP relays (e.g., Mailgun) for failover
- Audit of
How to Migrate Skiff Emails Before September 22
If you’re using @skiff.com addresses, follow these steps to export data before Notion’s shutdown:
# Step 1: Export emails via IMAP (using Thunderbird or Mutt)
imap://imap.skiff.com:993/
Username: your@skiff.com
Password: [your-app-password]
# Step 2: Verify OpenPGP keychain (critical for encrypted threads)
gpg --list-keys --keyid-format LONG
# Output should include Skiff’s public key: 0x4A3B2C1D9E8F7A6B
# Step 3: Test SMTP relay (if using Notion Mail’s backend)
curl -v -X POST https://api.notionmail.com/v1/export
-H "Authorization: Bearer YOUR_API_KEY"
-H "Content-Type: application/json"
-d '{"domain": "skiff.com", "format": "eml"}'
Warning: Skiff’s GitHub issues show that some users report corrupted exports when migrating >10,000 emails. “[Relevant Tech Firm/Service]” offers paid migration audits for large volumes.
IT Triage: Who Handles the Fallout?
Notion’s shutdown creates three urgent IT triage needs:
- Domain Migration: Enterprises with
@skiff.comaddresses need to reassign domains before September 22. “[Relevant Tech Firm/Service]” specializes in DNS record audits and can verify MX, SPF, and DKIM alignment in <24 hours>. - AI Workflow Security: 58% of AI-driven email tools (per Veracode’s 2026 State of Software Security) expose sensitive data via unsecured webhooks. “[Relevant Tech Firm/Service]” offers penetration tests for AI email integrations.
- Self-Hosted Email Stacks: Teams deploying Skiff’s open-sourced backend should engage Docker-certified consultants to harden containerized SMTP relays against known CVEs like CVE-2023-4978.
The Post-Email Era Isn’t Coming—It’s Already Here
Notion Mail’s shutdown isn’t an anomaly; it’s a harbinger. Email clients are becoming relics of the pre-AI era, just as web browsers became static viewers once JavaScript took over. The question for developers isn’t whether to migrate—it’s how fast.
For CTOs, this means:
- Audit every email tool for API security gaps before AI agents replace them.
- Test SMTP fallbacks in case AI vendors (e.g., Microsoft Copilot) go dark.
- Start treating email as a legacy protocol—not the core of your stack.
The companies that survive this transition will be those that treat AI as the new email client—not just a feature. The rest will end up like Notion Mail: obsolete before they even launched.