Journal
Long-form writing about provider-connected email, provider-native routing, the REST API, and the parts of the platform that show up in the security review.
Categories
Tags
10 of 25 posts match
A suspended HTTP request dies on the edge long before the verification mail arrives. The wait is a row instead of an open connection: the platform answers immediately, the agent polls, and the answer survives the disconnect.
Mail without operating an MTA: Cloudflare Email Routing plus one hosted worker gives you a full mail surface on the same runtime as the rest of your stack — no MTA, no Dovecot, no SpamAssassin.
Cloudflare Email Routing handles inbound. For sending, you need Email Services + a Worker. Here's the REST API contract for outbound send, how the threading shape works, and how Flowmails wraps it.
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.
Receive email events in a Cloudflare Worker: HMAC-SHA256 signature verification, retry schedule, idempotency key (SMTP Message-ID), and the failure modes that catch teams out.
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.
Why most transactional-email providers are overkill for a small team, and how one provider connection plus an API key gets you there in a day.
Why a catch-all isn't always enough, how Flowmails route tables enforce an address allow-list per domain, and how to switch safely.
The shape of the Flowmails API, how the durable event log and the durable wait replace polling, and a worked example of inbound-to-ticket automation in 30 lines.