Non-catchall user+ routing
If I setup a worker route for user@email.domain I would expect/hope that the + separator trick used by so many other providers would cause user+someservice@email.domain to route to the worker as well but that doesn't appear to be the case. I get a generic Address not found bounce message instead. What is the intent here? Do I need to setup a catchall route instead to deal with these?
4 Replies
yup this is documented
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.You can use a catchall route or a catchall route to a worker to manually parse and fwd
Man I thought I searched the documentation pretty well. Can you point me to what I missed there?
but thanks for clarifying
it's hidden a bit under the postmaster -> "Known limitations" section https://developers.cloudflare.com/email-routing/postmaster/#signs-such--and--are-treated-as-normal-characters-for-custom-addresses
ooh yeah I hadn't even looked at this section but it looks like lots of great info here