Hotfix 2026.10.26.9: DNS setup counts a domain's own valid DMARC or SPF as done #241

Merged
jcoffey-dev merged 2 commits from fix/239-dns-own-record-2026 into release/2026 2026-11-18 19:14:34 +00:00
2 Commits
Author SHA1 Message Date
jcoffey-dev 7793506613 Version 2026.10.26.9
ci / build (pull_request) Skipped
ci / publish (pull_request) Skipped
ci / notices (pull_request) Successful in 54s
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 1m26s
2026-11-18 12:12:25 -07:00
jcoffey-dev 3ca4ca8f16 DNS setup: a domain's own valid DMARC or SPF counts as done (#239)
The DNS setup pages marked every published record that wasn't exactly
the suggested one as different, in amber, with a note about old records
in caches, and never reached "All set". A DMARC with the domain's own
report addresses, or an SPF with an extra include, is neither: the
admin chose it and it's valid.

The pages now judge DMARC and SPF with coreState from #237. A single
well-formed record of the domain's own gets a green badge ("Your own
record, valid"), counts toward the progress and "All set", and a note
says it can stay. The amber mark and its caching note stay for records
that really differ: two SPF records, a DMARC with no policy, an MX or
DKIM key elsewhere.
2026-11-18 12:12:25 -07:00