Blog

/

Onboarding walkthrough: set up email on your own domain

Sixty-five seconds of the whole setup: connect the provider your domains already live on, pick the domains, verify the forwarding address, choose a sending channel, and watch the first message land. One step in it is yours, and this post says which one and why — along with the earlier cut we replaced, and the reason we replaced it.

The final cut. The recording is a rendering of the flow rather than a screen capture — every frame is drawn to match what the wizard shows — so the whole path can be read in one pass.

The eleven beats

This is the recording’s own script, with the timestamps it carries. It is worth reading once before watching, because the two halves of the setup are easy to confuse: receiving is the provider forwarding mail into your mailbox, and sending is the channel your domain replies from. The recording does both, and they are configured separately.

  1. 0:00 Setup — Start here — connect a domain.
  2. 0:03 1 · Connect — Sign in with your DNS provider. No API keys to paste.
  3. 0:08 2 · Domains — Pick the domains Flowmails should route.
  4. 0:12 3 · Receive — Inbound mail forwards into your Flowmails mailbox.
  5. 0:17 3 · Verify — Cloudflare emails a verification link — you click it. Flowmails cannot.
  6. 0:25 4 · Send — Resend needs an API key. Paste it once.
  7. 0:31 4 · DNS — Then Resend verifies the domain over DNS — a few minutes.
  8. 0:37 5 · Done — Both halves live — on your own domain.
  9. 0:40 Inbox — Mail lands in the Inbox. No forwarding by hand.
  10. 0:44 Sent — Reply from the same address — it leaves in Sent.
  11. 0:54 Inbox — And when they write back, it arrives right here.

The one click that is yours

At 0:17 the recording opens a second window: your provider’s own page, with a Verify button on it. That window is the honest part of the flow, and it is the part a screenshot of the wizard usually leaves out.

When you point a domain at a new destination, the provider wants proof that whoever set this up controls the address the mail will arrive at. It proves it by sending a verification link to that address. The link has to be opened. Flowmails finds the message in the domain’s own mailbox and puts the link in front of you — and then it waits. It does not click it: the provider’s bot management rejects an automated client, so an automated click would fail even if we tried.

Click it, and the wizard notices and continues by itself. There is no button to press afterwards and nothing to paste back in.

Receiving: the provider does the first hop

Your provider still does what it has always done: it captures the mail for the zone and forwards it. What changes is the destination. Flowmails generates a routing address for the domain and points the zone’s catch-all at it, so you never copy a forwarding address anywhere and never edit a record by hand.

From that point on the allow-list is ours, not the provider’s: a route table per domain decides which local parts are delivered and which are rejected. It is enforced on our side rather than as a literal rule in the provider, because a literal rule runs before the catch-all and would quietly override the whole list. How route tables work has the details.

One caveat, stated out loud in the product as well: the allow-list applies with a short propagation delay, so mail sent to a local part you have just added can bounce for up to a minute. Nothing is lost — it is a delay, not a drop — and the same is true of the provider’s own routing changes.

Sending: the channel is chosen per domain

The recording picks the second path at 0:25. Resend is connected by pasting one API key, once; after that the sending calls go to Resend with your key. Resend then verifies the domain over DNS, which is the provider checking a set of records — that part takes a few minutes and the recording compresses it into a beat.

The other path is the zone you already connected: Cloudflare Email Sending, with a very small sending helper placed in your own Cloudflare account so the mail leaves from your domain, from your account, with no second service to pay for. Either way the choice belongs to the domain, not to the account — one account can send from one domain through one channel and from another through the other. The first cut of this recording follows the Cloudflare path; the final cut follows Resend, because that is the path where the provider is a separate account you sign into.

The first cut, kept for the record

The first version of this walkthrough was thirteen seconds shorter, and it was wrong about the one step that matters most. It showed the forwarding-address verification completing inside the wizard — a Verify button in our own interface — and the product does not do that. On the Cloudflare path the verification link comes from the provider and has to be clicked by the person who owns the domain.

So the final cut was re-shot with the provider’s own page in the picture, and this one is published next to it rather than quietly dropped: a walkthrough that hides the hand-off is a walkthrough that teaches a step the reader will not get. If you are following the steps, follow the final cut.

The first cut. Same opening, same mailbox at the end — but the verification is shown completing inside the wizard, and the sending path is Cloudflare’s rather than Resend’s.
  1. 0:00 Setup — Start here — connect a domain.
  2. 0:03 1 · Connect — Sign in with your DNS provider. No API keys to paste.
  3. 0:08 2 · Domains — Pick the domains Flowmails should route.
  4. 0:12 3 · Receive — Inbound mail forwards into your Flowmails mailbox.
  5. 0:20 4 · Send — Outbound leaves through the provider you choose.
  6. 0:25 5 · Done — Both halves live — on your own domain.
  7. 0:26 Inbox — Mail lands in the Inbox. No forwarding by hand.
  8. 0:32 Sent — Reply from the same address — it leaves in Sent.
  9. 0:42 Inbox — And when they write back, it arrives right here.

Nine beats instead of eleven, and the gap is the whole point: the final cut spends thirteen seconds on the verification the first one skipped.

What the mailbox is afterwards

The setup is the visible half. The useful half is that the mailbox is now a surface your code can call: the same inbox, outbox and events over the REST API, the SDK, the CLI and the hosted MCP server. An inbound message arrives as an event carrying routing facts and the subject line; the body is fetched when you ask for it, not pushed at you. And a wait lets an agent block on the next message instead of polling for it — an agent signing up for things is the same mailbox, used the other way round.

What the recording does not show

  • The click, and the wait. The two moments that take real time — the verification link and the provider’s DNS check — are the two the recording spends the least time on.
  • A screen capture. The clip is drawn, not filmed. It matches the flow, not the pixels of one particular release.
  • The address your mail is forwarded to. It is generated for your domain and it is a credential: anyone who has it can inject mail into your inbox. Never paste it into a form, a ticket, or a chat message.

If you would rather read than watch, the install guide has the same path as commands, and what Flowmails is has the reasoning behind it.