Why are Google DMARC aggregate reports not being received?

Email marketer from StackOverflow User responds that issues can be caused by invalid DMARC syntax, which is a common problem. Check for common errors like semicolons, spaces, and typos.

Marketer from Email Geeks updates that the behavior is seen with one domain, which is p=reject and has two URIs in the RUA tag and uses Google Apps as their MX, indicating a possible bug related to intra-Google emails.

Email marketer from Mailhardener explains that if DMARC aggregate reports aren't received, it could be due to a misconfigured DMARC record, issues with the receiving email server, or the sending domain not having enough email volume to trigger report generation.

Marketer from Email Geeks asks if anything is different with the records on the affected domains (e.g., pct tags) and suggests verifying that the issue isn't related to the MTA not accepting the report messages.

Email marketer from Agari shares that if a domain does not have any mail flow or is newly configured, Google may not send DMARC aggregate reports. Additionally, if a RUA is managed by a third-party provider, they may have blocked reporting from that domain.

Email marketer from Postmark shares that the two primary reasons you are not receiving reports are because of the DMARC record being incorrect or there is an issue with the receiving server.

Email marketer from EmailGeekly explains one of the main reasons for not receiving reports from Google is due to having multiple redirects and/or hops in the RUA record. Google is very sensitive about this and has issues sending to RUA's that aren't immediately resolvable.

Marketer from Email Geeks explains that one of the domains that is not recieving reports from google has p=reject and has 100% SPF and DKIM alignment, one is p=none and has 5% SPF and 100% DKIM alignment.

Email marketer from Reddit suggests that the issue may be with the receiving server's configuration. This can include capacity issues on their server, incorrect setup for the DMARC reporting recipient, or issues related to firewalls and security protocols.

Marketer from Email Geeks asks if differences in DKIM or SPF configurations might be causing an issue with evaluation and the lack of reports.

Email marketer from MXToolbox explains that DMARC is a DNS record that specifies how email receivers should handle messages that fail SPF or DKIM checks. One of the first troubleshooting steps is to make sure the syntax of the record is correct and that the destination server specified in the RUA tag accepts DMARC reports.

Email marketer from Email Deliverability Forum explains that the amount of email you send impacts whether or not you receive DMARC reports. If you are only sending a small amount of emails, or your emails are being classified as spam, the receiving server may not trigger a DMARC report.

Email marketer from EasyDMARC shares that invalid `rua` or `ruf` tags in the DMARC record will cause reports to not be generated. Common mistakes can be using a non-email address in the tag, using an unresolvable domain in the tag, or using an email address to which you do not have access to verify proper DMARC record usage.

Marketer from Email Geeks notes they have found at least two domains with multiple RUAs (including themselves) that do not appear to be receiving Google aggregate reports, suggesting it might be a wider issue.

Expert from Email Geeks explains the dmarc verifier is allowed to limit the number of report destinations above the spec-required minimum of two, so it could be the reason the DMARC aggregate reports are not being recieved.

Expert from Word to the Wise explains the importance of setting up the RUA correctly and the risks of missing reports due to bad configuration.

Expert from Email Geeks asks if Google is accepting the mail, implying a potential deliverability issue.

Expert from Email Geeks asks if the DMARC specification has a limit on the number of places reports can be sent, referencing a recent discussion on the topic.

Expert from Spam Resource explains that a possible cause could be Google not sending reports because the volume of mail sent does not meet some unknown criteria Google has for report generation.

Expert from Email Geeks suggests checking that the reporting permission records are correctly in place in DNS (`_report._dmarc` stuff) for the domains not working, especially if handling is done internally.

Documentation from Microsoft explains DMARC relies on the alignment between the domain used in the From address and the domain used for SPF or DKIM authentication. If these domains do not align, or if SPF and DKIM checks fail, then the receiving mail server may not trigger DMARC reports.

Documentation from DMARC.org shares that common reasons for not receiving DMARC reports include DNS configuration errors, syntax errors in the DMARC record, or the receiving mail server blocking the reports due to spam filtering or size limitations.

Documentation from RFC 7489 explains that DMARC aggregate reports might be suppressed if the receiving domain's policy prevents the sending of reports to third parties, or if the sending domain doesn't have sufficient authentication or alignment.

Documentation from Google Workspace Admin Help explains that DMARC reports might not be delivered if the receiving server is misconfigured or has deliverability issues. The DMARC record's `rua` tag must point to a valid and accepting mailbox.