Hello, I have a question regarding email routing. Let me describe the situation: Our customers use our SAAS tool to send emails to their clients, for instance, using demo@ourdomain.com. We've set a reply-to header, but unfortunately, it's sometimes ignored by email clients. In cases where one of their clients sends an email to demo@ourdomain.com, we want to forward it to our customer's email address instead of it arriving in our inbox. Currently, we are using Google Workspace for our inboxes and are manually adding forwarding rules each time. We were hoping there could be a way to automate this so that when an email arrives at demo@ourdomain.com, it can be correctly forwarded to info@democompany.com. Is this possible with Cloudflare's email workers? Or through normal routing? It involves hundreds of companies to which the emails need to be forwarded. We are open for any suggestions, we would like to keep using the google workspace if possible. If not possible thats also ok.

Email Workers require each destination to be verified (which is done via a verf email and them clicking a link) They would also have to take over your mailservers for the root domain in that case, or iirc Workspace has some forwarding features which may work but ymmv, I suspect you may be blocked by the first requirement there regardless

So there is no way of forwarding the mails without the verification mails?

not using CF's built in forward stuff

Hmmm. And our own mailboxes that are currently in the google workspace. Everyone in the company has his/her own E-mail and we were wondering how this could work together. Would we need to use the workspace on a subdomain. Or can the workers work on a subdomain and the workspace on the root domain.

If you skip the getting started setup you can just setup email routing on a subdomain yea

> Our customers use our SAAS tool to send emails to their clients, for instance, using demo@ourdomain.com. I would recommend you to look in to this part ASAP. First of all, this severe operational failure, as I would call it, is the root cause to your problem. Additionally, it is also a very weak security policy of your company, e.g. the domain

ourdomain.com

in your example, that any customer can just send out using your company's domain name. 1. What if I were sending out junk through your SaaS platform? Your domain would obviously appear as the culprit, and be the one taking a dive in it's reputation, causing consequences for all of your customers at once. 2. What if I were sending out illegal stuff, or otherwise stuff that is (generally) considered nasty, through your SaaS platform? It would literally appear to be originating from your domain, ... so who would the public see, as the one to blame in that case?

You indeed make a good point, we hadn't thought about it that way before. However, we often see major parties like Intercom also offering email services through their own domain. Intercom does use @intercom-mail.com instead of the main domain, is this a better solution? We've discussed it and are considering doing it your way for existing customers and for new customers in trial periods to retain the standard mail function but in a limited capacity.

Corrected: > Additionally, it is also a very security policy of your company, to: > Additionally, it is also a very weak security policy of your company,