DMARC, by itself, is not a complex protocol. At its simplest, it allows a domain to define a set of email addresses to receive reports from recipient servers on email processed by them coming from that domain and a policy for how those servers should treat email that is not DMARC compliant. The complexity is the rest of DMARC…
Understanding the associated technologies
To send DMARC compliant email, your domain must also leverage SPF and DKIM. SPF records define who is a valid sender of email for your domain. You need to have all your senders in the SPF record they will not pass DMARC checks. DKIM is much more complicated: your outbound email servers and 3rd-party services must support DKIM by cryptographically signing outbound email and you need to publish the public key to allow recipient servers to decrypt the signature.
BIMI is often an end-goal for DMARC adoption but requires additional certifications and utilizes an image format that is sometimes difficult to meet.
Understanding how to get these associated technologies correctly configured is a big chunk of what needs to be done.
Understanding DMARC compliance logic
DMARC compliance is not exactly simple. An email can be compliant if:
- The sending IP address is listed in your SPF record.
- The Return-path listed in the email header is the same as the sending domain.
- The DKIM signature of the email is decrypted with the key in your DKIM record with the correct selector.
Navigating compliance can be complicated without some assistance.
Organizational Ownership
Quite often Marketing is driving DMARC adoption for business reason that improve email delivery and therefore open rates, click-through rates and, hopefully purchases:
- DMARC compliance is required for Inbox placement at many large inbox providers: Google, Yahoo, Microsoft and others.
- BIMI requires a DMARC reject policy in order to get a corporate logo next to email in the Inbox.
- A DMARC reject policy prevents bad actors from using your brand in fraud and phishing attempts.
So, if Marketing is driving, who owns the DMARC setup? Typically, IT owns DNS and outbound email servers, so IT would be responsible for configuring SPF, DKIM, DMARC and BIMI. This requires coordination, communication and getting everyone on board with DMARC adoption because it’s more than simply configuration.
DMARC Reports are Technical
While XML is human readable, DMARC XML reports are sent daily from each inbox provider you may have sent an email. If you have any appreciable outbound email volume, it becomes difficult to discern DMARC compliance from the XML alone it. Turning an IP address into a valid source, like MailChimp, Hubspot or your own servers becomes a headache.
The Adoption Process is Iterative
DMARC adoption requires patience and feedback. Once you configure SPF, DKIM and DMARC, you need to analyze DMARC reports:
- Make sure that all the senders are legitimate
- Look for senders you might have missed in your SPF record
- Make sure DKIM is properly configured for all senders
Depending on email volume and the number of senders, it could take a week or so to get sufficient data on all your senders to spot irregularities and make changes to your records to accommodate them.
Moving to a Reject Policy might seem risky
A DMARC policy of reject has real value to both Marketing and IT Security. A Reject policy instructs recipient email servers to trash email that fails DMARC compliance checks. This protects your brand from being used in fraud and phishing, including your email servers. In addition, a Reject policy is required to implement BIMI and get your logo shown alongside your email in the inbox.
The risk here is that legitimate email could be rejected if sent from a non-compliant source. Adopting a Reject policy is therefore another iterative process requiring coordination across the organization.
Maintenance is on-going
Your business is likely to add, drop or change email senders at some point. Each time Marketing adds an email marketing platform, Sales adopts a new CRM or you move from on-prem email to cloud-based, you will need to change your SPF record and monitor DMARC compliance.
How can MxToolbox help?
MxToolbox provides free tools to help you setup SPF, DKIM and DMARC as well as tools to help you read the DMARC XML reports.
MxToolbox Delivery Center provides everything you need to adopt DMARC, monitor DMARC compliance, manage adoption of a DMARC Reject policy and handling on-going maintenance. DMARC, however, does not promise inbox delivery. With support for BIMI, Inbox Placement analysis and integration with Google Spam Rates, Marketing gets all the tools they need to improve email deliverability while IT also gets the reassurance that MxToolbox has over 20 years in DNS and Email.
