Email security
DMARC from p=none to p=reject: a safe rollout for small teams
A DMARC record with p=none only watches. Spoofed email that claims to come from your domain still arrives. Moving to quarantine and then reject stops it, as long as your own mail passes first.
What DMARC checks
DMARC is a TXT record published at _dmarc.yourdomain. A message passes DMARC when SPF or DKIM passes and the passing domain aligns with the domain in the From address the reader sees. The p tag sets the policy for the domain. The none policy only monitors traffic. The quarantine policy sends failing mail to spam. The reject policy refuses the mail entirely.
For a small company, this means you can control how other mail servers handle messages that claim to be from you. If you start with a none policy, you can see who is sending mail on your behalf without blocking any messages. You should move to quarantine or reject once you know your legitimate mail passes these checks. This prevents others from spoofing your domain.
Start by reading the reports
The rua tag provides an email address to receive daily aggregate reports from large mailbox providers. These reports list every server that sent mail using your domain. They show whether each sender passed SPF and DKIM checks. This data lets you see who is sending mail on your behalf and if those messages are authenticated correctly.
Common senders that fail these checks at first include your CRM, billing system, help desk, and newsletter service. For a small company, this means you must identify every legitimate tool that sends mail for you. You then need to add each of these senders to your SPF record or set them up to sign with DKIM for your domain.
Move to quarantine, then reject
Change your policy from p=none to p=quarantine once reports show your own senders pass. You can use the pct tag to apply this policy to a share of failing mail. For example, set pct=25 to make the change in steps. This allows you to test the effect on your email delivery before applying the policy to all messages.
Move to p=reject after a few weeks of clean reports. This final step ensures that unauthorized mail is blocked entirely. For a small company, this means you reduce the risk of someone spoofing your domain. Start with a small percentage of mail and increase it slowly to avoid blocking legitimate messages.
Why it matters now
Google and Yahoo now require bulk senders to publish SPF, DKIM, and DMARC records. This applies to those sending more than 5,000 messages a day to their users. Customer security questionnaires also frequently ask if you have these three protocols in place. Phishing attacks that use a supplier's real domain are a common way for attackers to enter a company.
These requirements mean your emails may be blocked if you lack these records. You also risk losing customers who require these security standards during their vetting process. Attackers can spoof your domain to trick your partners if you do not have a strict policy. You should implement these records to ensure email delivery and protect your brand reputation.
Questions
Will p=reject block my own email?
Only mail that fails both SPF and DKIM alignment is rejected. You can read aggregate reports first to see which of your senders would fail.
What is a safe first DMARC record?
A safe first DMARC record is v=DMARC1; p=none; rua=mailto:dmarc@yourdomain. This record collects reports without changing delivery.