And yeah - as Leo said, CF doesn't send emails. Email Routing is receive only which is why it needs
And yeah - as Leo said, CF doesn't send emails. Email Routing is receive only which is why it needs to be your highest priority MX record
JThanks guys!
SIf you see X-MC-Relay: Bad in the headers of a message delivered through MailChannels, it means the message has been grouped with somewhat suspicious traffic. You won't necessarily get worse deliverability as a result and I would encourage you to just be patient. Over time, you will gain a good reputation within our platform and your mail will be promoted to a "Good" pool if your behaviour is flawless.
SYou may see other IP pools identified; if you see "Junk" then there is really a problem with your mail 
SFor email routing, if your domain's email is generally handled by Gmail, you can set up a subdomain for your Cloudflare email routing traffic - something like routed.example.com - and configure Cloudflare MX'es for that subdomain.
IYeah absolutely, but you'd still need to send to that subdomain - you can't route to both on the apex domain
SThanks for clarifying, Leo. I wasn't aware of that limitation.
FIn Cloudflare Routing I only managed to configure to receive emails, is it possible to send emails using cloudflare in between?
HYou can send to already-verified email addresses, but for arbitrary emails, you can use MailChannels to send emails from Workers.
FVerified email addresses refers to the SPF configured to approve some mail hosting (that sends emails)? With Cloudflare Workers I am interested in sending emails but are there any docs?
HNo, Verified Emails are the ones that have clicked the verification link they received
HSo any email approved for Email Routing/Forwarding
FOk yes true, Cloudflare sends verification email, thanks
FAnother question, is MailChannels paid?
HMailChannels does have a paid product, but you aren’t required to pay to send emails
FThank you very much for your knowledge, one more question I found that Cloudflare has a partnership with MailChannels, that is, can I send emails for free via Workers? 
HYes, that is true
SWe may introduce features that requirement a paid plan in future, but basic email sending will remain free. The major advantage of using a paid plan is you gain the ability to add a sender-id header, allowing you to specify which of your "end users" is responsible for each message. For people building apps that allow, say, their users to send messages to contacts in a SaaS platform, being able to specify a "sender-id" is helpful because it lets us block those individual senders rather than your entire CF-Worker.
SWe will do our best to be transparent about any plans to charge for functionality that we introduce to the API in future.
UI think I'd rather take my chances of being blocked rather than paying a minimum of $80/mo for me and my 0 users 
SYes for sure if you don’t have user-generated content, there is no need to have multiple sender-id’s.
HWould this also be able to be accomplished by rate-limiting MC API calls from the Worker-side?
SNot necessarily. If you send user generated content at significant scale, you will definitely want the fine grained abuse handling of sender-id’s. It also allows us to send you web hooks when we detect badly behaved senders, which you can then easily block. This is how we service tens of millions of WordPress sites across hundreds of hosting providers.
HWould this be oriented more toward generic sending? Since with Transactional(at least if I understand what they are correctly) Emails, then it shouldn’t be too difficult to manually rate limit it? I.e. sending magic links, there isn’t much you can abuse there if you can only send once every five minutes(plus maybe a blacklist for certain emails that do get spammed).
SWe automatically adapt to your Worker as you send. Generally speaking, if you are sending only a few messages per hour, you won’t trigger any adaptive rate limits at all. If you want to blast to a huge list, then keeping your initial sending rate under about 1,000 per hour will ensure we don’t slow you down. As a general rule, if you get a rate limiting error response from our API, just pause for a bit and then keep going, backing off until your mail is accepted again.
Dyou can use a subdomain for email routing
Dif you want to send mail to CF email routing from your main domain (on Google Workspace) for specific inboxes, go here: https://admin.google.com/u/1/ac/apps/gmail/routing
https://admin.google.com/u/1/ac/apps/gmail/hosts <- add Cloudflare as a host here.
https://admin.google.com/u/1/ac/apps/gmail/hosts <- add Cloudflare as a host here.
JOh wow, this is awesome, thanks. I just ended up using the mail channels free offering but may have to switch to this approach
Dthis is for inbound emails, not outgoing 
Dafaik mailchannels does not have a free offering for inbound mail
DYou can also do the same thing but with SendGrid Inbound Parse (100% free too) to send a webhook to your CF Worker. You should protect your POST endpoint with basic auth, as SendGrid does not sign these webhook payloads. I would also recommend using random path to reduce the number of Worker requests you pay for (e.g. bind your POST endpoint to
That said, Cloudflare Email Routing to a Worker seems to be working great for us. Anecdotally I've heard from others that SendGrid can be more reliable, but I have yet to personally see that. For really important emails, you could have Google Workspace forward to both SendGrid Inbound Parse and Cloudflare Email Routing, and then do deduplication in your Worker.
https://jeff.invalid/sg/random_string_hereThat said, Cloudflare Email Routing to a Worker seems to be working great for us. Anecdotally I've heard from others that SendGrid can be more reliable, but I have yet to personally see that. For really important emails, you could have Google Workspace forward to both SendGrid Inbound Parse and Cloudflare Email Routing, and then do deduplication in your Worker.
DSendGrid Inbound Parse also does not allow you to use
You need access to
Cloudflare Email Routing works fine for
abusepostmasterunsubscribeYou need access to
postmaster@jeff.exampleCloudflare Email Routing works fine for
abusepostmasterunsubscribeLast thing, be mindful that you are rate limited to 60 emails per minute if you use your root domain (which is on Google Workspace).
https://support.google.com/a/answer/1366776?hl=en
https://support.google.com/a/answer/1366776?hl=en
To keep Gmail efficient and accounts safe, Google limits the number of messages you can receive. If your account receives many automated messages, it's more likely your account will reach the message
SWe used to offer free inbound filtering to Cloudflare customers via the app marketplace, but uptake wasn't great. We removed it.
Disn't the app marketplace dead too?
SWe sort of thought it might be dying soon too...
DI think inbound parsing is oddly not as popular as many of us would initially believe. Like SendGrid not bothering to add signatures makes me wonder how many people really use it. 
Uim curious how apps v2 will play out whenever they eventually get that out...
Uno theyve said in the past that they are working on a new apps system that will be similar to cf apps
DI like that.
UI mean it basically would be yes but you add it to other peoples accounts instead of your own
Uthats not workers for platforms
UIt would be cloudflare apps but revived and using CF workers instead of whatever system it uses rn
UThough who knows if thats even being actively worked on or its just an idea for at some point in the future maybe they will do it lol
KAnyone know the maximum number of matchers for a routing rule? (see https://developers.cloudflare.com/api/operations/email-routing-routing-rules-update-routing-rule)
I've been trying to get the limit of 200 rules raised for my domain but two weeks later and I'm not getting a response after several attempts. My fallback solution could be to create a single rule with >200 matchers and just maintain it via the API, but I'd rather not do the work and only later find out that there's another hidden limit.
I've been trying to get the limit of 200 rules raised for my domain but two weeks later and I'm not getting a response after several attempts. My fallback solution could be to create a single rule with >200 matchers and just maintain it via the API, but I'd rather not do the work and only later find out that there's another hidden limit.
Interact with Cloudflare's products and services via the Cloudflare API
USounds like you should be using workers to route it where you want instead which allow an infinite number of conditions for how you want to route mail since you can code anything you want with that path
KIf the worker would allow me to dynamically update the list via an API, I may do that. After dropping Google Workspace for my email routing due to the lack of an API (seriously, wtf is up with that?) I found CF's API to be great and I figured I could do just about anything with it.
Uyou wouldnt update with an API the worker would be the routing rules so you can lookup rules into KV or just have static rules that you update a worker when you need or whatever
SIt seems e-mail workers are pretty popular and growing quickly. I paid for a database that has been scanning MX records for many years (w3techs.com). The market share of email hosting owned by Cloudflare Email Routing is now at 0.3%, up from 0% obviously not so long ago. One third of a percent of all active website domains is a large figure.
S
