Rob Nagler via mailop skrev den 2024-02-27 23:30:
gmail.com [1] started failing messages from domains which are
correctly setup for SPF (and have been for some years):
550-5.7.26 Gmail requires all senders to authenticate with
either SPF or DKIM. 550-5.7.26 550-5.7.26 Authentication
results:
550-5.7.26 DKIM = did not pass 550-5.7.26 SPF [nagler.me [2]]
with ip:
[139.177.203.52] = did not pass 550-5.7.26 550-5.7.26
$ dig +short txt nagler.me [2]
"v=spf1 a mx ip4:139.177.203.52 include:_spf.google.com [3] -all"
Sending to (paid) Google Workspace domains works fine. Nothing has
changed on our end, and failures only started this morning.
Any ideas?
remove the include part :)
6 nagler.me
v=spf1 a mx ip4:139.177.203.52 include:_spf.google.com -all
1 +a:nagler.me:139.177.203.52/32
1 +mx:nagler.me:139.177.203.52/32
+ip4:139.177.203.52/32
redudendance does not help there
https://dmarcian.com/spf-survey/?domain=nagler.me
dont include anything you dont control, unless you own a google server
at all
30
netblocks are authorized
328,963 individual IPv4 addresses
Authorized netblocks produce SPF "pass" results (as opposed to
"neutral", "fail", or "softfail").
and its fails still :=)
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
