de en


Administration: DKIM and sender domains

When you send your newsletters, DKIM protects against phishing and spoofing and helps to avoid classification as SPAM. Thanks to the DKIM signature, the receiving mail server can check whether your newsletter remained unchanged on its way and actually comes from the specified sender domain.

Only two steps are required:

Then use the sender domain: in the basic settings of your emails, select the sender domain you want.

In addition, emma offers the following options:

 

Brief explanation of terms

To begin with, here is a brief explanation of some terms.

  • Sender domain: In a sender address such as 'info@newsletter.example.com', the part after the '@' is the sender domain, in this example 'newsletter.example.com'. This domain is DKIM-signed so that the sender address is considered authentic. For this, you need to create the matching sender domain for each sender address you use.
  • DKIM: "DomainKeys Identified Mail" is a method that checks the authenticity of the domain of the email sender address. It ensures that the content of the email has not been changed or falsified by a third party and that the sender is authentic. For this purpose, the email header is given a tamper-proof DKIM signature, which the receiving server checks against the DNS entry of this domain. Only the domain owner can set this DNS entry. This authentication prevents sender addresses from being forged to send phishing or spam emails and deceive recipients.
  • SPF: "Sender Policy Framework" determines whether the sending IP is authorized to send the email. For this, the SPF record lists all servers that are authorized to send. Sending via unauthorized mail servers is prevented.
  • MX: The "Mail Exchange" record consists of two values: (1) the domain name of the mail server responsible for the sender domain and (2) the priority of use if several mail servers are specified. 

Why is DKIM so important?

To achieve the best possible delivery rate for your mailings, we are committed, as a member of the CSA (Certified Senders Alliance), to sending only DKIM-signed newsletters.

There are very good reasons for this obligation, and you benefit from them directly:

  • Your recipients' mailbox provider recognizes that the newsletter is genuine. This authenticates you as a reputable sender and gives you a higher sender reputation.
  • The SPAM check does not wrongly classify your newsletters as phishing or mail spoofing. Your open rates remain stable in the future.
  • The SPAM checks of major email services such as Gmail or GMX require a DKIM signature that matches your organization. The emma DKIM signature, which used to be sufficient, cannot meet this criterion because it does not match your sender address.

For these reasons, all your sender domains must have a valid DKIM entry. The following sections describe step by step how this works.

Overview of sender domains

In the menu 'Administration -> DKIM and sender domains', the account administrator finds the overview of the configured sender domains. The overview offers the following information and actions:

  • 'Default' column: The sender domain selected as default is marked with an icon (for its meaning, see the next section).
  • Columns 'DKIM', 'SPF' and 'MX': A green ✓ indicates that the domain has been set up correctly and can be used for sending. A red ✘ indicates that the domain has not yet been configured correctly. It usually takes 24 hours after the DNS entry has been stored before the validation succeeds.
  • 'Forwarding' column: Shows the selected forwarding of the sender domain, which you set when creating or editing a domain. If the column is empty, the option 'No forwarding' was selected. A red ✘ indicates that the forwarding is not yet active on our mail server, because a successful DNS check is required first. The system checks regularly whether the DNS entry of the sender domain has become valid. Once it has, the column shows a green ✓, indicating that the forwarding is active. The advantage is that you can select the forwarding when you create the sender domain and do not have to edit it later, while the forwarding only takes effect once the DNS entry is valid.
  • Action 'DNS entry': Shows the DNS entries (DKIM, SPF, MX) that you need to store with your web host.
  • 'Edit' action: Existing sender domains can be edited later.
  • 'Delete' action: Sender domains can be deleted. Before deleting, there is no check whether the domain is in use. Please check yourself whether the domain should really be deleted.

Creating a new sender domain

To create a sender domain, click 'New sender domain'. The required entries are:

  • Sender domain: Enter the URL of the sender domain. Once created, the URL of the sender domain cannot be changed.
  • Default domain: The selected default sender domain is automatically preselected (after successful DNS configuration) in every newly created email and in every email shared across accounts.

There are also the following settings for the DKIM configuration:

  • Selector: A DKIM selector is a freely selectable identifier that almost all web hosts require. It must be unique within the domain and must not contain special characters or umlauts. Using different DKIM selectors, you can use different DKIM signatures for different purposes within one domain. Once created, the selector cannot be changed. It is also a mandatory field.
  • Key size: The key size can be 1024 bits or 2048 bits. We recommend 2048 bits because it offers more security. For domain providers that only allow shorter DKIM keys, 1024 bits are suitable. Once the sender domain has been created, the key size cannot be changed.
  • Email forwarding: To receive replies from your newsletter recipients, you must set up forwarding to your mailbox. Choose from the following options:
    • No forwarding: Replies are not forwarded, i.e. they are lost. Not recommended!
    • Forwarding to parent domain: If, for example, the sender address info@subdomain.example.com is set in the mailing, replies are forwarded to info@example.com. Please make sure that this mailbox exists.
    • Forwarding to individual address: Replies are forwarded to the address you enter. Please make sure that this mailbox exists.

After saving, you will find the new sender domain together with the automatically generated DNS entry in the overview.

Editing a sender domain

For an existing sender domain, you can change the following settings later:

  • Default domain: If you set a new default domain, the previous default domain automatically loses this status.
  • Email forwarding: You can change the forwarding target at any time.

All other settings cannot be changed later. Of course, you can delete an outdated sender domain at any time and start the whole process again, i.e. create the new domain you want and store its DKIM setting on your web server (see next section).

Copying the settings into the DNS entry of your domain

Click the gear icon in the actions to open the DNS entry. It contains the DKIM entry, the SPF1.0 entry and the MX entry. These entries are needed to authenticate the domain. You store them with your website provider. Since this procedure differs from provider to provider, there are no general instructions. If you have questions, it is best to contact your website administrator or your provider. However, the necessary steps are usually similar:

  • Log in to your website provider or domain hosting platform and open the administration area. Many providers have a menu called 'Domain management' or something similar.
  • Look for the DNS settings.
  • Follow the instructions and store the DKIM entry in the right place.
  • To avoid unnecessary error messages, please specify a priority for the MX entry.
  • Also make sure to set the SPF entry. If an SPF entry already exists, extend it.

The 'DNS check' column shows whether the entries have been stored correctly. '✓' means that the entry of the domain is valid and the domain can be used for sending. '✘', on the other hand, indicates that the configuration has not yet been completed successfully. Please note: It can take up to 24 hours until the DNS settings have taken effect at your web host.

Sender domains in multi-account systems: Sharing across accounts

Since March 6, 2023, as the owner of a multi-account system with several subaccounts that use the same sender domain, you can share this sender domain with selected subaccounts from the admin account. After sharing, the sender domain is listed in the overview of these accounts and can be selected for sending when editing an email, but it cannot be edited or deleted there.

To share a sender domain, follow these steps:

  • Step 1: In the admin account, open the 'DKIM and sender domains' overview and edit the sender domain you want to share. Use the bottom option 'Share sender domain with subaccounts' to share it.
  • Step 2: Click 'Select accounts' to open the account overview. The left side lists all subaccounts of the multi-account system, while the right side shows the subaccounts the sender domain has been shared with. Clicking a subaccount moves it to the right side and shares the sender domain with it. Once you confirm the changes with 'Save', you return to the window for editing the sender domain, where all subaccounts the sender domain has been shared with are listed above the button.

Sending emails: Using the sender domain

Once a sender domain has been set up in the account, it can be used for all future sends. To do so, open or create an email and go to the 'Basic settings' tab. There you see two fields that make up the sender address:

  • Local part: Enter the part of the sender address before the @. For example, if the address is 'localpart@senderdomain.com', enter 'localpart' here. 
  • Sender domain: The drop-down list contains all sender domains that have been created. The default sender domain is preselected. Select the sender domain you want to complete the sender address.

Then prepare everything else for sending, and check once more in the test send or in the send window that the sender address is set correctly.

If the account contains emails with a sender address that were created before a sender domain was set up, the system checks when you open such an email whether its sender address matches a sender domain created later. There are two possible outcomes:

  • The sender domain in the email matches the sender domain created later: The system automatically recognizes that the sender domain exists, and the drop-down list is displayed. You do not need to change anything manually.
  • The sender domain in the email does not match any sender domain created later: You see the old interface with the 'Sender address' input field and a notice. Nothing is changed automatically. Recommended steps: (1) Enter a sender domain that already exists in the account. When you save, the system checks again whether the sender domain exists and then switches to the drop-down list automatically. (2) Create the missing sender domain and open the email again. The check will find that the sender domain exists, and the drop-down list is displayed.

Please note that all sender domains of your account can be selected, even if they do not (yet) have a valid DKIM entry. Before sending, please check that a sender domain with a valid DKIM entry is used.

Replacing outdated sender addresses in existing mailings

Suppose you have recently set up the sender domain news.example.com, with the previously unused subdomain news. Now you want to replace the previous sender address info@example.com with info@news.example.com so that your current and future mailings use a DKIM-signed sender.

In these three use cases, emma supports you:

Case 1: Replacing the sender in activated campaign and dialog mailings, email setups and email drafts

In the overview of your sender domains, you will find the "Replace sender addresses in emails" button at the top right. It starts a search & replace tool that first searches the sender addresses of all active campaign and dialog mailings, email setups and email drafts.

The "Non-matching domain" column shows the domains of all sender addresses that do not match any of your configured sender domains. These senders should be replaced so that future sends use one of your DKIM-signed sender domains.

For each non-matching domain, select the replacement you want. The option "Do not replace" is preselected. You can choose to replace only one sender domain at first or several at once.

Once you have selected all the replacements you want, click the "Replace now irrevocably" button. The replacement cannot be undone. You can of course change the sender address of individual mailings manually at any time (provided that the sender domain you want has been created beforehand).

IMPORTANT: Personalized sender addresses and placeholders

Also, sender addresses personalized with placeholders can be replaced. Please note the following:

  • Not critical: If only the local part before the @ is personalized, as in the example [Personalized_name /]@example.com, the domain example.com is offered for replacement. The personalization of the local part is kept.
  • Possibly critical: If the part after the @ is personalized, as in the example john_doe@[Personalized_domain /], the placeholder [Personalized_domain /] is offered for replacement. After this replacement, the sender domain is no longer personalized. A replacement is not necessary if the source data (subscriber fields, personalization helpers, account constants) uses your current sender domains.
  • Possibly critical: If the complete sender address consists of a placeholder, as in the example [Personalized_address /], the placeholder [Personalized_address /] is offered for replacement. The result of this replacement is a mix of the two previous examples. Afterwards, the sender domain is no longer personalized. However, the personalization of the local part is kept, because [LOCAL-PART][Personalized_address /][/LOCAL-PART] is inserted, i.e. the local part is still extracted from the placeholder at the moment of sending.

Case 2: Automatically replacing the sender when copying emails

If the sender address of the source mailing does not use any of your current sender domains, the copied mailing automatically gets the default sender domain. An info message shows the change so that you can (and should) check the new sender. This also applies when copying an archived mailing.

You can of course change the sender address of the copy manually afterwards (provided that the sender domain you want has been created beforehand).

Placeholder-personalized sender addresses are replaced as described above in case 1. After the replacement, the domain of a sender address can no longer be personalized.

Case 3: Creating emails from an email setup

The behavior is the same as in Case 2: Automatically replacing the sender when copying emails.

 

Tags: