Skip to content

docs: note DMARC RFC support in the features list#778

Merged
seanthegeek merged 6 commits into
masterfrom
docs-rfc-features
May 21, 2026
Merged

docs: note DMARC RFC support in the features list#778
seanthegeek merged 6 commits into
masterfrom
docs-rfc-features

Conversation

@seanthegeek
Copy link
Copy Markdown
Contributor

@seanthegeek seanthegeek commented May 21, 2026

Summary

Brings the Features list (in README.md and docs/source/index.md) up to date with what parsedmarc actually supports:

  • Report standards — aggregate/rua: draft and 1.0 schemas (RFC 7489) plus the new RFC 9990 schema for the final DMARC standard (RFC 9989); failure/ruf: RFC 6591 and RFC 9991; SMTP TLS Reporting: TLS-RPT (RFC 8460)
  • Output destinations — now lists every sink: Elasticsearch, OpenSearch, Splunk, and PostgreSQL (premade dashboards), plus Apache Kafka, Amazon S3, Azure Log Analytics (Microsoft Sentinel), Graylog (GELF), syslog, and HTTP webhooks

Also re-aligns the Python compatibility table so the status-emoji rows satisfy markdownlint MD060 (the rule measures display width; the emoji render two columns wide).

Docs-only; both files kept in sync.

Note

The features list mentions PostgreSQL, which lands via #667. Both are targeted at 10.0.0 — merge #667 first (or accept that this doc briefly leads master until it does).

Test plan

  • cd docs && make html builds cleanly
  • markdownlint-cli2 reports 0 MD060 errors on both files

seanthegeek and others added 2 commits May 21, 2026 12:48
The features list only mentioned "draft and 1.0" aggregate reports. Spell
out the standards parsedmarc parses: RFC 7489 (legacy DMARC) and the final
DMARC standard RFC 9989 with RFC 9990 aggregate reports, RFC 6591 and
RFC 9991 failure reports, and RFC 8460 SMTP TLS reports.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The emoji cells were padded for display width, leaving the source pipes
misaligned by character count and tripping markdownlint MD060. Re-pad so
every row's pipes line up by codepoint.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@codecov
Copy link
Copy Markdown

codecov Bot commented May 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 85.54%. Comparing base (ef2fb84) to head (da56f60).
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #778   +/-   ##
=======================================
  Coverage   85.54%   85.54%           
=======================================
  Files          17       17           
  Lines        4628     4628           
=======================================
  Hits         3959     3959           
  Misses        669      669           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

seanthegeek and others added 4 commits May 21, 2026 13:14
Expand the features list to cover every output sink: Elasticsearch,
OpenSearch, Splunk, and PostgreSQL (premade dashboards), plus Kafka,
Amazon S3, Azure Log Analytics (Microsoft Sentinel), Graylog (GELF),
syslog, and HTTP webhooks.

Also re-pad the Python compatibility table using display width (the
status emoji render two columns wide), which is what markdownlint MD060
measures — the previous codepoint-based padding still tripped the rule.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PostgreSQL is a storage target without bundled premade dashboards, so it
shouldn't sit inside the "for use with premade dashboards" phrase next to
Elasticsearch/OpenSearch/Splunk.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Switch the markdown tables (Python compatibility, env-var section mapping)
to compact single-space format. It reads cleanly in a text editor and
sidesteps the column-alignment churn that emoji/variable-width content
caused with padded tables (markdownlint MD060). The reStructuredText grid
table in dmarc.md is left as-is — it relies on multi-line cells markdown
can't express.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@seanthegeek seanthegeek merged commit caac8e6 into master May 21, 2026
11 checks passed
@seanthegeek seanthegeek deleted the docs-rfc-features branch May 21, 2026 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant