#Cloudflare Email Routing: How to set up `+topic` custom addresses?

6 messages · Page 1 of 1 (latest)

west vector
#

I want to set up a custom address with + symbol in it, e.g. someone+sometopic@my.domain.
Firstly, I tried setting up this address directly by creating a custom email address in the dashboard but was blocked by the validation logic indicating that allowed characters in the address are 0-9 a-z _ . (as shown in the screenshot).
Then I tried to create a custom address without the topic (i.e. someone@my.domain) and expected Cloudflare Email Routing would follow the same rule for the address with the topic (i.e. someone+sometopic@my.domain), as Gmail does (https://support.google.com/a/users/answer/9282734?hl=en#email-address-variation); but testing showed someone+sometopic@my.domain just matches the catch-all rule, so no luck.
So is there a way to use custom email addresses like someone+sometopic@my.domain with Cloudflare Email Routing? Thanks in advance.

violet needle
# west vector I want to set up a custom address with `+` symbol in it, e.g. `someone+sometopic...

👋
https://developers.cloudflare.com/email-routing/postmaster/#signs-such--and--are-treated-as-normal-characters-for-custom-addresses

Signs such “+” and “.” are treated as normal characters for custom addresses

Email Routing does not have advanced routing options. Characters such as + or ., 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.
So maybe one day. Otherwise right now you could use the catch-all, or create a CF Email Worker that handles it/has forwarding logic

Cloudflare Docs

Reference page with postmaster information for professionals, as well as a known limitations section.

west vector
violet needle
#

Where that faq entry is, is more under the post master/how they deal with stuff internally.
The UI is seperate, not sure why they have that validation logic there but it's been that way forever

#

as far as I am aware it is intentional that you can't from the ui though, they commented on it way back:
#email-routing message