How to Manage Cloudflare Email Routing Without Touching the Dashboard

Cloudflare Email Routing does one thing well: it accepts email for your domain and forwards it. What it does not give you is a way to manage that traffic — no rule editor with filters, no searchable history, no per-rule statistics. Every change means a trip to the dashboard.

The three things Email Routing is missing

• Rules with conditions — the dashboard supports exact addresses and catch-all, but not sender blacklists, subject regexes, or size caps.
• Archived copies — forwarded mail leaves no trace unless you store it yourself.
• Analytics you can act on — how many mails were blocked, bounced, or dropped, per rule and per domain.

How a management layer works

The pattern is simple: keep one catch-all rule pointing at a Worker, and do all the real routing inside the Worker. Rules live in a database (D1), so they can be edited from a panel instead of the dashboard — and every decision the Worker makes can be logged and counted.

1. Email Routing delivers everything to your Worker.
2. The Worker parses MIME, matches rules (exact → catch-all, first match wins).
3. It applies filters: blacklist, subject regex, size limit, attachment condition.
4. Forwarded mail is stored (HTML + raw MIME + attachments) and counted.

Managing Cloudflare email routing in one place

That layer is what InboxFly implements: a panel whose rule page mirrors Cloudflare’s own design, plus search, batch actions, per-rule stats, and a 30-day archive by default. You keep the one catch-all rule in Cloudflare; everything else is managed in the panel.

FAQ

Can I use Cloudflare native rules and a panel at the same time? Avoid it on the same domain — native rules take priority over catch-all and will bypass the panel. Import existing rules instead.

Do I still need the Cloudflare dashboard? Only for the initial Email Routing enablement and destination verification.