Domains and subdomains are handled by DNS which is why Cloudflare can E2E proxy them. Email mailboxes are handled by an application running on a server.
Obviously if there's any recipient address trranslation in play forwarding becomes necessary.
Define 'properly'.
It's a bog-standard forwarding specifically because this is the only way to have to separate systems to operate.
Gmail doesn't know what `yourdomain.tld`[0] is yours and what if it receives anyhting to *@yourdomain.tld it should route it to [email protected].
If you don't point yourdomain.tld MX records to Cloudflare then Cloudflare would never receive anything to @yourdomain.tld, because MX doesn't point at them.
[0] the only way to for it know that is to run some Google Business or whatever it called now, where you actually ... point yourdomain.tld MX records to Gmail and it would process them... but it would not deliver them to [email protected]!
BTW it would be absolutely the same idea if instead of Cloudflare you would use Google Business (again, whatsitsname). You would setup 'Send As' in [email protected] as a usual SMTP identity which would allow you to use Gmail interface to send from [email protected], and similar you need some way to explain to Google/Gmail what all mails at *@yourdomain.tld should be forwarded to [email protected].
I understand the vagaries wrt forwarding to an acount of a different name and you're spot on there.
Support for such use cases is imminent: https://blog.cloudflare.com/announcing-route-to-workers/
That is you have your MX records pointing to `mx.example.com` in your example.com zone config, and enable the Cloudflare proxying of it (usual orange cloud in the UI).
Now, once it's proxied, Cloudflare returns the IP of their mailserver instead of yours on public lookup, just as they do when returing the IP of a proxied webserver.
So this Cloudflare MX server gets your mail, and then as it knows your 'real' MX server it connects to that server and delivers it to you, maybe adding some header or other on the way.
I don't like the fact they use bog-standard forwarding as it necessitates messing with your SPF records, getting crazy forwarding headers and having to navigate ARC etc.
There just seems to be a cleverer way to do this than just do what everyone else does, and they're generally ahead of the curve technically. Must be something I'm missing.