Domain-based Message Authentication, Reporting & Conformance is an email authentication protocol that is built on top of SPF and DKIM protocols. SPF and DKIM are prerequisites of DMARC and must be in place before setting up a DMARC policy. A DMARC policy allows a sender to indicate that their emails are signed by SPF and DKIM and tells a receiver what to do if neither of those authentication methods passes – such as junk or bounce the email. DMARC removes the guesswork from the receiver’s handling of these failed emails, limiting or eliminating the user’s exposure to potentially fraudulent & harmful emails. DMARC also provides a way for the email receiver to report back to the sender about emails that pass and/or fail DMARC evaluation.
Note there is no specific configuration needed in CampaignRaven besides ensuring that your SPF and DKIM are both valid. Further, a DMARC policy on your domain(s) will affect all of your email sending from that domain (not just the mail you are sending through CampaignRaven) so you need to ensure you are using SPF and DKIM for all your email delivery.
The following are example DMARC TXT entries to set up on your domain(s) DNS.
Option 1- Setup your DMARC policy with a simple, most common DMARC record.
Host/Name:_dmarc Value: v=DMARC1;p=none;
Option 2 - We don’t recommend getting reports, so you can have a slightly more detaild setting:
Host/Name:_dmarc Value: v=DMARC1;p=none;pct=100;aspf=r;adkim=r;