Curious if the scenario of using cf email routing _only_ on a subdomain is meant to be supported? i

Curious if the scenario of using cf email routing only on a subdomain is meant to be supported? ie keep your original mx for the root zone, and use cf only for the subdomain. I would have thought this would be one of the main use cases for subdomains. It works in some ways (incoming email is received), but two major blockers I stumbled into:

1.

.reply(

.reply(

.reply(

.reply( does not work, you get a

mail from is not from the correct domain

mail from is not from the correct domain

mail from is not from the correct domain

mail from is not from the correct domain, even though it is
2. sending emails via the worker binding is blocked by gmail servers with

This mail has been blocked because the sender is unauthenticated

This mail has been blocked because the sender is unauthenticated

This mail has been blocked because the sender is unauthenticated

This mail has been blocked because the sender is unauthenticated, the error includes an SPF lookup of the root zone (?), not the subdomain. For more lenient gmail domains, like business domains, the email goes through, but received with a big red warning question mark in the contact photo

Original message was deleted

dave•2/4/24, 4:18 PM

We’ve been using it for months. You can email me using test@leo.testing.email.ai.moda and it’ll work.

Original message was deleted

dave•2/4/24, 5:07 PM

I added these manually and it works.

Original message was deleted

dave•2/4/24, 5:07 PM

try sending me an email to test@leo.testing.email.ai.modatest@leo.testing.email.ai.moda and I'll provde it

dave•2/4/24, 5:07 PM

I have no records at all for testing.email.ai.modatesting.email.ai.moda or leo.testing.email.ai.modaleo.testing.email.ai.moda.

Ddave try sending me an email to `test@leo.testing.email.ai.moda` and I'll provde it �...

DarkDeviL•2/4/24, 5:08 PM

One thing is "appearing to work fine", something else is "supported"

DDarkDeviL One thing is "appearing to work fine", something else is "supported" 😉

Hello, I’m Allie!•2/4/24, 5:09 PM

Isn't the docs thing just about the fact that you can't create a rule that only covers a subdomain?

Hello, I’m Allie!•2/4/24, 5:09 PM

So subdomain catch all could still be supported, just not "subdomain without root catchall"

Original message was deleted

dave•2/4/24, 5:17 PM

ahhh. Probably not the answer you're looking for, but we do the routing forwarding for the wildcard catch-all using a Worker.

Ddave ahhh. Probably not the answer you're looking for, but we do the routing forwardi...

Hello, I’m Allie!•2/4/24, 5:18 PM

HHello, I’m Allie!Isn't the docs thing just about the fact that you can't create a rule that **onl...

DarkDeviL•2/4/24, 5:18 PM

Last I heard about it was that such as e.g. the *.email*.email records, even though they might work, they were not actually supported.

DDarkDeviL Last I heard about it was that such as e.g. the `*.email` records, even though t...

dave•2/4/24, 5:19 PM

wait is me using emailemail some special allowed edge case that I guessed...?

dave•2/4/24, 5:19 PM

I thought *.anything*.anything would work.

HHello, I’m Allie!||Can we put it in a Snippet? /j||

dave•2/4/24, 5:20 PM

eh we do more complicated routing decisions that are much easier to do in a Worker.

Ddave eh we do more complicated routing decisions that are much easier to do in a Work...

Hello, I’m Allie!•2/4/24, 5:20 PM

I mean a Snippet is a Worker, it is just free

HHello, I’m Allie!I mean a Snippet **is** a Worker, it is just free

dave•2/4/24, 5:20 PM

it's a big Worker lol

Hello, I’m Allie!•2/4/24, 5:20 PM

But it doesn't support anything other than HTTP afaik

Ddave it's a big Worker lol

Hello, I’m Allie!•2/4/24, 5:20 PM

Yeah, that's what the /j was for

HHello, I’m Allie!But it doesn't support anything other than HTTP afaik

dave•2/4/24, 5:21 PM

what else would you need to support other than HTTP?

HHello, I’m Allie!Yeah, that's what the /j was for

dave•2/4/24, 5:21 PM

eh for simple things it would work I think!

Ddave what else would you need to support other than HTTP?

Hello, I’m Allie!•2/4/24, 5:22 PM

All of the Worker tasks. Like a Workers free tier that isn't bounded by number of requests, but rather size of Workers/execution time

HHello, I’m Allie!All of the Worker tasks. Like a Workers free tier that isn't bounded by number o...

dave•2/4/24, 5:23 PM

oh we're talking about snippets? (We still haven't used them, don't fully understand their limitations yet tbh.)

Ddave oh we're talking about snippets? (We still haven't used them, don't fully unders...

Hello, I’m Allie!•2/4/24, 5:23 PM

I would assume so:

dave•2/4/24, 5:23 PM

does the 5ms count when you're awaiting on a fetch?

dave•2/4/24, 5:23 PM

if not, 5ms doesn't seem that bad.

Ddave does the 5ms count when you're awaiting on a fetch?

Hello, I’m Allie!•2/4/24, 5:24 PM

Afaik it is CPU time, though the docs are a little ambiguous

dave•2/4/24, 5:24 PM

Our catch-all email Worker takes ~6.6ms on average of CPU time and it could be optimized if we felt like it.

dave•2/4/24, 5:24 PM

it does crypto in multiple places iirc

Ddave Our catch-all email Worker takes ~6.6ms on average of CPU time and it could be o...

Hello, I’m Allie!•2/4/24, 5:25 PM

But yeah, you can't actually handle any events other than a

fetch

fetch

event in a Snippet, so it wouldn't matter.

Hello, I’m Allie!•2/4/24, 5:25 PM

Or, that is to say, you can't yet

Ddave wait is me using `email` some special allowed edge case that I guessed...?

DarkDeviL•2/4/24, 5:42 PM

Actually, - my understanding of it comes from before subdomains were supported in the Dashboard, where my understanding was, ... that it was a "hacky workaround" that you shouldn't rely on, because it wasn't officially supported.

DarkDeviL•2/4/24, 5:43 PM

If the Dashboard doesn't allow you to add "

.email

.email

" as a sub-domain, I would personally still not consider it to be officially supported.

DDarkDeviL If the Dashboard doesn't allow you to add "`.email`" as a sub-domain, I would **...

dave•2/4/24, 5:44 PM

it makes sense it works to hit the default catch-all Worker

dave•2/4/24, 5:44 PM

I agree I wouldn't depend on it for setting subdomain routing rules

dave•2/4/24, 5:44 PM

but I think the catch-all case is reliable

Ddave but I think the catch-all case is reliable

DarkDeviL•2/4/24, 5:48 PM

My point is simply that I wouldn't suggest relying or depending on something that isn't officially supported, no matter how well / reliable it appears to be working.

DarkDeviL•2/4/24, 5:49 PM

And especially not if we're talking about it for mission critical things.

jordan•2/4/24, 9:17 PM

Has anyone implemented nested replies (replying to a reply) from a worker?

JJohn Spurlock Curious if the scenario of using cf email routing _only_ on a subdomain is meant...

John SpurlockOP•2/6/24, 11:09 PM

(bumping a question from over the weekend) Curious if the scenario of using cf email routing only on a subdomain is meant to be supported?

TTraffy I have added my email to gmail alias. I can also send email from gmail. So in th...

Chaika•2/7/24, 4:23 AM

Gmail. You can't send mail via Cloudflare except via Workers to your verified addresses or in reply to messages via email worker

Chaika•2/7/24, 4:23 AM

also iirc gmail like that always fails spf because the way it sends/alignment, been a while though

TTraffy How would you suggest to use cloudflare to receive and send email?

Chaika•2/7/24, 5:00 AM

Sadly, you don't. CF can't send mail like a normal email provider/solution. Sounds like you want a more traditional email setup like Fastmail, Google Workspace, ProtonMail that works with Custom Domains and can send and receive.