Email Routing

Enable Cloudflare Email Routing on your zone and understand what vuzon writes there — and what it deliberately leaves alone.

Enable it on your zone

In the Cloudflare dashboard, open your zone → Email → Email Routing and enable it. Cloudflare guides you through creating the MX and SPF records for the domain. vuzon needs Email Routing to be already enabled on the zone — it manages the rules, not the DNS onboarding.

Zone and account autodetection

On startup, vuzon resolves your zone and account from DOMAIN (via the Zone: Read permission), so there are usually only two variables to set. If autodetection fails — or two zones share the same name — add both CF_ZONE_ID and CF_ACCOUNT_ID to your .env; the startup error tells you when. See Environment variables.

What vuzon writes

vuzon only writes actions it fully understands: forward to one verified address, or discard. Everything else it shows without touching:

• A rule pointing at an Email Worker shows its script name.
• A fan-out rule (multiple destinations) shows all its addresses.
• Editing one of those replaces its action, so the panel asks first — routing you configured outside the panel is never overwritten by a guess.

The catch-all

The catch-all handles mail sent to any address without an alias. From the panel you can pause it or change what it does — forward the leftovers to a verified address, or discard them.