The MX constraint

What that means in practice

support@yourdomain.com is only available to you if that domain carries no other mail. This is the decision provisioning asks you to make, and pithy support is where you make it — running a support inbox and receiving mail generally both start here.

If your apex is already receiving mail — a mailbox provider, a marketing tool, anything with an MX record — claiming it for a support inbox takes that mail with it.

The answer everyone else uses

A subdomain:

support@help.yourdomain.com

It works identically and is slightly less polished. That is the whole trade.

Put the address on a help. subdomain, turn Email Routing on for that subdomain, and your apex mail is untouched. A subdomain is usually not a zone of its own: in the Cloudflare dashboard its Email Routing is set up under the parent zone, at Email > Email Routing > Settings > Subdomains.

Why the provisioning command will not turn it on

pithy support provision routes your address by itself, and never enables Email Routing. For each environment it finds the zone that holds the address’s domain, checks that Email Routing is already on for that domain, and only then creates the rule:

pithy support provision

Turning Email Routing on for the wrong domain would move your real mail, and that is not a mistake a provisioning command gets to make on your behalf. So the switch stays yours, in the Cloudflare dashboard, and provision routes only a domain you have already turned on.

Until you do, everything else still provisions — the bucket, the classification Worker, the migrations — and the run names the domain it refused and where to turn it on. The first run after you do routes it.

The same care on the way out

pithy support deprovision --env <environment> removes that environment’s routing rule first, so mail stops arriving before the Workers that would have handled it go away.

It removes only a rule that sends an address the environment claims to the environment’s own Worker. A rule sending that address anywhere else is left alone, and so is every other environment’s.

--routing-zone is only for the one project-global rule the override flags (--routing-zone, --inbound-address, --app-worker) create, and only with the last environment.

The rule name carries the project

<project>-<env>-support-inbound, one per environment, deliberately distinct from the email capability’s bounce rule. The override flags make one project-global rule instead, <project>-global-support-inbound.

A rule is found by the address it matches, not only by its name. One already sending the address to the Worker is left alone, whatever it is called. The sole enabled rule sending it elsewhere is updated to the Worker, keeping its name, and several enabled rules claiming it are refused by name rather than guessed between.

An address two environments both claim is refused for both, because one exact-address rule delivers to one Worker. Give each environment its own address.

Until you configure an address, the inbox is inert

pithy add support wires the capability and runs the migrations. Until inboundAddresses is set, it ignores every message and says so once in the log — rather than quietly storing mail from an address nobody chose.

ESC