With (the free) Gmail ("@gmail.com")you will never it get it to DKIM sign your outbound for you. As
With (the free) Gmail ("@gmail.com")you will never it get it to DKIM sign your outbound for you. As such, there isn't the DKIM authentication mark.
As such, you cannot fulfil the DKIM alignment requirement for DMARC.
Gmail authenticating SPF with @gmail.com, so adding _spf.google.com to yuor own domain's SPF is literally useless there.
Since the SMTP MAIL FROM (envelope from) would be @gmail.com, you likewise cannot have have no SPF alignment for DMARC.
Since both the DKIM and SPF alignment ones are failing, DMARC with a custom domain would always fail, even if you manage to get Gmail to send with a header From of your custom domain, e.g."@example.com".
As such, you cannot fulfil the DKIM alignment requirement for DMARC.
Gmail authenticating SPF with @gmail.com, so adding _spf.google.com to yuor own domain's SPF is literally useless there.
Since the SMTP MAIL FROM (envelope from) would be @gmail.com, you likewise cannot have have no SPF alignment for DMARC.
Since both the DKIM and SPF alignment ones are failing, DMARC with a custom domain would always fail, even if you manage to get Gmail to send with a header From of your custom domain, e.g."@example.com".
![[Email routing] Several rules on the same custom address by marcioc...](https://images-ext-1.discordapp.net/external/2u6uKFT3T3gE-4u_XVRpOiXUddJSlyfe-249cQjwDvo/https/opengraph.githubassets.com/b6e74a24bf0e4f167904a0d7da481ea1a163d479ca835edf7682db37ddfc78c3/cloudflare/cloudflare-docs/pull/2865)
