efaf016c5f
test / test (push) Has been cancelled
The panel now suggests policy-only DMARC by default, lets operators configure a default and per-domain report address, and DNS-checks hub _report._dmarc records. Future in-panel report ingestion is tracked as dmarc-reports in the roadmap. Co-authored-by: Cursor <cursoragent@cursor.com>
1.7 KiB
1.7 KiB
Plan: dmarc-reports
Status: candidate
Goal
SelfPost receives DMARC aggregate reports on SMTP, parses them inside the
image, and shows summaries in the panel — pass/fail by source, hints when
tighten p= is reasonable. No external DMARC SaaS and no IMAP workflow for the
operator.
Scope
In:
- Inbound SMTP for configured report addresses only (not a general backup-MX).
- gzip + XML aggregate parsing → SQLite summaries per sending domain.
- Panel page and/or per-domain section: recent reports, third-party senders, delivery health of report ingestion.
- Reuse
admin.dmarc_report_emailanddomains.dmarc_ruafor DNS templates; when enabled, suggest a SelfPost-hosted report address.
Out:
- Forensic reports (
ruf=). - Full dashboards, APIs, email alerting.
- Mailboxes for people (IMAP/POP3/webmail).
Architecture (sketch)
- Receiving MTAs → SMTP to SelfPost (hub MX).
- Postfix virtual alias or dedicated listener → panel ingest worker.
- Parse XML →
dmarc_reportstable (domain, reporter, counts, date). - Panel reads SQLite; links from domain DNS card.
May share port-25 plumbing with inbound-relay.md but must remain a separate, opt-in feature that does not forward mail upstream.
Done when
- Operator can point
rua=at an address SelfPost accepts and see parsed summaries in the panel within one reporting cycle. - With the feature off, outbound-only behaviour is unchanged.
- Documented in guide.md; migrations are backward-compatible.
Risks
- Attack surface of accepting mail (mitigate: strict recipient allow-list).
- Report volume and retention (mitigate: caps + pruning).