Gmail and Yahoo have refused unauthenticated bulk mail since February 2024. See where your domain stands against the parts of their requirements that live in DNS, and what is left to confirm yourself.
Meeting the bar is not the same as being protected. Google accepts a DMARC record set to p=none, which satisfies the requirement and instructs receivers to do nothing about anybody forging you.
Since February 2024 both require SPF and DKIM on your sending domain, a published DMARC policy, alignment between the From domain and whichever of SPF or DKIM passes, one-click unsubscribe on marketing mail, and a spam complaint rate below 0.3%. Bulk means roughly 5,000 messages a day to their users.
Yes. A published record with p=none satisfies Gmail and Yahoo, and protects nobody from forging your domain. Treat it as the starting line rather than the finish.
The formal thresholds do not, but the signals are the same ones every receiving server weighs. A small business with no SPF record still lands in spam; it simply gets filtered rather than rejected.
It is a pair of headers on the message itself, List-Unsubscribe and List-Unsubscribe-Post, and nothing about it is published in DNS. Send yourself a copy of a campaign and read the raw headers, or paste them into the header analyzer.
The domain in the From address a human sees has to match the domain that SPF or DKIM validated. Mail that passes SPF for a sending platform's own domain but shows your domain in From is not aligned and does not count.