mirror of
https://github.com/domainaware/parsedmarc.git
synced 2026-08-15 19:53:18 +00:00
Sean WhalenandClaude Fable 5
e30b0ab9ec
Three unresolved review threads, all verified against cli.py's
re-raising init handler before fixing:
- elastic.py/opensearch.py: connections.get_connection() sat outside
migrate_indexes()'s try/except, so a connection-registration failure
would abort startup despite the docstring's promise that migration
errors are caught and logged. Now caught, logged, and skipped until
the next startup.
- opensearch.py: the legacy published_policy.fo migration loop did
unguarded network I/O (exists/get_field_mapping/reindex/delete), so a
transient cluster error aborted startup on the OpenSearch path while
the identical situation on the Elasticsearch path was logged and
survived. Each index's migration attempt is now wrapped, warns, and
moves on.
- opensearch_dashboards.ndjson: normalized two pre-existing panel
titles in the aggregate dashboard's panelsJSON ("Reporting
organizations " trailing space, "Map of message sources by country"
double space).
Regression tests assert migrate_indexes never propagates connection or
per-index cluster errors on either backend.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
parsedmarc
parsedmarc is a Python module and CLI utility for parsing DMARC
reports. When used with Elasticsearch and Kibana (or Splunk), it works
as a self-hosted open-source alternative to commercial DMARC report
processing services such as Agari Brand Protection, Dmarcian, OnDMARC,
ProofPoint Email Fraud Defense, and Valimail.
Note
Domain-based Message Authentication, Reporting, and Conformance (DMARC) is an email authentication protocol.
Sponsors
This project is maintained by one developer. Please consider sponsoring my work if you or your organization benefit from it.
Features
- Parses aggregate/rua DMARC reports: the legacy draft and 1.0 schemas (RFC 7489) and the new RFC 9990 schema for the final DMARC standard (RFC 9989)
- Parses failure/ruf DMARC reports (RFC 6591 and RFC 9991; formerly called forensic reports)
- Parses reports from SMTP TLS Reporting (TLS-RPT, RFC 8460)
- Can parse reports from an inbox over IMAP, Microsoft Graph, or Gmail API
- Transparently handles gzip or zip compressed reports
- Consistent data structures
- Simple JSON and/or CSV output
- Optionally email the results
- Optionally send the results to Elasticsearch, OpenSearch, Splunk, or PostgreSQL, for use with premade dashboards
- Optionally send the results to Apache Kafka, Amazon S3, Azure Log Analytics (Microsoft Sentinel), a Graylog (GELF) endpoint, a syslog server, or an HTTP webhook
Python Compatibility
This project supports the following Python versions, which are either actively maintained or are the default versions for RHEL or Debian.
| Version | Supported | Reason |
|---|---|---|
| < 3.6 | ❌ | End of Life (EOL) |
| 3.6 | ❌ | Used in RHEL 8, but not supported by project dependencies |
| 3.7 | ❌ | End of Life (EOL) |
| 3.8 | ❌ | End of Life (EOL) |
| 3.9 | ❌ | Used in Debian 11 and RHEL 9, but not supported by project dependencies |
| 3.10 | ✅ | Actively maintained |
| 3.11 | ✅ | Actively maintained; supported until June 2028 (Debian 12) |
| 3.12 | ✅ | Actively maintained; supported until May 2035 (RHEL 10) |
| 3.13 | ✅ | Actively maintained; supported until June 2030 (Debian 13) |
| 3.14 | ✅ | Supported (requires imapclient>=3.1.0) |