Domains › Deliverability: what other mail servers see of this one #83

Merged
jcoffey-dev merged 1 commits from feat/deliverability-page into main 2026-10-06 01:28:11 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev 4f34cddb4d Domains › Deliverability: what other mail servers see of this one
ci / build (pull_request) Skipped
ci / publish (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 1m2s
The console side of the deliverability check (deliverability spec), on
the reports inbuxa-server #150 keeps; the menu link is server #153.

- The page (DL-17): sending addresses per node, then domains, worst
  first, each finding Fail, Warn or Couldn't check with one fix: the
  list's removal page, the domain, the setting, or a note that the
  hosting provider sets it. Passed checks folded away; no score and no
  "all good" banner, as on the Security page.
- Grading lives in the console (grade.ts): blocklists, reverse DNS,
  SPF per node, DKIM keys, DMARC alignment, MTA-STS and TLS-RPT,
  certificates. A refused lookup is Couldn't check, with the list's own
  note where it has one (Barracuda's resolver registration).
- Check now (DL-15) asks every node and polls until the receiving
  node's report is newer; it's off for ten minutes after a check.
- Blocklists asked: a switch per list, for whoever may change them.
- Needs attention (DL-18): blocklist and reverse-DNS failures.
- The domain hover card (DL-19): the domain's worst failure.
- A tenant administrator sees their domains only, as the server sends.

77 new English strings; no other catalogues yet. Listing meanings and
list notes come from the server, in English.
2026-10-05 16:43:50 -07:00