Since February 2024, Gmail has required DMARC for bulk senders. This is not a suggestion or best practice. It is a mandatory requirement enforced at the protocol level. This guide answers common questions about DMARC and Gmail.
Gmail's DMARC Requirement
For bulk senders (those sending 5,000+ messages per day to personal Gmail accounts), Gmail requires:
- A published DMARC record in DNS
- Minimum policy of p=none
- Either SPF or DKIM must pass with alignment
What About Smaller Senders?
Gmail does not explicitly require DMARC for senders below the 5,000 message threshold. However, DMARC still benefits smaller senders:
- Improved deliverability through better authentication
- Protection against domain spoofing
- Visibility into who is sending as your domain
- Preparation for potential growth past the threshold
We recommend implementing DMARC regardless of your sending volume. The effort to implement is modest, and the benefits are significant.
Minimum Acceptable DMARC Record
The simplest DMARC record that satisfies Gmail's requirement:
v=DMARC1; p=none; rua=mailto:[email protected]
This record:
- Declares DMARC version 1
- Sets policy to none (monitor only)
- Specifies an email address for aggregate reports
p=none Is Just the Start
While p=none meets Gmail's minimum requirement, it does not protect your domain from spoofing. Work toward p=quarantine and eventually p=reject for full protection.
What Happens Without DMARC?
Bulk senders without DMARC face:
- Increased spam folder placement
- Temporary delivery errors (4xx codes)
- Potential permanent rejection (5xx codes)
- Poor reputation in Google Postmaster Tools
Gmail's enforcement has progressively strengthened since 2024. By November 2025, non-compliant messages are actively rejected rather than just filtered.
DMARC Alignment for Gmail
Gmail requires that at least one authentication method passes with alignment:
- SPF Alignment: The Return-Path domain matches (or is a subdomain of) your From header domain
- DKIM Alignment: The d= domain in your DKIM signature matches (or is a subdomain of) your From header domain
Having both aligned provides redundancy, but only one is required for DMARC to pass.
Steps to Implement DMARC for Gmail
- Verify SPF: Ensure all sending sources pass SPF
- Verify DKIM: Ensure all sending sources have valid DKIM signatures
- Check alignment: Confirm SPF or DKIM domains align with your From header
- Publish DMARC: Add the TXT record at _dmarc.yourdomain.com
- Monitor reports: Analyze aggregate reports for authentication failures
