This issue has been reported here 3 years ago but has not been fixed.
The mail sent by firstname.lastname@example.org is from IP 126.96.36.199, which violates the SPF record (SOFTFAIL).
$ dig +short TXT caddy.community @188.8.131.52
"v=spf1 include:sendgrid.net ~all"
The IP 184.108.40.206 belongs to gandi, not sendgrid.
$ dig +short -x 220.127.116.11 @18.104.22.168
To fix this issue, the domain administrator should update the SPF record.
Thanks for the notice; not really sure how or when that changed… will look into it soon.
I submitted a request to have the records updated. Will let you know if I hear back!
The SPF record has been updated
Yeah the SPF record has been updated, but,
$ dig +short TXT caddy.community @22.214.171.124
"v=spf1 include:sendgrid.net ip4:126.96.36.199 ~all"
I think including an IP may be inappropriate, since mails from Gandi are not guaranteed to be sent through the IP 188.8.131.52.
According to Gandi’s document, The domain
_mailcust.gandi.net should be included into SPF record, which puts all the Gandi mailer IPs into consideration.
$ dig +short TXT _mailcust.gandi.net @184.108.40.206
"v=spf1 include:_nblcust.gandi.net ?all"
$ dig +short TXT _nblcust.gandi.net @220.127.116.11
"v=spf1 ip4:18.104.22.168/26 ip6:2001:4b98:dc4:8::/64 ip4:22.214.171.124/28 " "ip4:126.96.36.199/32 " "ip4:188.8.131.52/32 " "?all"
Therefore, the SPF record for caddy.community should be updated to
v=spf1 include:sendgrid.net include:_mailcust.gandi.net ~all if SendGrid is not to be removed.
Thank you very much!
So, we don’t actually use gandi to send emails. We use sendgrid, and I just did a test and the SPF is passing and everything seems to be fine now?
This topic was automatically closed after 90 days. New replies are no longer allowed.