Help for owners
I need to set up DMARC but I am afraid of blocking my own email
Short answer
DMARC asks receivers to deliver, quarantine or reject mail from your domain that fails SPF and DKIM alignment. Google recommends starting at p=none with reports, then tightening gradually. The risk is not the record itself, it is a forgotten service that sends in your name and is then rejected.
Does this sound like your situation?
- Gmail or Yahoo requirements say I need a DMARC record and I do not have one.
- A security scan or my mail provider tells me to set a DMARC policy.
- I am afraid a strict policy will block invoices, forms or newsletters.
- Someone sent fake emails that look like they came from my domain.
- Reports are arriving as unreadable XML files.
Why does this happen?
Receivers now ask for it
Google requires bulk senders, those sending more than 5,000 messages a day to Gmail, to publish DMARC, and says the policy can be set to none. Yahoo also asks bulk senders for a DMARC policy of at least p=none.
Confirmed by support.google.com
A policy acts on mail that fails alignment
The p tag can be none (deliver and report), quarantine (spam folder) or reject (refuse). A message passes if SPF or DKIM passes and the domain matches the visible From address. It fails only if both fail.
Confirmed by knowledge.workspace.google.com
Forgotten senders get blocked
Any service that sends as your domain without proper SPF or DKIM alignment, such as an old CRM, a form plugin or a supplier's system, fails once the policy tightens.
Technical detail: Mail from your own domain keeps landing in the spam folder
Strict alignment is easy to misjudge
Google says relaxed alignment is the default and usually protects enough. Strict alignment can cause legitimate mail from subdomains to be rejected or marked as spam.
Confirmed by knowledge.workspace.google.com
SPF and DKIM must work first
Google advises setting up SPF and or DKIM first and allowing 48 hours before turning on DMARC.
Confirmed by knowledge.workspace.google.com
What can I do about it today?
- Do not publish quarantine or reject yetIf you have no record, the safe first step is a monitoring policy only. Ask your domain manager before publishing anything stricter.
- List every service that sends as youMail provider, website, shop, newsletter, CRM, invoicing, helpdesk, and any supplier that sends on your behalf.
- Set up a mailbox for reportsGoogle recommends a dedicated group or mailbox for aggregate reports because the volume can be high. Do not use your own inbox.
- Keep a copy of the DNS recordsSave the current TXT records before anything changes, so you can go back to them.
- Review the reports before tighteningRaise the policy only when the reports show your own services passing.
When should I bring someone in?
- You send mail from several systems and do not know which ones pass.
- Someone is already spoofing your domain.
- A stricter policy was published and legitimate mail started disappearing.
How do I handle it?
- Start with monitoringI publish a policy that only reports, with a mailbox for aggregate reports, and leave it long enough to see all regular senders.
- Turn reports into a sender listI read the reports and mark each source as known and passing, known and failing, or unknown.
- Fix failing senders one at a timeEach legitimate sender gets its own SPF or DKIM alignment, with a test message after each change.
- Tighten in stepsI move to quarantine, using the percentage tag where the platform supports it, then to reject, with a written way back at each step.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Which DMARC policy should I start with?
Google recommends starting with p=none and moving to quarantine or reject over time.
Can I move gradually?
Yes. Google describes a pct tag that sets the share of unauthenticated mail the policy applies to, which can be raised to 100.
Does DMARC stop spam to me?
No. It controls how receivers treat mail that claims to come from your domain.
Do I need DMARC if I send only a few emails?
Google requires it for bulk senders over 5,000 messages a day to Gmail. Smaller senders still need SPF or DKIM, and DMARC is a good addition.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.