Skip to Main Content
Back to Learning Center

"Sender requirement failed" in Google DMARC reports

Samuel ChenardBy Samuel ChenardSeptember 29, 2025Updated November 11, 20266 min read

In brief

Google's DMARC aggregate reports add a Sender requirement failed comment with an SMTP code. What each code means, whether it is temporary, and the fix.

"Sender requirement failed" in Google DMARC reports

Sender requirement failed is a comment Google writes into its DMARC aggregate reports when a message breaks one of Gmail's sender requirements. It sits in the <reason><comment> field of the report's XML and is followed by the SMTP code Gmail returned, such as 550-5.7.27 for an SPF failure. A code starting with 421 means Gmail throttled the message and the sending server can retry; a code starting with 550 means Gmail rejected it.

At a glance

Quick Takeaways

  • Google adds a <reason> element with a fixed Sender requirement failed prefix and an SMTP code to its DMARC aggregate reports.
  • The code names which requirement failed: SPF, DKIM, alignment, TLS, reverse DNS, or a general policy block.
  • 421 codes are temporary throttling; 550 codes are permanent rejections.
  • Each code points to one fix, listed in the table below. No change to your DMARC record is needed.
  • Palisade reads your DMARC aggregate reports and opens a ticket when a sending source keeps failing SPF or DKIM.

Where does the comment appear in the report?

Google's aggregate reports carry the comment inside <policy_evaluated>, in a <reason> element of type local_policy:

XMLxml
<policy_evaluated>
  <disposition>none</disposition>
  <dkim>fail</dkim>
  <spf>fail</spf>
  <reason>
    <type>local_policy</type>
    <comment>Sender requirement failed: 550-5.7.1</comment>
  </reason>
</policy_evaluated>

The “Sender requirement failed:” prefix is constant. The SMTP code after it is the part to read. The disposition field reports the result of DMARC evaluation, so a row can show none while the comment records that Gmail throttled or blocked the mail under its own sender rules.

The change was reported in August 2025 by Spam Resource. Before it, the usual trace of a Gmail rejection was the bounce in the sender's own mailbox, invisible to anyone watching a domain at scale. Now the same signal arrives in the aggregate (rua) feed, so whoever reads your DMARC reports can see why Gmail throttled or blocked a source.

Is the failure temporary or permanent?

SMTP codes that start with 4 are temporary: the receiving server refuses the message for now and the sender is expected to retry, as RFC 5321 defines. Codes that start with 5 are permanent: the message is rejected and retrying unchanged will fail again. In Google's list, the 421 codes throttle bulk senders and the 550 codes block the message.

Comparison grouping Google's SMTP error codes into 421 rate-limiting signals and 550 permanent blocks, with the meaning of each code. Codes starting with 421 signal rate limiting; 550 codes are permanent blocks.

What does each code mean, and how do you fix it?

CodeTemporary or permanentWhat failedFix
421-4.7.27TemporarySPF check failed for a bulk senderAdd the sending service to your SPF record and check it with the SPF checker. Stay under the 10-lookup limit.
550-5.7.27PermanentSPF authentication failedSame fix as 421-4.7.27.
421-4.7.30TemporaryDKIM check failed for a bulk senderConfirm the service signs with your domain using the DKIM checker. Republish the selector if the key rotated.
550-5.7.30PermanentDKIM authentication failedSame fix as 421-4.7.30.
421-4.7.32TemporaryThe From domain does not align with the SPF or DKIM domainMake SPF or DKIM pass on a domain that matches the visible From address. See SPF alignment.
421-4.7.29TemporaryThe connection was not encrypted with TLSMake your outbound server offer STARTTLS.
550-5.7.29PermanentThe connection was not encrypted with TLSSame fix as 421-4.7.29.
550-5.7.26PermanentThe message is unauthenticated: it failed SPF or DKIM, or the domain's DMARC policy blocked itMake SPF or DKIM pass for the sending service, using the fixes above.
550-5.7.25PermanentThe sending IP has no valid PTR record, or it does not match forward DNSFix reverse DNS with whoever owns the IP. On a shared platform, that is the provider.
550-5.7.1PermanentA general policy block, such as spam signals, reputation, or RFC 5322 non-complianceCheck message formatting and sending reputation rather than one authentication record.

Google's page Gmail SMTP errors and codes lists every code and its wording. 550-5.7.1 has many variants there, so read the full bounce text when you have it.

Five steps for turning a Google DMARC failure code into a fix, from locating the reason tag to verifying the resolution.

How does Palisade help you act on the data?

Palisade reads the DMARC aggregate reports for your domains and shows which sending sources fail SPF, DKIM or alignment. When a source keeps failing, Palisade opens a ticket that names it, so you can:

  • Pinpoint misconfigured SPF or DKIM records.
  • Identify alignment gaps that break DMARC enforcement.
  • Prioritize remediation based on volume and impact.

Next steps

If you’re still struggling to meet Google’s email sender guidelines, book a demo to accelerate compliance and DMARC enforcement.

Use the Email Security Score to check the public DNS baseline for your domain.

Sources

Questions readers ask

FAQs

What is the Sender requirement failed tag in Google DMARC reports?

It is a <reason> element with a fixed prefix and the SMTP code Gmail returned. It names which Google sender requirement the message failed.

How do I tell rate limiting from a hard block?

Codes starting with 421 are temporary throttling and the sender retries. Codes starting with 550 are permanent rejections.

How can I differentiate between SPF and DKIM failures in the report?

Look at the spf and dkim fields inside <policy_evaluated> and match them with the SMTP code (for example, 550-5.7.27 indicates an SPF failure).

Do I need to change my DMARC record?

No. The comment is added on Google's side. Fix the authentication or DNS problem the code names.

Can I monitor a specific error code over time?

Compare the <reason> comments across consecutive aggregate reports from Google. A code that keeps appearing points to a fix that has not landed.

Turn Google DMARC findings into a managed fix path

Start in Palisade.

Get started

Share this article

Samuel Chenard

Written by

Samuel Chenard

CEO & Co-Founder, Palisade

Samuel Chenard is the CEO and co-founder of Palisade, agentic DMARC software for IT teams and MSPs, from one domain to thousands.

More from Samuel →

Related articles and tools