Hey, I am new to all of this. I didn’t know emails would be rejected by cloudfare. I thought it was just routing and everything (good and bad) would be sent through to my nominated address(es).
Everything has been running smoothly for a few months but suddenly, many emails are failing to be forwarded due to being suspected spam or DMARC policies. I can’t figure out how to allowlist domains that I know are genuine.
The picture is just a couple that happened in the last 24 hours but has happened numerous times with different senders to different custom addresses with the same errors since I first discovered a problem about a week ago (which seems to have already started about a week before that).
Thankfully, most are just non-essential update type emails but some are time-sensitive alerts etc.
What you’re showing isn’t actually Cloudflare, but the final destination, which you’re attempting to route the message to, that is rejecting the message.
I did a long explanation about that, for example over here:
Do you see SPF=none, DMARC=none, DKIM=none on just a few messages every now and then, or does it actually happen to all messages you receive?
Is there more than just these two, ebay.com and windscribe.com, where they all apparently equal none?
Strange, I wonder if there is some sort of localized problem regarding that, considering other threads here.
I haven’t yet been able to reproduce that myself though.
It wouldn’t be completely impossible that the functionality your ISP has there would be able to make a change, but also depends on how that list with your ISP works, e.g. two possible ways could be:
Anything that CLAIMS to be example.com
Anything that CLAIMS AND IS VERIFIABLE to be example.com.
If your ISP takes the extra kind of “security” step of #2, it wouldn’t work.
Thank you for your help. I will try the simple way with my ISP first in hopes it may correct it. If not I will contact them directly to see if anything can be done. If not, then I may need to reconsider using the forwarding service.
