Authenticating your domain(s)

Authentication gives the receiving party more assurance about the sender and the content of an email, and therefore more reason to trust the email. This is good for the deliverability of your newsletters.

Does your domain use DMARC? Then authentication is required, because many of your newsletters will be refused otherwise. You will automatically get a notification from within our application (in Step 1, 5 and 6 when creating a campaign).

What do I have to set up?

Under Settings > Authentication you will find your domain(s) and, per domain, two lines that must be added to DNS. You can do this yourself, if you have access to the settings of the domain. Otherwise you can send the lines to your web builder or IT department.

[screenshot]

Don't forget to activate

When the DNS records have been added, you still have to indicate this to Laposta. You can do that by pressing the 'Active' button (under Settings > Authentication).

[screenshot]

You can also find all necessary actions in our step-by-step authentication manual.

Technical background

We automatically authenticate every newsletter sent through our system with DKIM and SPF (see links below for more explanation). 

Because the newsletters are sent through our system, the authentication concerns our servers. It is useful to set this up further, so that emails do not appear to come from our servers. In that case, we alter the Return-Path to your domain. The DKIM signature then refers to your own domain.