DKIM - DomainKeys Identified Mail

DomainKeys Identified Mail (DKIM) is an authentication method, which uses email encryption with public/ private keys, to validate whether the emails are generated from the authorized servers, recognized and configured by the administrators of the sending domains. This authentication method enables secure email communication and prevents spam.

Why configure DKIM?

Spammers often send out emails that claim to be from authentic email senders. These emails are mostly sent with the intent to make the recipients view the email, or sometimes to collect sensitive information (passwords, email addresses etc.) from the recipients under the pretext of being a legitimate sender. Two methods that are commonly used by spammers include email spoofing and backscattering. 

Email Spoofing:

Email spoofing is a cheating method used by spammers to make emails appear to be sent from a legitimate domain/ email address, that does not belong to them. This is done by forging the email headers, to make it seem legit so that the recipients trust and open the emails.

Spammers follow this approach as it makes more people view the email since the sender appears to be authentic. But, sometimes, it may pose serious consequences if they try to retrieve sensitive information from the user. Spoofed emails can be detected and avoided by configuring SPF and DKIM. If DKIM is configured, the domain name identity associated with each message is validated. 

If this DKIM validation fails, such emails are quarantined or rejected based on the conditions set by you when DKIM validation fails.

Email Backscattering:

Spammers spoof a domain name and send emails using the tampered email address. If the recipient domain rejects the email, it will send bounce messages to the domain that was spoofed. Such bounce messages which a user receives for emails that they never sent are called Email Backscatter.

Consider a case where a spammer has spoofed your email address and sent spam emails to another domain. When these spam emails are sent to invalid email addresses, the recipient domain sends a bounce message to the spoofed domain. This bounce message, instead of being sent to the spammer will be sent to the spoofed domain from which the user is claiming to send the email. The spoofed domain will also be blocked by the recipient domain. If DKIM is configured, the authenticity of your domain can be validated and your domain blocking can be avoided. In case you're on the receiving end of these spam emails, DKIM can help detect the authenticity of the emails, and those emails that are not genuine will not be delivered to your mailbox.

Email spoofing and backscattering, two methods that are commonly used by spammers, can be prevented to a certain extent by configuring SPF and DKIM for your domain.

​How DKIM Works

In the DKIM process, a public key is published as a TXT record for the domain's DNS Manager(registrar of the domain or DNS Provider). Every outgoing email includes a unique signature generated using the private key for the particular domain. The receiving email server uses this private-public key combination to validate the email source. If there is a validation failure, the recipient server may reject the email or classify it as Spam/ Forged email, based on the server behavior.

Enabling and using DKIM for your domain, ensures that valid emails sent using NICeMail, are not classified as Spam at the recipient end.

​DKIM Selector

The selector is used to identify the public DKIM Key details of the Domain. It is an attribute for the DKIM Signature and is included in the DKIM header of the email. You can use multiple selectors for a single domain in cases where you need to provide Special Signatory Controls for different sets of users.

Once you have added a selector and verified the selector, you need to make it as default and enable it for the domain. Once enabled, all the outgoing emails based on the domain will be signed by the default selector, unless the users have been associated with a different selector in the Users section.

Steps to add DKIM Signature for your Domain:

You can enable DKIM for your domain from NICeMail Admin Console, after creating the required text record in your domain's DNS manager. The DKIM configuration has three major steps:

1. Generate unique public DKIM Key-value using a default selector in NICeMail.
2. Create a TXT record in your Domain's DNS Manager (Domain registrar/ DNS Provider).
3. Validate the selector and Enable DKIM in NICeMail.

I.Generate Unique Domain Key in NICeMail:

1. Login to https://mailadmin.mgovcloud.in.
2. Go to Domains from the left menu, and choose the domain for which you want to configure DKIM.
3. In the Email Configuration tab, select DKIM
4. Click on Add to add a new selector for the domain.
5. Provide the selector name, for the domain to be used with NICeMail.
6. Click Add. The selector will be added and a TXT record will be generated and displayed across the added selector.
7. You can copy the text in the TXT value field.
8. You need to create a TXT record with this value in the DNS Manager before you click Verify.

II. Creating TXT Record in DNS Manager.

1. Login to the domain's DNS Manager where your domain's name server is pointed.
2. Create a TXT record in your DNS with the title as <selector>._domainkey.<yourdomainname.com>
3. In the TXT record value, paste the entire content you copied from the text field TXT Record Value in NICeMail.
4. Save the TXT record in the DNS Manager.
5. You can check the validity of the DKIM using a DKIM checker.

Steps to add TXT record in GoDaddy domain manager:

1. Log in to your GoDaddy DNS Manager. Select the My Account menu and choose Domains.
2. Expand Domains and click the Manage DNS button for the domain you want to verify.
3. The DNS Manager page will open with information about existing DNS records.
4. Scroll down to the Records section and click the Add button to add a DNS record.
5. Select TXT from the Record Type drop-down menu.
6. In the Host field, enter <selector>._domainkey
7. In the TXT Value field, enter the TXT Record value generated in your NICeMail Admin Console.
8. Click Finish.

III. Enabling DKIM for the domain

1. If the Validation of the DKIM is successful on the third-party site, log in to https://mailadmin.mgovcloud.in.
2. Click Verify across the particular selector. The text record will be modified to the verified state.
3. Once verified, you will see a prompt to Enable DKIM immediately or later. You can enable DKIM immediately to start signing DKIM signatures for the emails from your domain.
4. Once you enable, the DKIM signatures will be added to all the emails generated from the domain. 

Multiple DKIM Selectors:

You can use multiple selectors for a single domain to provide separate DKIM signatures for multiple offices in different locations or provide separate DKIM signatures for a set of accounts. 

Example:

• ukoffice._domainkey.zylker.com
• usoffice._domainkey.zylker.com
• hrteam._domainkey.zylker.com
• marketing._domainkey.zylker.com

You can add more selectors for specific DKIM keys for different sets of users or for different locations of offices.

User-based Domain Selectors:

When you have multiple selectors, you can associate the different sets of users with the selectors based on your requirements. The default selector is automatically applied for all users and hence it will not be listed in the drop-down.

Once you add an additional selector, you can associate for a specific set of users from the User List section. 

Troubleshoot SPF/ DKIM Problems

Longer TTL

TTL (Time To Live) is the time specified in your DNS for each change in your DNS to be effective. If you have a huge TTL value (24 hrs/ 48 hrs), then the TXT/ SPF Records might take a while to get propagated. It might take up to 12 - 24 hours for DNS changes to take effect, based on the TTL set.

Incorrect Values

The way the SPF records need to be added often varies with different DNS Providers.  Hence it is recommended to check the help pages or instruction manuals of your registrar or reach out to the support team of your DNS provider, to add the respective SPF/ DKIM records.

Typos/ Spelling Mistakes

Check if you have copy-pasted the correct information from NICeMail Setup pages. In the case of DKIM, you need to copy the entire key displayed and provide it as a value of the TXT Record. The TXT Record name should follow the suggested naming conventions