A DMARC policy not enabled warning, or a policy set to none, means your domain isn’t asking other mail servers to do anything about mail that forges it. Don’t fix that by flipping straight to reject. Publish a policy that only monitors. Read the reports it sends. Find every service that sends mail as the office, and fix what fails. Then step up to quarantine and reject. DMARC stands for Domain-based Message Authentication, Reporting and Conformance. It’s how a domain tells other servers what it would like done with mail that fails its checks.
Without an enforced policy, other mail servers can deliver mail that forges the office’s domain. A fake invoice may reach a customer under your name. But an office that jumps straight to reject, before it finds every service that sends mail as it, can have its own invoices and newsletters refused.
What Does DMARC Policy Not Enabled Mean?
DMARC is the setting that tells other mail servers how you’d like them to treat mail that claims to come from your domain but fails the checks. A warning that it’s not enabled, or a policy of none, means the domain has asked for no action. Forged mail may still be delivered. Receiving servers decide.
The Federal Trade Commission (FTC) covers this in plain terms. The FTC’s small-business cybersecurity guide speaks to businesses whose email uses their own domain name. It advises making sure the email provider has SPF and DKIM, along with DMARC. It says DMARC lets the domain owner ask receiving servers to reject a suspicious message, flag it as spam or take no action. You can also set it up so you’re notified when that happens.
SPF and DKIM check the address a server uses behind the scenes. DMARC checks that this address matches the from address a person sees.
What Do None, Quarantine and Reject Do?
They’re the three values a DMARC policy can take. Each one is a request to the receiving server, not an order. They run from the weakest, which only watches, to the strongest, which asks servers to refuse mail that fails. The receiving server decides what to do with each request.
- None. The domain owner states no preference about mail that fails. Reports can still come back, which is why it’s the place to start.
- Quarantine. The domain owner considers mail that fails to be suspicious. A server that honors it may send that mail to a spam or quarantine folder instead of the inbox.
- Reject. Receivers are asked to refuse mail that fails the check.
These values are defined in RFC 9989, the current DMARC standard, published in May 2026. It replaced the older RFC 7489 and dropped that version’s setting for applying a policy to only a share of the mail, because servers applied it unevenly. In its place is a testing flag. It asks servers to treat failing mail one step more gently than the published policy while the owner checks the setup.
Why Not Jump Straight to Reject?
Legitimate mail your office sends can fail the check too. A policy of reject asks other servers to refuse mail that fails. If one of your own services isn’t set up to pass, its mail could be turned away along with the forgeries. Watching first shows you which senders need work.
In a small Florida office, the mail provider may not be the only system sending mail as your domain. An invoicing service may send it too. So may a newsletter service, a helpdesk, a website form or the system that emails payment receipts. A sender that isn’t set up to pass the check can have its mail quarantined or refused once the policy tightens.
The FTC puts the risk in its own words: “It takes some expertise to configure these tools so they work as intended and don’t block legitimate emails.” That’s why the order matters. Watch first. Tighten second.
Moving From None to Reject, Step by Step
Start from wherever your policy stands and move up one step at a time. Read the reports at every step before you take the next one. If you’re starting with no policy at all, the first step is the same.
- Publish a policy of none with reports turned on. The reports can show who’s sending mail as your domain. Both the FTC and the DMARC specification describe the owner being told about mail that fails.
- List every sender. Match the reports to your mail provider and to every other service that sends mail as the office. Anything you don’t recognize deserves a closer look.
- Fix what fails. Each legitimate sender may need its own setup so its mail passes. Use your mail provider’s instructions and each service’s own instructions.
- Move to quarantine, testing first. You can publish quarantine with the standard’s testing flag on, so failing mail is still handled as it was under none while you watch the reports. Turn the flag off once the reports stay clean.
- Move to reject. Take this step only when the reports show every legitimate sender passing.
There’s no set number of weeks for any of this. The reports, not the calendar, tell you when to move. A sender you missed may still turn up later, so it’s sensible to keep reading them after you reach reject.
Who Makes the Change, and What to Ask
A DMARC policy is published as a setting in your domain’s DNS records. So whoever controls the domain account has to be able to make the change. If you’re not sure who that is, start with who controls the account behind your domain name.
Before anything changes, put a few plain questions to your mail provider and to whoever runs the domain:
- Does the provider support all three authentication tools for the office’s domain?
- Who can change the domain’s DNS settings?
- Who reads the reports, and who fixes a sender that fails?
DMARC covers mail that claims to come from your domain. Filtering the mail that arrives in your inbox is a separate job, which is why a spam filter needs someone tuning it.
O&O Systems’ Email Security and Spam Protection team tailors email protection rules to match a business’s needs and compliance requirements.
O&O Systems also offers a free Domain Security Risk Assessment that scans a domain. It returns a summary of risks across email, cloud, web and infrastructure, including risky email configurations such as missing DKIM and DMARC.
Frequently Asked Questions About DMARC Policy
What is DMARC?
DMARC is a setting on your domain that tells other mail servers what you’d like done with mail that claims to be from you but fails the checks. It can ask them to take no specific action, treat the mail as suspicious or refuse it. Receiving servers make the final call.
Is a DMARC policy of none the same as having no DMARC?
Not quite. A policy of none is a published policy that requests no specific action, and if it names an address for reports, receiving servers can still send you reports. That makes it the starting point. With no policy published at all, the domain has made no request and named no report address, so there are no reports to learn from.
Will DMARC stop all fake email?
No. It asks receiving servers to act on mail that fails the checks for your own domain, and those servers decide what to do. It’s one layer. Filtering the rest of what lands in your inbox is a separate job.
Do I need SPF and DKIM too?
The FTC advises it. Its guide suggests making sure your email provider has all three tools. DMARC works from the results of the SPF and DKIM checks, so they belong together.
How long does it take to get to reject?
There’s no set time. It depends on how many services send mail as your office and how each one gets fixed. The reports, not the calendar, show when every legitimate sender is passing. That’s when reject makes sense.
Turn the Policy Up in Steps
A policy of none is a fine place to start, as long as it doesn’t become the place you stop. Watch the reports. Fix your own senders. Then ask for more, one step at a time.
If a DMARC policy not enabled warning is on your report, ask O&O Systems to check your domain’s DMARC policy before you change anything.