I was invited to try out the email routing and it has been working fine so far.
Me and my parents are running a small business where we’d like to receive all emails in each of our own personal email addresses.
Reason for the catch-all is because sometimes our clients misspelled our email addresses particularly our names, and for all of us to receive catch-all emails is because sometimes one of us might miss the email.
Would like ability to forward emails to multiple ids. This would remove the need for me to have postfix on my server which is only used to forward mails.
Use case? Netflix account shared by four users. Netflix mails sent to account mail id are forwarded to all four users. Since authorization is required for forwarded addresses, this should be safe to implement?
I absolutely need to be able to forward most emails to more than one destination address, and 5 would be adequate, but why limit it to 5? All destination addresses must be authenticated, so spam should not be an issue. Anti-spam authentication could even be enhanced by something like limiting further destination addresses when there are more than 5 pending an authentication response.
I just switched my name servers on one of my domains to try out Cloudflare. I’m really liking it, except I really need 2 email aliases at my domain to forward to 2 email addresses instead of just one.
I’d like to stay and transfer my domains to Cloudflare as well, but I really need this feature.
I really love and appreciate the Email Routing feature!
I thought it would be very useful if we cloud route emails to multiple addresses, for instance, [email protected] → [email protected] and [email protected].
I would be very grateful if Cloudflare added this kind of feature!
I’m currently with ImprovMX until I can migrate to CF.
ImprovMX has had its fair share of outages and unlogged lost emails over the past year. On the other hand, I do love some of their features, putting it here in case the Cloudflare Email routing team checks this thread:
multiple recipients for a forwarded email
regex match: enable regular expressions to catch a leftside of the email address
regex capture: enable to match a pattern and use it in the destination email. For example a rule (.*)@smallcompany.com → [email protected]
transparency may be a bit too technical for the current CF MX menu, yet it’s useful to be able to browse the logs of the routed emails in the past N days and check the status, including the SpamAssassin score and rules it hit.
I’ve not tried the email workers but just noticed them now. Would anyone know if the above is already possible with the current features of CF?