{"id":42878,"date":"2024-11-06T10:09:01","date_gmt":"2024-11-06T10:09:01","guid":{"rendered":"https:\/\/easydmarc.com\/blog\/?p=42878"},"modified":"2025-11-18T22:02:23","modified_gmt":"2025-11-18T22:02:23","slug":"dmarc-quarantine-reject-policy-not-enabled","status":"publish","type":"post","link":"https:\/\/easydmarc.com\/blog\/dmarc-quarantine-reject-policy-not-enabled\/","title":{"rendered":"Resolving a \u2018DMARC Quarantine\/Reject Policy Not Enabled\u2019 Error"},"content":{"rendered":"\n

If you get the warning \u2018DMARC quarantine\/reject policy not enabled\u2019 when scanning your domain<\/a>, then your domain\u2019s DMARC policy is likely set to p=none. This means that although DMARC is configured, unauthenticated emails sent from your domain won\u2019t be flagged or blocked by mail servers, leaving your domain open to spoofing. The none policy is a good place to start with your DMARC policy during configuration, but it\u2019s only the beginning, and moving towards increased scrutiny should be the goal from the outset.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Key Takeaways<\/h2>\n\n\n\n
    \n
  1. The warning \u201cDMARC Quarantine\/Reject Policy Not Enabled\u201d means your domain\u2019s DMARC policy is set to p=none, allowing unauthenticated emails to pass without restriction.<\/li>\n\n\n\n
  2. Changing your policy to p=quarantine or p=reject instructs receivers to quarantine or reject unauthenticated or unaligned messages, preventing spoofing and spam falsely originating from your domain.<\/li>\n\n\n\n
  3. You can easily check your domain\u2019s setup with EasyDMARC\u2019s lookup tool and update your record following best practices for setting up DMARC.<\/li>\n\n\n\n
  4. Before enforcing stricter policies, review your DMARC reports and make sure SPF and DKIM are properly aligned.<\/li>\n\n\n\n
  5. A well-enforced policy improves domain reputation, which helps improve deliverability, strengthens brand trust, and protects your domain from impersonation, all while keeping your email communication secure and reliable.<\/li>\n<\/ol>\n\n\n\n

    How to Fix a Quarantine\/Reject Policy Not Enabled Error<\/h2>\n\n\n\n

    If you\u2019re seeing the warning \u201cDMARC quarantine\/reject policy not enabled,\u201d it likely means your domain\u2019s DMARC record is set to p=none. This mode allows you to monitor email activity without taking any action against unauthenticated messages, leaving your domain vulnerable to spoofing and phishing attacks. To fix this, you need to update your DMARC record so it enforces a protection policy.<\/p>\n\n\n\n

    Log in to your DNS management console and locate your DMARC TXT record (it starts with v=DMARC1). Then, change the p=value to one of the enforcement modes: p=quarantine sends unauthenticated emails to the recipient\u2019s spam or quarantine folder, while p=reject blocks them entirely before they reach the inbox.<\/p>\n\n\n\n

    Examples Before and After the Change <\/h3>\n\n\n\n

    Before (monitoring only):<\/p>\n\n\n\n

    v=DMARC1; p=none; rua=mailto:reports@yourdomain.com<\/p>\n\n\n\n

    After (with enforcement):<\/p>\n\n\n\n

    v=DMARC1; p=quarantine; rua=mailto:reports@yourdomain.com<\/p>\n\n\n\n

    v=DMARC1; p=reject; rua=mailto:reports@yourdomain.com<\/p>\n\n\n\n


    Once the record is updated, save your changes and allow up to 48 hours for DNS propagation. After that, recheck your domain using EasyDMARC\u2019s     DMARC Lookup tool<\/a> to confirm that your new policy is active and your domain is now protected from unauthorized email activity.<\/p>\n\n\n\n

    Fix Your DMARC Policy in 5 Steps<\/h2>\n\n\n\n

    If your DMARC policy is set to p=none, your domain is still in monitoring mode, meaning unauthenticated emails can pass through without restriction. To fully protect your domain, it\u2019s time to move toward enforcement. Here\u2019s how to do it safely and effectively.<\/p>\n\n\n\n

    Step 1: Evaluate Your Existing DMARC Policy<\/h3>\n\n\n\n

    Start by reviewing your current DMARC setup and reports. Analyze the data in your DMARC aggregate reports<\/a> to see which email sources are passing or failing authentication checks. Pay attention to SPF and DKIM alignment, as at least one must align for a valid DMARC pass.<\/p>\n\n\n\n

    This evaluation will help you identify:<\/p>\n\n\n\n