Setting Up DKIM For Your Email Domain On Ezekia

Modified on Wed, 4 Nov at 2:25 PM

DomainKeys Identified Mail (DKIM) is an email authentication method designed to reduce your emails being flagged as spam. When enabled, this will ensure notification type emails sent through Ezekia appear to come from your chosen email domain, instead of from @ezekia.com. This is useful when sending an invitation to the client portal, for example, but won't have any impact on day-to-day emails, which use a different system.

Which emails use DKIM

DKIM applies to system emails, including: 

  • compliance emails 
  • client portal invitations, updates and password resets 
  • candidate invitations 
  • new user invitations 
  • record sharing emails 
  • form completion links 
  • Outlook task and meeting emails 


These emails are always sent from an Ezekia address, whatever your DKIM settings: 

password resets for your firm’s own users 

  • test emails 
  • report download emails 
  • sequence error emails 
  • password changed notices


Emails you send from the composer or through sequences come from your own Outlook mailbox and are not affected by DKIM.


Steps to Set Up DKIM on Ezekia

Only the initial two steps require action from your Ezekia account:

  1. Access Your Ezekia Account: Log in to your Ezekia account and navigate to the Integrations section in Settings.
  2. Generate DKIM Keys: Enable DKIM using the toggle switch, and then enter your preferred originating email address (it's best to use a shared email or mailbox that you normally send notification type emails from, rather than an individual person's email). To generate your public and private keys, select "Save and generate CNAME records", make a note of these for the next steps if you're adding them yourself, or pass them onto your IT/Website support team to add them.

The following steps can be completed by your IT/Website support team, if you have one. If not, anyone with access to administer your website can do it:

  1. Add DKIM Records to Your DNS Settings:
    • Go to the DNS management page for your domain (if you can't find it, please refer to the instructions below, under Finding Your Domain’s Registrar and Common DNS/Hosting Providers).
    • Add a new record, select the type (such as TXT, CNAME etc).
    • In the Host/Name field, enter the DKIM selector name, this usually ends in "._domainkey".
    • In the Value field, enter the DKIM public key generated, this usually ends in "dkim.amazonses.com" .
    • If TTL is a mandatary field, generally, a time-to-live of 24 hours (86,400 seconds) is recommended.
    • Repeat for all keys (TXT, plus all 3 CNAME records).
  2. Check/Add SPF Record:

Adding to an Existing SPF Record: If your domain already has an SPF record, then you must add the following SPF mechanism to the existing record: “include:amazonses.com”

Adding a New SPF Record: If your custom MAIL FROM domain does not have an existing SPF record, publish a TXT record with the following value. The name of the record can be blank or @, depending on your DNS service: "v=spf1 include:amazonses.com ~all"

  1. Save the Changes: Save your DNS settings and wait for the changes to propagate, which may take up to 48 hours.
  2. Verify DKIM Setup: In your Ezekia account, select the "Verify" button back in the Integrations section in Settings to check if the DKIM setup is correctly configured. If this fails, please retrace your steps above and check the Troubleshooting section below or consult the documentation links for your DNS/hosting provider. For further assistance, please contact Ezekia Support at support@ezekia.com.


Adding more than one email domain

If your firm uses more than one email domain (for example, a separate domain for each office), you can add a DKIM address for each one. Each domain can only be added once, and each needs its own set of DNS records.


  1. Go to Settings, Integrations, DKIM Settings and click “Add another domain”.
  2. Enter the email address you want notification emails to come from on that domain. We recommend a shared mailbox such as info@ or notifications@ rather than an individual’s address.
  3. Click “Save and generate CNAME records”, then add the TXT and CNAME records to that domain’s DNS settings.
  4. Click “Verify” once the records have propagated.


If the domain is different from your firm’s own email domain, Ezekia will need to approve it before it can be used. Please contact support@ezekia.com.


Your Primary address

The first address you add becomes your Primary automatically. To change it, click the “Primary” tag on another row.


An address can only be used for sending once it has been verified. If your Primary address has not been verified yet, emails will be sent from @ezekia.com and a yellow banner will show on the DKIM Settings page.


Which address is used

When a system email is sent, Ezekia looks at the email domain of the user who triggered it. If you have a DKIM address on that domain, the email is sent from that address. If not, it is sent from your Primary address, or from no-reply@ezekia.com if no Primary is set up.


This means that if an individual’s email address is added as a DKIM address, system emails triggered by anyone on that domain will appear to come from that person. A shared mailbox avoids this.


Removing a domain

You can delete any address other than your Primary. Users on that domain will then send from your Primary address, or from no-reply@ezekia.com if there isn’t one. If your Compliance email is on the domain you are deleting, it will be removed as well, and the screen will warn you before this happens.


Video Guide

For a detailed explanation of the DKIM process, please watch this video.


Common DNS/Hosting Providers

Different DNS/hosting providers have their own specific instructions for adding DNS records. Below is a table with links to the documentation for some of the most common providers: 

 

Troubleshooting

Are you unsure of who hosts your website, or perhaps you need to implement DMARC? Please see this article for a detailed troubleshooting guide of the DKIM process.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article