If you are unsure whether you need a DMARC record, see DMARC explanation page.
If you would like to add a DMARC record, you can create a TXT DNS record in our control panel.
_dmarc.example.org
or _dmarc.example.net
v=DMARC1; p=none;
or v=DMARC1; p=reject;
or v=DMARC1; p=quarantine;
The above examples represents a minimal policy you can define. And, it specifies that if a message fails the test that it should be delivered (p=none
, safest option to avoid deliverability problems), quarantined (p=quarantined
, which means sent to the spam folder) or outright rejected (p=reject
, safest option to avoid spoofed email problems).
You may also consider adding: ruf:emailto:you@example.org
which will cause any policy failures to be emailed to you. You can combine this with p=reject pct=0
which will ensure no action is taken on your email (percent of email to act on is 0%) but your policy is reject which means software that behaves differently when you have a DMARC policy of reject will kick in (for example, email list software may make adjustments to ensure your email does not violate DMARC). Meanwhile, you still get reports. The full version would then be: v=DMARC1; p=reject; pct=0; ruf=emailto:you@example.org
.
Warning: The volume of email you will get will be overwhelming! To help, you may choose to use a DMARC service provider like Postmark to manage the email and send you weekly summaries.
For more options, please see the General Record Format of the spec.