Sending email from a domain with a strict DMARC setting (and both DKIM and SPF configured; email hosted by iCloud) to a domain configured with Cloudflare Email Routing with the forwarding address as a Gmail account seems to result in the forwarded email landing in spam.
Sending from another Gmail account lands the forwarded mail in the Gmail inbox.
While I could relax the DMARC controls on my custom domain, I’m worried that some mail sent by others and forwarded through Cloudflare Email Routing is going to end up in spam if coming from domains with strict DMARC settings. Is there a recommended setup in Gmail and/or on the domain with Email Routing enabled to overcome Gmail’s treatment of these messages as spam?
For me also emails from GMail to email routed email address on GMail also ends up in spam.
And from my work email I see in the headers: Authentication-Results: mx.cloudflare.net; spf=pass; dkim=neutral; dmarc=none;
And it also end up in spam.
This is all a bit technical for me, but since I signed up for using Cloudflare email routing I’m getting these kinds of error reports, and don’t know what I can do about them? (Except perhaps not use Cloudflare?)
Since the domains are different, the headers are “unaligned” and dmarc fails.
Why is the RFC5321.MailFrom changed? For SPF checks. SPF will lookup the domain based on the RFC5321.MailFrom, and since the sending IP is now from Cloudflare (due to forwarding) the RFC5321.MailFrom is changed to a DNS record controlled by your domain in Cloudflare.
Now, the question is - what to do about the send to spam? Again I’m no expert (far from it).
Cloudflare should not modify the RFC5321.MailFrom header and just allow SPF to fail.
I’ve seen other forwarding platforms add X-Forwarded-To and X-Forwarded-For headers. Maybe that helps to identify forwarded mail?
I encountered this as well, but I think there is an easy fix would ask others to confirm.
Configure CF email forwarding catch-all to target address.
Send to catch-all from an account other than the target.
Mark the received email as “not spam”.
This not only made all subsequent emails to the catch-all appear properly in the target inbox, it fixed all other CF catch-alls (at least for me). So just by correcting one spam from one CF catch-all fixed them all.
Please confirm. Otherwise a test email from every CF catch-all must be marked as not spam (still not a bad solution - at least it will work for sure, but may not be necessary).