Import a report
Import one file at a time. Signal accepts.xml, .gz, .gzip, .zip, and .eml files.
The result identifies newly imported reports and duplicates.
1
Obtain the aggregate report
Use a report sent to the rua destination in your DMARC record or exported from your reporting mailbox.
2
Preserve the original file
Do not edit provider XML before import.
Keep the original if your operational policy requires evidence retention.
3
Import
Open DMARC, choose the file, and review the imported and duplicate counts.
4
Investigate sources
Find unexpected source IPs, authentication failures, or disposition changes.
Time ranges
Choose 30 minutes, 1 hour, 6 hours, 12 hours, 24 hours, 7 days, 30 days, 90 days, or a custom range up to 90 days. A short range helps incident work; a longer range establishes normal sender inventory.Metrics
Dispositions
A report can show pass or policy actions such asnone, quarantine, or reject.
Investigate an unexpected source before authorizing it in SPF or changing policy.
Adding every observed sender to SPF can legitimize abuse and exceed SPF lookup limits.
SDK example: DMARC advisor signals
The public SDK does not expose DMARC report import or report-list operations. Keep file import and report inspection in the dashboard. The public metrics advisor does expose the project’s DMARC alignment, policy, domain, observed-message, and recommendation signals:TypeScript