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

*.email records, even though they might work, they were not actually supported.email some special allowed edge case that I guessed...?*.anything would work.
fetch event in a Snippet, so it wouldn't matter..email" as a sub-domain, I would personally still not consider it to be officially supported.fetch from my Pages to bounded Mail Workers and from the Workerse to Mailchannels.Cancelled a mx include:_spf.google.com" part from your SPF.a: Cloudflare HTTP Reverse Proxies will never send on your domain's behalf.mx: Is pointing to Cloudflare's INBOUND mail servers, they do NOT send OUTBOUND and should not be listed in your SPF.include:_spf.google.com: The "trick" will always authenticate as the @gmail.com, and expose the real Gmail address. Since the SPF is done on gmail.com, you're overauthorizing by having include:_spf.google.com, which - depending on the eyes looking at it, is a security issue / risk.*.email*.anything.emailCancelleda mx include:_spf.google.commxinclude:_spf.google.cominclude:_spf.google.com@gmail.comgmail.com