DMARC Policy Record

Introduction

In order for ESco to send emails on behalf of your domain, a valid Domain-based Message Authentication, Reporting & Conformance (DMARC) Record needs to be in place.

DMARC allows the recipient’s mail server to check the SPF and DKIM keys on the domain and verify the message was sent and authorised by the owner of the domain. If this fails, the email can be quarantined or rejected – only if the policy is configured to do so however.

Additionally Google (Gmail), Yahoo and AOL all require a DMARC record to process bulk emails sent on behalf of your domain. Otherwise bulk emails will not even be received to recipients junk or spam folders.

Regardless of whether your recipients use these or alternative services, a DMARC record should be setup to follow best practice recommendations that help all recipients receive your emails correctly.

More information on DMARC records and configuring the policy can be found here where you can check the DMARC record on your domain and view the available policy tags with explanations.

DMARC Record Requirements

ESco is unable to support domain administration tasks for third party domains and therefore require that DMARC record configuration should be handled by your domain administrator.

ESco Recommended settings:

• Don’t setup a new policy as active (quarantine or reject) unless we advise otherwise during setup
• Set a specific email inbox to receive notifications for DMARC alerts

As a minimum, please add the below text into your domains DNS text record:

v=DMARC1;p=none

This facilitates the following:

• Satisfying Google & Yahoo’s bulk sender requirements
• No emails being quarantined due to the inactive/passive policy

An example DMARC record should look like the below:

v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1

Please see here for an example email template to send to your domain administrator.