Caddy Forum registration confirmation mail is marked as spam

Site Feedback
1

Hi,

This issue has been reported here 3 years ago but has not been fixed.

The mail sent by noreply@caddy.community is from IP 217.70.183.193, which violates the SPF record (SOFTFAIL).

$ dig +short TXT caddy.community @1.1.1.1
"v=spf1 include:sendgrid.net ~all"

The IP 217.70.183.193 belongs to gandi, not sendgrid.

$ dig +short -x 217.70.183.193 @1.1.1.1
relay1-d.mail.gandi.net.

To fix this issue, the domain administrator should update the SPF record.

1 Like
2

Thanks for the notice; not really sure how or when that changed… will look into it soon.

1 Like
3

I submitted a request to have the records updated. Will let you know if I hear back!

1 Like
4

The SPF record has been updated :+1:

5

Hi @matt,

Yeah the SPF record has been updated, but,

$ dig +short TXT caddy.community @8.8.8.8
"v=spf1 include:sendgrid.net ip4:217.70.183.193 ~all"

I think including an IP may be inappropriate, since mails from Gandi are not guaranteed to be sent through the IP 217.70.183.193.

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 @8.8.8.8
"v=spf1 include:_nblcust.gandi.net ?all"

$ dig +short TXT _nblcust.gandi.net @8.8.8.8
"v=spf1 ip4:217.70.178.192/26 ip6:2001:4b98:dc4:8::/64 ip4:217.70.183.192/28 " "ip4:217.70.182.72/32 " "ip4:217.70.182.74/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!

6

Thank you!

7

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?

8

This topic was automatically closed after 90 days. New replies are no longer allowed.