Email Routing is a forwarder. It takes mail sent to you@yourdomain.com and drops it into an inbox you already have. It does not give you a way to answer as you@yourdomain.com. That is not a bug you can fix in the dashboard; it is what the product is. Pick the symptom below that matches yours.
What Email Routing does, in one paragraph
Cloudflare's documentation describes Email Routing as a way to handle incoming email: it routes mail for addresses on your domain to a Worker or to a destination address you have verified (developers.cloudflare.com/email-routing, checked 6 October 2026). It is free on every Cloudflare plan. When you enable it, Cloudflare adds its own MX records and an SPF record to your zone, so from that moment Cloudflare receives your domain's mail and forwards it on.
The limits page (developers.cloudflare.com/email-routing/limits, same date) lists 200 routing rules per domain, 200 verified destination addresses per account and a 25 MiB cap on incoming messages. Nothing on that page describes an outbound mailbox, because there is none. Every symptom below comes from that one fact.
You replied, and it went out from your Gmail address
This is the most common surprise. A customer writes to hello@yourdomain.com, Routing forwards it to your Gmail, you hit reply, and the customer gets an answer from yourname@gmail.com. The thread now has two addresses in it and your domain looks like a decoy.
The free fix is Gmail's "Send mail as" feature. It lets Gmail send on behalf of another address, but Gmail needs an SMTP server to hand the message to, and Cloudflare does not provide one for this. You need an SMTP login somewhere: a mailbox on your domain at any host, or a sending service that allows personal use. With that in hand, the steps on Google's help page (support.google.com/mail/answer/22370, checked 6 October 2026) are:
- Open the Accounts tab. In Gmail on a computer, click Settings, then See all settings, then the Accounts and Import tab.
- Add the address. Under Send mail as, click Add another email address. Enter your name and hello@yourdomain.com, then Next Step.
- Enter the SMTP server. Type the SMTP server, username and password of the mailbox or service that will carry the mail. Google's page says to use SSL on port 465 or TLS on port 587, and to pick port 25 with the unsecured option only if your provider cannot do better.
- Verify. Gmail sends a confirmation to the new address. Routing forwards it into your inbox; click the link, and the address appears in the From menu when you compose.
Two things to know before you rely on it. Replies you send this way still live in Gmail, so your sent mail for the domain is scattered across personal accounts. And the SMTP server you borrow is the one that signs the message for SPF and DKIM, so whichever host you use has to be allowed to send for your domain in DNS, or receivers will file the reply as spam.
You need support@ to answer, and more than one person reads it
Routing can forward support@ into a teammate's inbox. It cannot give a team one shared place to answer from, and the Gmail trick above is per person, per address. The moment a second teammate needs to reply as support@, you are managing SMTP passwords in several personal accounts.
Cloudflare's own sending feature does not close this gap either. Email Sending, in beta on 6 October 2026, is available on the Workers Paid plan and is designed for code. You call it from a Worker binding, the REST API or authenticated SMTP. Sending to the destination addresses you verified in your account is free on all plans (developers.cloudflare.com/email-routing/send-email). It is a good tool for an app that sends receipts. It is not an inbox a person opens in the morning.
For a shared address that people answer, you want a real mailbox on the domain. Any email host can provide one, and you do not have to leave Cloudflare DNS to get it. The host's MX records replace Cloudflare's, the inbox lives at the host, and support@ becomes an account several people can sign in to from Apple Mail, Outlook or webmail. On Faivelo that mailbox is included in a $6 a month flat price however many addresses you add, and the one-click Cloudflare connect writes the records into your zone for you.
You want a catch-all on more than one domain, and more than forwarding
Routing's catch-all is handy: anything@yourdomain.com lands in one inbox, which is useful for signing up to services with a unique address each. The rule is per domain and it still only forwards, so every reply has the same problem as above, and each domain's catch-all needs its own rule and destination.
If you have outgrown forwarding, the catch-all moves with you. A hosted mailbox can take a catch-all too, delivering into a mailbox you pick rather than bouncing out to a third address, and from there you reply as any address on the domain. The trade-offs of a catch-all are a story of their own, and we cover them separately.
The trap when you switch: the orange cloud
Cloudflare's DNS reference notes that MX and TXT records are always DNS-only, and that records used for email should stay DNS-only (developers.cloudflare.com/dns/manage-dns-records/reference/proxied-dns-records, checked 6 October 2026). The MX record itself is never the problem. The problem is the hostname the MX points at: if that A or CNAME record has the orange cloud on, mail servers connect to Cloudflare's proxy on port 25 and get nothing. Any record your email host asks you to add that names a mail server must have the grey cloud.
The second trap is Email Routing itself. While it is enabled, it owns your MX records, and a new host's records will sit beside Cloudflare's or be refused. Turn Routing off under Email first, then add the host's records. The one-click connect handles both: it writes every record DNS-only and tells you if Routing is still switched on.
Routing answers the question "where does my mail go". It was never built to answer "who am I when I write back".
FAQs
Can Cloudflare Email Routing send email at all?
Not from an inbox. It forwards incoming mail to a destination you verify. Cloudflare's separate Email Sending feature, in beta on the Workers Paid plan, sends from code, and sending to your own verified addresses is free, but neither gives you a mailbox to reply from.
Is the Gmail "Send mail as" method free?
Gmail does not charge for it, but it needs an SMTP server to deliver through. That server comes from a mailbox or sending service you already pay for, or one that offers it free, and that server must be allowed to send for your domain in your SPF record.
Do I have to leave Cloudflare DNS to get a real mailbox?
No. Keep the domain and DNS at Cloudflare, switch Email Routing off, and add your email host's MX and authentication records with the grey cloud. Faivelo does this through a one-click connect to your Cloudflare account.
Will my existing forwarding rules keep working after I add a mailbox?
Routing rules stop once Routing is disabled, because the MX records change. A hosted mailbox replaces them with aliases and a catch-all on the host's side, which can forward too if you still want copies elsewhere.
Why did replies sent with "Send mail as" land in spam?
Usually because the SMTP server you entered is not listed in your domain's SPF record, or does not sign with DKIM for your domain. Check the domain at /email-checkup and add the server's include to SPF.
Give hello@ a real inbox
Keep Cloudflare for DNS. Connect your account once and Faivelo writes the records, creates the mailboxes, and lets everyone reply as the address they were written to. Fourteen days free, no card.