Below, you will find information regarding the current limitations for Email Routing.
Email Workers size limits
When you process emails with Email Workers and you are on you might encounter an allocation error. This may happen due to the size of the emails you are processing and / or the complexity of your Email Worker. Refer to for more information.
Email address internationalization (EAI)
This means that you can have email addresses with an internationalized domain, but not an internationalized local-part (the first part of your email address, before the
@ symbol). Refer to the following examples:
Non-delivery reports (NDRs)
Email Routing does not forward non-delivery reports to the original sender. This means the sender will not receive a notification indicating that the email did not reach the intended destination.
Subdomains are only supported for Enterprise customers
Subdomains cannot use Email Routing to forward emails, unless they are part of an Enterprise account.
Signs such “
+” and “
.” are treated as normal characters for custom addresses
Email Routing does not have advanced routing options. Characters such as
., which perform special actions in email providers like Gmail and Outlook, are currently treated as normal characters on custom addresses. More flexible routing options are in our roadmap.
Restrictive DMARC policies can make forwarded emails fail
Sending or replying to an email from your Cloudflare domain
Email Routing does not support sending or replying from your Cloudflare domain. When you reply to emails forwarded by Email Routing, the reply will be sent from your destination address (like
[email protected]), not your custom address (like