

Deliverability settings

For every domain that will be used as the from email address (noreply@company.com) for the Newsletter emails you need to complete the following steps to increase deliverability. If you plan to use company.se, company.no etc. you need to follow these steps for each domain. The examples below are based on company.com and need to be changed to the actual domain.

Set up sending domains

To be able to use the sending domain and verify that all settings are correct you need to add it as a sending domain in Newsletter administration. There you also need to verify domain ownership by adding a verification record. More info here. After the sending domain has been added you need to make three changes in your DNS. A TXT record to verify domain ownership, a CNAME record for DKIM and a TXT/SPF record. Instructions for this can be found when adding the sending domain. Below in is a brief explanation on what you can prepare.

Setup a domain verification record

This is done to verify that you are the owner of the domain. A TXT-record limeverify.(company.com) needs to be added with a unique code found on the sending domains administration page in Newsletter.

Setup a SPF record

A SPF record is a DNS setting made by the owner of the domain (company.com) which instructs receiving SMTP-servers which IPs that are allowed to send with company.com as the from email address. In the company.com DNS you need to add a SPF TXT record. If the company.com domain already has a SPF record you can extend that by adding:

"include:spf.bedrock.lime-technologies.com"

If you don’t have a SPF record you can create this standard SPF record which won’t disrupt other email services but include Newsletter services:

"v=spf1 a mx include:spf.bedrock.lime-technologies.com ~all"

To verify the settings you can use a service on MX Toolbox (change company.com to the actual domain).

Setup a DKIM record

With DKIM, Newsletter creates a digital signature based on the from information in the email with a private key stored on the newsletter servers. When the receiving SMTP-server receives a signed email from @company.com the SMTP-server can verify the signature by getting the public key from the company.com DNS. In the company.com DNS you need to create a CNAME record:

bedrock._domainkey(.company.com) CNAME dkim.bedrock.lime-technologies.com