This article contains information on Mimecast's automated DMARC aggregate reports, detailing how they provide insights into email authentication, corrective actions, and DMARC policy effects, along with considerations for reporting addresses and recommended tools for analysis.
Mimecast provides automated daily DMARC aggregate reports as outlined in Section 7.2 of RFC 7489 (an RFC is a Request For Comments, a formal specification from the Internet Engineering Task Force).
These reports provide domain owners with visibility and insight into the following:
- What email messages sent from their domains pass Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM) authentication, and DMARC.
- The corrective action to be taken by Domain Owners.
- How the domain owners' DMARC policy affects the emails processed by receiving servers, e.g., None, Quarantine, or Reject.
Domain owners can use this information to understand their email message flow and authentication better, leading to updates to their DMARC policy to apply stricter enforcement.
Reporting Addresses
DMARC aggregate reports will be sent automatically to those domains that the global Mimecast Cloud Gateway service processes for our customers and where the sender requests a DMARC aggregate report through the ‘rua’ attribute in their DMARC DNS.
The 'rua' tag contains a comma-separated list of mail-to URLs, that define where receivers should send aggregate reports.
DMARC Aggregate Reporting Considerations
- DMARC aggregate reports are provided on an 'as is' basis. No warranties or representations of any kind, express or implied, are given regarding the provided information's nature, accuracy, suitability, or otherwise. For more information, please see our website.
- Mimecast does not support DMARC forensic reports.
- Mimecast recommends using a DMARC reporting tool such as Mimecast DMARC Analyzer to automate the processing and visualization of DMARC aggregate reports. Please contact Mimecast for further details.
Comments
Please sign in to leave a comment.