Email Configuration Updates

Shield Email Updates

Shield uses Mailchimp Transactional/Mandrill to deliver emails on your behalf to your clients. Mailchimp recently announced that Google and Yahoo are enacting new sending requirements that will go into effect February 14th. Mailchimp is making mandatory updates to stay in compliance with these changes. In order for Shield to continue being able to successfully deliver emails to your clients, urgent updates to your DKIM records and potentially the creation of a DMARC policy are required. See instructions below.

DKIM

Create two CNAME records on the sending domain you use for Shield: one with the name “mte1._domainkey.{The Sending Domain You Use For Shield}” and value “dkim1.mandrillapp.com”, and another with name “mte2._domainkey.{The Sending Domain You Use For Shield}” and value “dkim2.mandrillapp.com”.

For example, if your sending domain was example.com, you would create the following CNAME records for example.com:

Name: mte1._domainkey.example.com
 Value: dkim1.mandrillapp.com

Name: mte2._domainkey.example.com
 Value: dkim2.mandrillapp.com

DMARC

Note: if you already have a DMARC record configured for your sending domain, this section should be skipped

Create and save a TXT record in your DNS with a name of “_dmarc.{The sending domain you use for Shield}” and value of “v=DMARC1; p=none”.

For example, if your sending domain was example.com, you would create the following TXT record in your DNS:

TXT Record Name: _dmarc.example.com
TXT Record Content: v=DMARC1; p=none

This update MUST be completed before February 14 in order for Shield to continue to successfully deliver emails to your clients.

Additional information can be found here: https://mailchimp.com/developer/release-notes/new-sending-domain-authentication-requirements/