Changing a DMARC policy to 'quarantine' instructs recipient mail servers to place emails failing DMARC authentication checks (SPF and DKIM) into the spam folder. This commonly occurs due to SPF/DKIM misconfigurations, alignment issues between the 'From' address and authentication domains, uninventoried or unauthenticated email streams, or simply a misunderstanding of DMARC's implications. Experts and documentation recommend auditing sending sources, ensuring proper SPF/DKIM configuration and alignment, analyzing DMARC reports, using validation tools, and adopting a phased implementation approach (starting with 'p=none') to avoid unintended deliverability problems and protect against spoofing and phishing attacks.
10 marketer opinions
Changing your DMARC policy to 'quarantine' instructs receiving mail servers to place emails that fail DMARC authentication checks (SPF and DKIM) into the recipient's spam folder. This typically happens due to misconfigured SPF or DKIM records, domain mismatches, or unauthenticated email streams. To resolve this, it's crucial to audit and correct SPF and DKIM records, ensure proper alignment between the 'From' address and authentication domains, identify all email sources, use DMARC reporting tools to diagnose issues, and consider a gradual implementation approach to avoid deliverability problems.
Marketer view
Email marketer from Mailjet shares that setting DMARC to quarantine instructs receiving mail servers to place non-compliant emails in the spam folder. This happens because the policy signals that the sender is serious about email security. To fix this, one must ensure that SPF and DKIM records are properly configured and aligned with the sending domain to pass DMARC authentication.
9 Jun 2024 - Mailjet
Marketer view
Email marketer from ReturnPath shares that DMARC helps protect your domain from spoofing and phishing attacks. However, a quarantine policy can negatively impact deliverability if not implemented correctly. They recommend a phased approach, starting with monitoring, then quarantining, and finally rejecting, after ensuring all legitimate email sources are properly authenticated.
18 Apr 2024 - ReturnPath
5 expert opinions
Changing DMARC policy to 'quarantine' can send legitimate emails to spam if not implemented correctly. This often stems from alignment issues, where SPF and DKIM records aren't in the same domain space as the visible 'From' address. A lack of understanding of all sending sources and misconfiguration of SPF/DKIM records are major contributors. DMARC reports are crucial for identifying failing mail streams. Experts recommend auditing all sending sources, ensuring SPF and DKIM alignment, and adopting a gradual approach to implementing DMARC, understanding the implications of each policy before publishing a DMARC record.
Expert view
Expert from Word to the Wise explains that moving to a DMARC quarantine policy will cause email deliverability issues when not implemented correctly. If a company has not inventoried their email streams and doesn't know what services are sending email on their behalf, they will have deliverability issues. The fix is to audit all sending sources, ensure SPF and DKIM alignment, and then gradually move to a quarantine policy.
3 Jan 2022 - Word to the Wise
Expert view
Expert from Email Geeks explains the emails are likely failing DMARC because they are not aligned. It is not enough for DKIM and SPF to pass; they must be in the same domain space as the visible From: address.
11 Feb 2022 - Email Geeks
4 technical articles
According to official documentation, implementing a 'quarantine' DMARC policy directs emails failing DMARC checks to the recipient's spam folder as a security measure. These failures frequently arise from SPF or DKIM misconfigurations, syntax errors in SPF records, or exceeding SPF lookup limits. Addressing these issues involves closely monitoring DMARC reports, analyzing aggregate reports to identify authentication failures, correcting SPF/DKIM configurations, checking DNS record accuracy, ensuring authorized sending domains, and verifying alignment between SPF/DKIM domains and the 'From' domain. Using SPF validation tools is also advised.
Technical article
Documentation from RFC Editor, defining DMARC, states that the 'quarantine' policy advises mail receivers to treat messages that fail DMARC checks as suspicious. This typically results in the messages being placed in the recipient's junk mail folder, though the exact implementation is up to the receiver. To resolve issues, administrators should analyze DMARC aggregate reports to identify authentication failures and correct underlying SPF/DKIM configurations.
11 Feb 2024 - RFC Editor
Technical article
Documentation from AuthSMTP details that a DMARC failure leading to quarantine often stems from SPF or DKIM misconfigurations. They recommend checking DNS records for accuracy, verifying that the sending domain is authorized to send emails on behalf of the 'From' address, and ensuring alignment between SPF/DKIM domains and the 'From' domain.
1 Jan 2023 - AuthSMTP
Does DMARC guarantee emails will not be flagged as spam?
How can I implement a DMARC reject policy for non-existent domains to prevent spam?
How can I implement a strict DMARC policy without blocking Google Workspace emails?
How do DMARC policies and RUA/RUF settings inherit or override each other between a domain and its subdomains?
How do DMARC quarantine and reject policies affect sender reputation and email delivery?
How does DMARC impact email deliverability, and what are the pros and cons of using it?