@lunareclipse@kitten honestly i can excuse them missing this edge case... i don't think I've ever seen a server's FQDN being (and its PTR pointing to) a naked domain
@kitten@lunareclipse SPF can be used to check two things: the HELO (or EHLO) identity, and the envelope from domain. honestly I've never cared about the former, maybe I missed something and it is used for something important or maybe they are just doing it to follow the RFC to the letter
@mildsunrise@kitten SPF in general seems obsolete in the age of DKIM but I think I heard some places will be upset if you don't have an SPF policy as a sender?
@lunareclipse@kitten huh, I'm curious why you think that. in my mind they are for different things: SPF authenticates SMTP transactions (therefore binding the envelope from) while DKIM authenticates mail messages (so it's typically the domain who authored the email that signs it). sometimes these two domains will be different, such as in the case of a mailing list forwarding a message
@mildsunrise@lunareclipse@kitten Yeah, and then there's DMARC, which says "what to do with it" depending on the results of both of those checks (Which can be "complain only" as DMARC also contains reporting functionality)