Roy
Roy
PostsComments
CDCloudflare Developers
Created by Roy on 1/8/2024 in #general-help
Email routing many clients to customers
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 [email protected]. 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 [email protected], 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 [email protected], it can be correctly forwarded to [email protected]. 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.
18 replies
CDCloudflare Developers
Created by Roy on 12/11/2023 in #general-help
Simulate Zone field in load balancer monitor
Hello, I am setting up the authentication origin pulls and found online that i need to fill in the "Simulator Zone" field in my loadbalancer for it to send the SSL certificate. https://community.cloudflare.com/t/can-you-use-load-balancer-monitoring-with-authenticated-origin-pulls/242312/2 Am i support to put the ZoneID that i find at the overview in this field? Or do i need to put something else in there. Filling in the ZoneID i copied from the overview of this domain i get the error: 
ProbeZone: "{zoneid}" is not a zone associated with this account: validation failed (Code: 1002)
ProbeZone: "{zoneid}" is not a zone associated with this account: validation failed (Code: 1002)
9 replies
CDCloudflare Developers
Created by Roy on 9/15/2023 in #workers-help
E-mail routing with worker only on subdomain
Hello, After searching for a bit i found that to make this possible i needed to create a different zone for the subdomain following the documentation i couldn't figure it out so i decided to try something else. We currently have our mailing in gmail and would like to keep it that way, so for gmail we are using the root of the domain: [email protected]. We have a SAAS tool that currently send mails using {company}@example.com. Since it needs to be on a subdomain to do the seperate routing I added the MX and TXT records manually in cloudflare's DNS on mailing.example.com. It seems that it's now beeing captured by the routing and send to the worker but when trying to send an E-mail to the subdomain [email protected] i get the following message back: 521 5.3.0 Upstream error, please check https://developers.cloudflare.com/email-routing/postmaster for possible reasons why. lqY8HOe6NBOb Looking at the URL given by the error I can't really figure out what is happening. In the router i created a very short piece of code that simple allows the "to" to go only to 1 domain as a test. 
export default {
  async email(message, env, ctx) {
    if (message.headers.get("to") == "[email protected]") {
      await message.forward("[email protected]");
    } else {
      message.setReject("Unknown address");
    }
  }
}
export default {
  async email(message, env, ctx) {
    if (message.headers.get("to") == "[email protected]") {
      await message.forward("[email protected]");
    } else {
      message.setReject("Unknown address");
    }
  }
}
What am i doing wrong?
5 replies