Wildcard/RegEx matching with Cloudflare Email routing

I also need this. Just migrated from Google Domains and it has this feature.

Would like to see this as a fallback/catch-all configuration.

  • abc @example.com → abc-mails @gmail.com
  • def @example.com → def-mails @gmail.com
  • *@example.com → everything-else @gmail.com
1 Like

The wildcard feature I requested already exists in a basic form. It is called a “catch-all”.

3 Likes

I am getting closer to having to make a decision and want that decision to be Cloudflare if possible, but I NEED this feature in order to not host email elsewhere. Is there a consulting rate that can be paid to finish a feature like this? I would be happy to discuss rates and time estimates for this work.

Thank you!

2 Likes

Thanks for sharing this @paramaggarwal. I think I missed this functionality because it’s not in the “Getting Started” wizard, but if you skip the wizard, you can go directly to this tab and set up a catch-all.

replicating the google workspace (gmail) feature of:
user+@domain.com > [email protected]

I can’t even begin to count the number of user+ email addresses in use between just the 3 of us that use our domain. That is the primary feature we don’t migrate off of google workspace to something more private.

Currently Cloudflare verifies destination address to avoid spamming for individual email addresses.

To verify the whole domain, it could potentially just use DNS records with TXT or CNAME (preferable to avoid bloating the root zone).

+1 to have *@domain1.com go to [email protected]

1 Like

it been almost 4 years and no update on this :slightly_frowning_face:

+1 want update for this topic