--- title: "Email Rejected Per DMARC Policy: Causes, Troubleshooting Steps, And Fixes | DMARC Report" description: "Emails rejected by DMARC policy? Learn the common causes, troubleshoot authentication failures, and apply effective fixes to restore successful email delivery." image: "https://dmarcreport.com/og/blog/email-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes.png" canonical: "https://dmarcreport.com/blog/email-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes/" --- Quick Answer An email is rejected under DMARC when SPF or DKIM authentication fails or domain alignment is incorrect. Check DNS records, verify SPF and DKIM, review DMARC reports, and correct alignment or policy settings to restore reliable email delivery. Share [ ](https://www.linkedin.com/sharing/share-offsite/?url=undefined%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=Email%20Rejected%20Per%20DMARC%20Policy%3A%20Causes%2C%20Troubleshooting%20Steps%2C%20And%20Fixes&url=undefined%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=undefined%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F "Share on Facebook") [ ](https://reddit.com/submit?url=undefined%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F&title=Email%20Rejected%20Per%20DMARC%20Policy%3A%20Causes%2C%20Troubleshooting%20Steps%2C%20And%20Fixes "Share on Reddit") [ ](mailto:?subject=Email%20Rejected%20Per%20DMARC%20Policy%3A%20Causes%2C%20Troubleshooting%20Steps%2C%20And%20Fixes&body=Check out this article: undefined%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F "Share via Email") ![Email Rejected Per DMARC Policy](https://media.mailhop.org/dmarcreport/create-dmarc-record-1236-1788442116407.jpg) ## Try Our Free DMARC Checker Validate your DMARC policy, check alignment settings, and verify reporting configuration. [ Check DMARC Record → ](/tools/dmarc-checker/) When an email is rejected per DMARC policy, it usually means the message failed the required email authentication checks and was blocked by the recipient’s [mail server](https://www.cloudflare.com/learning/email-security/what-is-a-mail-server/). This can happen due to SPF or DKIM failures, domain alignment issues, or incorrect DNS records. Understanding the cause and following the right troubleshooting steps can help **resolve DMARC-related rejections** and improve email deliverability. ## What “Email Rejected Per DMARC Policy” Means “Email rejected per DMARC policy” means the receiving mail server refused to accept a message because it failed DMARC validation and the sender’s published [DMARC policy](https://dmarcreport.com/blog/what-is-a-dmarc-policy-and-how-does-it-affect-sending-my-emails/) instructed receivers to reject non-compliant mail. _In practical terms, the recipient’s system checked the domain’s email authentication results, found that SPF and/or DKIM did not align with the visible From domain, and applied policy enforcement_. DMARC, or Domain-based Message Authentication, Reporting, and Conformance, builds on SPF and DKIM. SPF verifies whether the sending SMTP server is authorized in the domain’s SPF record. DKIM verifies whether the message carries a valid cryptographic signature that matches the domain’s DKIM record. DMARC then checks whether either SPF or DKIM passes and aligns with the domain shown to the recipient. When you see an email rejection message such as “email rejected per DMARC policy,” it does not always **mean the message is malicious**. It may be caused by a misconfigured [DNS record](https://www.ibm.com/think/topics/dns-records), a third-party sender that has not been authorized, forwarding behavior, or an incorrect DMARC record. However, the result is the same: the email rejection harms email deliverability and may prevent legitimate business messages from reaching customers, partners, or employees. A typical DMARC policy uses one of three modes: - **p=none**: Monitor only; no enforcement. - **p=quarantine**: Send failing mail to spam or junk. - **p=reject**: Reject failing mail at the SMTP level. The phrase “email rejected per DMARC policy” usually appears when the sending domain has moved to p=reject, making the DMARC policy strict enough to block unauthenticated or misaligned messages. ![Common Causes of DMARC Rejection](https://media.mailhop.org/dmarcreport/dmarc-report-2563-1788441766950.jpg) ## Common Causes of DMARC Rejection ### SPF Misalignment or SPF Failure SPF failure is one of the most common reasons behind an email authentication failure. If your mail server or email platform is not listed in the SPF record, receiving servers may treat the message as unauthorized. Even if SPF passes, DMARC may still fail if the SPF-authenticated domain does not align with the visible From domain. For example, if your From address is [billing@example.com](mailto:billing@example.com) but the return-path domain belongs to a third-party platform, SPF may pass for the vendor domain but fail **DMARC alignment for example.com**. _Use an SPF checker to verify that your SPF record includes all authorized email-sending sources and remains within the DNS lookup limit_. If your SPF record is becoming complex, a hosted SPF solution can simplify record management and help reduce the risk of exceeding the 10-[DNS-lookup](https://www.digicert.com/faq/dns/how-does-dns-lookup-work) limit. ### DKIM Signature Problems DKIM issues can also trigger emails rejected per DMARC policy errors. A DKIM signature may fail if the message is altered after signing, the DKIM selector is incorrect, or the public key in the DKIM record is missing or malformed. A DKIM checker helps confirm whether your DKIM record is published correctly and whether the selector used by your [email service provider](https://business.adobe.com/blog/basics/email-service-providers) matches the DNS record. DKIM alignment is especially **important for email deliverability** because DMARC can pass when DKIM passes and aligns, even if SPF fails due to forwarding. Hosted DKIM can make this easier by helping teams maintain keys and selectors more consistently across multiple platforms. ### Incorrect or Overly Strict DMARC Record A misconfigured DMARC record is another frequent cause of email rejection. Common problems include syntax errors, duplicate records, missing reporting addresses, or moving too quickly from p=none to p=reject. A DMARC checker can validate your DMARC record and identify formatting issues. A DMARC generator can also help create a valid record **with the correct tags**, such as: ``` v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com; adkim=s; aspf=s ``` Before using a strict DMARC policy, review your DMARC report data with a [DMARC analyzer](https://dmarcreport.com/blog/using-a-dmarc-analyzer-to-detect-email-authentication-issues/) to understand which systems send mail on behalf of your domain. ### Third-Party Senders and SaaS Platforms Many organizations send email through marketing, support, CRM, billing, analytics, and notification platforms. If those vendors are not configured for SPF and DKIM alignment, legitimate messages may result in email being rejected per DMARC policy. Examples include help desk tools, marketing automation platforms, [transactional email](https://www.getvero.com/resources/guides/lifecycle-marketing/transactional-emails/) providers, and services connected through integrations. Tools such as Freshdesk, YouTube notification workflows, Nitro document systems, CMC Simulator platforms, and other SaaS services may need domain authentication **before sending branded email**. ![How to Troubleshoot DMARC Failures Step by Step](https://media.mailhop.org/dmarcreport/dkim-selector-5236-1788441817812.jpg) _Third-party platforms can also cause DMARC failures when they send email on behalf of your domain_. Common examples include marketing automation platforms, CRM systems, customer support tools, transactional email services, and other SaaS applications. Review each service that sends messages using your domain and make sure SPF or DKIM is properly configured and aligned with your From domain. ## How to Troubleshoot DMARC Failures Step by Step ### Step 1: Inspect the Bounce Message and Headers Start with the SMTP bounce response. It may include wording such as “email rejected per DMARC policy,” “DMARC fail,” or “message rejected due to DMARC policy.” This confirms the email rejection is related to authentication rather than a content filter or blacklist. Next, use a header analyzer to inspect authentication results. Look for: - **SPF result**: pass, fail, softfail, neutral - **DKIM result**: pass or fail - **DMARC result**: pass or fail - Alignment status - Sending IP address - Return-path domain - DKIM selector This is the foundation of **effective email troubleshooting**. ### Step 2: Validate DNS Authentication Records Check the domain’s SPF record, DKIM record, and DMARC record. A DNS record error can break authentication immediately. Use: - A DMARC checker to inspect DMARC syntax and policy. - An SPF checker to validate authorized senders and lookup count. - A DKIM checker to verify selectors and [public keys](https://www.coursera.org/in/articles/public-key). - A BIMI checker if you use BIMI for brand indicators. - A domain analyzer to review the broader domain security posture. A domain analysis tool can help identify configuration issues across key email authentication protocols, including SPF, DKIM, DMARC, BIMI, MTA-STS, and TLS-RPT. Regularly checking these configurations can help organizations detect authentication gaps and maintain a stronger email security posture. ### Step 3: Review DMARC Reports A [DMARC report](https://dmarcreport.com/) provides visibility into who is sending email using your domain. Aggregate reports show sending IPs, authentication results, alignment status, and policy outcomes. Reviewing each DMARC report in a DMARC analyzer helps you separate legitimate sources from unauthorized senders. Look for: - Authorized platforms failing alignment. - Unknown sources that **may indicate phishing**. - Forwarded messages breaking SPF. - DKIM failures caused by message modification. - Sources affected by the current DMARC policy. DMARC reporting is essential before tightening policy enforcement. Without reporting, you may reject legitimate mail and damage [email deliverability](https://dmarcreport.com/blog/how-can-dmarc-improve-email-deliverability-and-reduce-phishing-risks/). ### Step 4: Check Reputation and Threat Signals Not every email rejection is caused only by DMARC. Use a blacklist checker and reputation monitoring to determine whether your domain or IP has [sender reputation](https://emaillabs.io/en/understanding-email-sender-reputation-and-how-it-affects-email-deliverability/) problems. AI Driven [Threat Intelligence](https://www.recordedfuture.com/threat-intelligence), security threat analysis, a phishing URL checker, and lookalike domain monitoring can also help identify abuse targeting your brand. Reputation monitoring, alerts, and threat intelligence can help security teams detect suspicious sending patterns, spoofing attempts, and unexpected authentication or policy changes. These insights provide greater visibility into email activity and can help organizations respond quickly to issues that may affect email security and deliverability. ## Practical Fixes for SPF, DKIM, and DMARC Alignment Issues ### Fix SPF Alignment To fix SPF-related email rejected per DMARC policy errors: 1. Identify every authorized sender. 2. Add approved senders to the SPF record. 3. Remove obsolete vendors. 4. Avoid exceeding the **10 DNS lookup limit**. 5. Use Hosted SPF if your SPF record is too complex. _SPF Analytics Reporting and SPF analytics can help show which sources are passing, failing, or misaligned. If a source cannot align SPF with your domain, configure DKIM instead_. ### Fix DKIM Alignment To fix DKIM issues: 1. Enable DKIM signing in each email platform. 2. Publish the correct DKIM record in DNS. 3. Confirm selector accuracy with a DKIM checker. 4. Make sure the DKIM signing domain aligns with the From domain. 5. Rotate keys periodically for security. DKIM Analytics Reporting and DKIM analytics help identify which vendors are signing properly and which are causing email authentication failure. Hosted DKIM can simplify key management for organizations with many senders. ### Fix DMARC Policy and Reporting If legitimate messages are being blocked, temporarily adjust your DMARC policy from p=reject to **p=quarantine or p=none** while you investigate. Then use a DMARC analyzer to review each DMARC report and correct authentication gaps. A DMARC generator helps create a correctly formatted DMARC record, while a DMARC checker verifies whether the published record is valid and properly configured. For organizations looking to simplify ongoing DMARC management, hosted DMARC solutions can centralize policy configuration, reporting, analytics, and updates, making it easier to monitor and maintain email authentication across domains. For example, a staged DMARC policy could look like: ``` v=DMARC1; p=none; rua=mailto:dmarc@example.com ``` Then: ``` v=DMARC1; p=quarantine; pct=50; rua=mailto:dmarc@example.com ``` Finally: ``` v=DMARC1; p=reject; rua=mailto:dmarc@example.com ``` This gradual approach reduces unexpected email rejection. ![Best Practices to Prevent Future DMARC Rejections](https://media.mailhop.org/dmarcreport/have-i-been-pwned-4123-1788441870759.jpg) ### Strengthen Related Protocols DMARC works best as part of a broader email security strategy. Consider: - BIMI and Hosted BIMI for verified brand **logos in supported inboxes**. - BIMI Reporting and a BIMI checker to validate implementation. - MTA-STS and Hosted MTA-STS to enforce secure mail transport. - TLS-RPT and TLS-RPT reporting to monitor [Transport Layer Security](https://ironscales.com/glossary/transport-layer-security) delivery issues. - Hosted services for DNS-heavy authentication management. These controls improve domain trust and support long-term email deliverability. ## Best Practices to Prevent Future DMARC Rejections ### Maintain a Complete Sending Inventory _Document every platform, application, and mail server that sends on behalf of your domain_. Include marketing platforms, CRMs, help desk systems, billing tools, internal SMTP relays, and API-based senders. API Developer Tools, MCP Server workflows, and integrations can help automate domain checks, reporting, and alerting. For technical teams, [Application Programming Interface](https://www.f5.com/glossary/api) developer tools are especially valuable when managing authentication across many domains or tenants. ### Monitor Authentication Continuously Do not treat DMARC as a one-time DNS project. Use a DMARC checker after every DNS change, review each DMARC report, and analyze trends **with a DMARC analyzer**. A self service tour of platform features can help teams understand tools such as DMARC AI Agent, Email Deliverability Tester, Power Alerts, and Domain Analyzer. Continuous monitoring allows you to catch email authentication failure before it becomes widespread email rejection. ![Solving the Email Rejected Per DMARC Policy Error](https://media.mailhop.org/dmarcreport/what-is-dmarc-5896-1--1788441961171.jpg) ### Use Hosted DMARC for Easier Management Hosted DMARC is useful for organizations that want centralized control over their DMARC policy, DMARC record, reporting, and enforcement strategy. Hosted DMARC reduces manual DNS edits, helps prevent syntax errors, and makes it easier to move safely toward p=reject. PowerDMARC combines Hosted DMARC with Hosted SPF, Hosted DKIM, Hosted MTA-STS, Hosted BIMI, Reputation Monitoring, SPF Analytics Reporting, DKIM Analytics Reporting, BIMI Reporting, and **AI Driven Threat Intelligence**. These hosted services improve visibility, simplify email policy management, and support stronger email deliverability. ### Move to Enforcement Gradually The safest path is to start with monitoring, resolve alignment problems, then increase policy enforcement over time. Avoid switching directly to p=reject unless your DMARC analyzer shows that all legitimate sources pass authentication. Use a DMARC generator to create a clean DMARC record, validate it with a DMARC checker, monitor every DMARC report, and adjust the DMARC policy only when you are confident. This disciplined approach prevents **unnecessary email rejected** per DMARC policy errors while protecting your domain from [phishing attack](https://thehackernews.com/2026/06/meta-blocks-nso-groups-new-whatsapp.html), spoofing attack, and unauthorized use. ![Brad Slavin](https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg) [ Brad Slavin ](/authors/brad-slavin/) General Manager Founder and General Manager of DuoCircle. Product strategy and commercial lead for DMARC Report's 2,000+ customer base. [LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) ## Take control of your DMARC reports Turn raw XML into actionable dashboards. Start free - no credit card required. [Start Free Trial](https://app.dmarcreport.com/signup?plan=free) [Check Your DMARC Record](/tools/dmarc-checker/) Scan Your Domain Now Instantly scan your domain for DKIM, SPF, and DMARC issues Check My Domain Share this article [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F) [ ](https://twitter.com/intent/tweet?text=Email%20Rejected%20Per%20DMARC%20Policy%3A%20Causes%2C%20Troubleshooting%20Steps%2C%20And%20Fixes&url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F) [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fdmarcreport.com%2Fblog%2Femail-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes%2F) Copy Related Articles - [ ![10 Reasons Why DKIM Fails](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-alignment-6379.jpg) 10 Reasons Why DKIM Fails Intermediate ](/blog/10-reasons-why-dkim-fails/) - [ ![cybersecurity news](https://media.mailhop.org/dmarcreport/dmarc-check-9711-1784029121308.jpg) Accenture Sourcecode Breached, JADEPUFFER AI Ransomware, GodDamn Disables Windows Intermediate ](/blog/accenture-sourcecode-breached-jadepuffer-ai-ransomware-goddamn-disables-windows/) - [ ![AppRiver SPF Record](https://media.mailhop.org/dmarcreport/dmarc-check-7224-1785846270575.jpg) AppRiver SPF Record: How To Set It Up (Owned By Zix) Intermediate ](/blog/appriver-spf-record-setup-guide-for-zix-email-security-platform/) - [ ![Cybersecurity ransomware news](https://media.mailhop.org/dmarcreport/dmarc-report-3120-1788259786008.jpg) Berlin Ransomware Extortion, McKesson Data Breach, Boston Scientific Disrupted Intermediate ](/blog/berlin-ransomware-extortion-mckesson-data-breach-boston-scientific-disrupted/) ## Related Articles [ Intermediate 4m 10 Reasons Why DKIM Fails Apr 19, 2022 ](/blog/10-reasons-why-dkim-fails/)[ Intermediate Accenture Sourcecode Breached, JADEPUFFER AI Ransomware, GodDamn Disables Windows Jul 14, 2026 ](/blog/accenture-sourcecode-breached-jadepuffer-ai-ransomware-goddamn-disables-windows/)[ Intermediate AppRiver SPF Record: How To Set It Up (Owned By Zix) Aug 4, 2026 ](/blog/appriver-spf-record-setup-guide-for-zix-email-security-platform/)[ Intermediate Berlin Ransomware Extortion, McKesson Data Breach, Boston Scientific Disrupted Sep 1, 2026 ](/blog/berlin-ransomware-extortion-mckesson-data-breach-boston-scientific-disrupted/) ```json {"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"471","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]} ``` ```json {"@context":"https://schema.org","@type":"WebSite","name":"DMARC Report","url":"https://dmarcreport.com","description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","publisher":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}} ``` ```json [{"@context":"https://schema.org","@type":"BlogPosting","headline":"Email Rejected Per DMARC Policy: Causes, Troubleshooting Steps, And Fixes","description":"Emails rejected by DMARC policy? Learn the common causes, troubleshoot authentication failures, and apply effective fixes to restore successful email delivery.","url":"https://dmarcreport.com/blog/email-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes/","datePublished":"2026-09-03T00:00:00.000Z","dateModified":"2026-09-03T00:00:00.000Z","dateCreated":"2026-09-03T00:00:00.000Z","author":{"@type":"Person","@id":"https://dmarcreport.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://dmarcreport.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the founder and General Manager of DuoCircle, the company behind DMARC Report, AutoSPF, Phish Protection, and Mailhop. He founded DuoCircle in 2014 and has led the company's growth to 2,000+ customers across its email security product family. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement).","image":"https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"471","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://dmarcreport.com/blog/email-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes/"},"articleSection":"intermediate","keywords":"","image":{"@type":"ImageObject","url":"https://media.mailhop.org/dmarcreport/create-dmarc-record-1236-1788442116407.jpg","caption":"Email Rejected Per DMARC Policy"},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}}] ``` ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://dmarcreport.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://dmarcreport.com/blog/"},{"@type":"ListItem","position":3,"name":"Intermediate","item":"https://dmarcreport.com/intermediate/"},{"@type":"ListItem","position":4,"name":"Email Rejected Per DMARC Policy: Causes, Troubleshooting Steps, And Fixes","item":"https://dmarcreport.com/blog/email-rejected-per-dmarc-policy-causes-troubleshooting-steps-and-fixes/"}]} ```