Custom Email Routing on Cloudflare: Build Your Own Address Book
Why a catch-all isn't always enough, how Flowmails route tables replace it with explicit literal-matcher rules, and how to switch safely.
Journal
Long-form writing about self-hosted email in D1, Workers-native routing, the REST API, and the parts of the platform that show up in the security review.
Categories
Tags
6 of 22 posts match
Why a catch-all isn't always enough, how Flowmails route tables replace it with explicit literal-matcher rules, and how to switch safely.
The shape of the Flowmails API, when to use webhooks vs polling, and a worked example of inbound-to-ticket automation in 30 lines.
Running your own Postfix / Exim / Dovecot stack is a real ops burden. Cloudflare Email Routing + a Worker gives you a self-hosted email platform without running an MTA — the runtime is the same one as the rest of your stack.
Cloudflare Email Routing + a small Worker + a D1 schema is enough to route inbound mail into a ticket pipeline. Here's the minimum viable ticket system and the schema behind it.
The Resend → Flowmails migration is mostly swap-the-SDK, but DNS, webhook fan-out, and template portability all have to land in the same PR. Here's the 8-step order that keeps the cutover reversible.
Cloudflare Email Routing auto-signs DKIM for the zone. You still publish SPF and DMARC yourself. Here's what each record does, the exact strings to use, and how to monitor your alignment.