...
- "v=DMARC1; p=quarantine; pct=10" -
1 in 10 emails that fail DMARC authentication should be quarantined. The rest will be treated by the "p=none" policy. - "v=DMARC1; p=quarantine; pct=50" -
1 in 2 emails that fail DMARC authentication should be quarantined. The rest will be treated by the "p=none" policy. - "v=DMARC1; p=quarantine; pct=100" -
All emails that fail DMARC authentication should be quarantined. At this stage, you can now switch to the "p=reject" policy, and reduce or completely eliminate the "pct=100" value.
...
- "v=DMARC1; p=reject; pct=10" -
1 in 10 emails that fail DMARC authentication should be rejected at SMTP time. The rest will be processed by the recipient's mail server settings. - "v=DMARC1; p=reject; pct=50" -
1 in 2 emails that fail DMARC authentication should be rejected at SMTP time. The rest will be processed by the recipient's mail server settings. - "v=DMARC1; p=reject; pct=100" -
All emails that fail DMARC authentication should be rejected at SMTP time.
At this stage, you can consider removing the "pct=100" tag entirely because "p=reject" and "p=reject; pct=100" carry the same weight in the DMARC policy enforcement hierarchy.
In other words
...
A , a DMARC policy using these two selectors mean the exact same thing:
"v=DMARC1; p=reject; pct=100"
"v=DMARC1; p=reject"
...