The message as you see here, was not DKIM signed at the time that it reached Cloudflare's Email Rout
The message as you see here, was not DKIM signed at the time that it reached Cloudflare's Email Routing ("DKIM status: none").
As per the Yahoogle! requirements (Google and Yahoo requirements) per 2024-02-01 (February 2024), emails MUST be authenticated.
SPF cannot survive message forwarding, so the only option you have, is to properly DKIM sign your emails (WITH PROPER ALIGNMENT to your own domain), if you expect any deliveries to Yahoo and Google after that date.
Without a such proper DKIM set up from the sender's side, Google will give the message the cold shoulder.
As per the Yahoogle! requirements (Google and Yahoo requirements) per 2024-02-01 (February 2024), emails MUST be authenticated.
SPF cannot survive message forwarding, so the only option you have, is to properly DKIM sign your emails (WITH PROPER ALIGNMENT to your own domain), if you expect any deliveries to Yahoo and Google after that date.
Without a such proper DKIM set up from the sender's side, Google will give the message the cold shoulder.
