This article covers the DKIM authentication processes for Constant Contact and how are they managed in Valimail.

Enabling DKIM signing for your custom domain can be done from the Constant Contact admin console in the Constant Contact platform.

Constant Contact can authenticate with either CNAME or TXT DKIM keys.

Self-authenticating using DKIM CNAME records is the simplest and most secure way to authenticate your domain email address.

1. Click the profile name in the upper-right and select My Account.

2. Click the Advanced settings tab.

3. Click Add self-authentication.

4. Select Self-authenticate using DKIM CNAME records.

5. Click Continue.

6. From the drop-down, select the domain you want to use for self-authentication. If the custom domain you want to use isn’t listed, choose Select another domain from the drop-down to add and verify a new email address.

7. Click Continue.

8. Copy the CNAME record names and values to and add them in Valimail Enforce.

9. Once you’re done, click OK.

10. Click Got it.

11. Click OK to return to your account.

12. About 24 hours after you've published the CNAME records into Valimail Enforce, click Check status or Manage to finish activating your self-authentication.

13. Click Activate.

You can find these instructions on how to configure DKIM in Constant Contact using CNAME records here.

When you self-publish for authentication using a DKIM TXT record, Constant Contact generates a public/private DKIM key pair for you. We use the private key to sign your outgoing emails, while you publish the public key in the DNS records for your domain. This option is best if you have multiple Constant Contact accounts using the same domain.

1. Click the profile name in the upper-right and select My Account.

2. Click the Advanced settings tab.

3. Click Add self-authentication.

4. Select Self-authenticate using DKIM TXT record.

5. Click Continue.

6. From the drop-down, select the domain you want to use for self-authentication. If the custom domain you want to use isn’t listed, choose Select another domain from the drop-down to add and verify a new email address.

7. Click Continue.

8. Click Generate key.

9. Copy the DKIM TXT record value and selector and add them in Valimail Enforce.

10. Once you’re done, click Ok.

Note: If emails are being sent on behalf of your domain from multiple Constant Contact accounts/instances, each account/instance will need a different private DKIM key, so the procedure described above in the Configuring DKIM authentication using a DKIMTXT record for your Constant Contact emails, will need to be repeated for each separate Constant Contact account/instance. You will have multiple public keys on your DNS to correspond to the private keys. DKIM keys are differentiated by the selector - in the above example, the selector is 10008432. Constant Contact uses numbers for the selector, but that's not always the case. For example, Google uses letters for the selector instead.

You can find these instructions on how to configure DKIM in Constant Contact using a DKIM TXT record here.

You can find more detailed information on how to add a DKIM key in Valimail, here:

Once you establish that Constant Contact is an authorized sender for your domain, you will need to add the service in your Enabled Senders.

You will find more detailed information on how to add a service for your domain in Valimail, here:

Note: We encourage you to use the comment section for any useful information about your sending service, such as the name of the service owner, change request ticket numbers, etc.

Constant Contact does not support SPF alignment for their emails.

However, as long as you have DKIM configured for your domain in Constant Contact , your Constant Contact emails will pass DMARC authenticating with DKIM.

For an email to pass DMARC, it needs to pass with either SPF or DKIM, not both necessarily.

You can find out more information about their support for DMARC alignment here.