Instructions for IT support

  • Updated

DKIM, SPF, and DMARC are email protection mechanisms that ensure your messages reach the recipient's mailbox.

The reason for email not be delivered to inbox, usually the sending address is not being identified and discrepancies between the sender and message content (links).

In these instructions, we inform you how to perform the needed actions to ensure the delivery of your newsletters.


DKIM verification and SPF validator inform the receiving server that LianaMailer's sending server has the authorization to use the @customer's address as the sender. In order for newsletters to reach the receiver as well as possible, forwarding for DKIM and, if necessary, SPF validators should be added to the DNS information of the sending domain. Also, a separate subdomain should be created for the subscription/unsubscription page. Taking these measures ensures that in the message both the second level sending domains and envelope sender are the same throughout.

DKIM verification is naturally only set to the customer's own LianaMailer account.

Example: address is used as the sender of a newsletter and the subscription page uses LianaMailer's default address "". Therefore, the message's envelope-sender is, and also the links in the newsletter refer to this same address. In this case, the receiving server sees inconsistencies with the sender and the message and this might result in the message not being delivered at all or being directed to the recipient's spam folder.

However, if the sender is and the subscription page address "", then also envelope-sender is Message links then also start with the same URL, and the message is more likely delivered to the recipients.


SPF (Sender Policy Framework) validator informs the receiving server that the sending server has the authorization to use the sender address for sending. Liana's support team checks the need for SPF upon request and provides the right SPF validator. 


DMARC is an authentication protocol that defines how email sent on behalf of a specific domain should be handled and which authentication methods the sent message must pass. DMARC also includes a built-in reporting mechanism that can generate XML-formatted reports on passed and rejected messages. DMARC verifies that the sender's domain of the message matches the domain used in SPF and DKIM validations, so DKIM and SPF settings must also be in order when DMARC is implemented.

Follow these instructions to ensure the delivery of your newsletters

  1. Open Settings -> Domain Settings
  2. Check which domains are in use and if they are marked as confirmed.
  3. If they are, you can go directly to step 5.
  4. If not, click on the domain you are using for transmission and select "Copy Proposed DNS Values."
  5. Then check your subscription page's address in Settings -> Sites. If you find the address of the domain you are using, which works in the browser, the settings are correct, and you can stop following the instructions here.
  6. If the address is, for example, in the form of or, please contact our technical support. You will receive a record from them that you can provide to the domain administrator.
  7. Ask your domain administrator to add these records to DNS management in steps 4. and 6. of the guide and inform when the additions are made. Support will finalize the settings.

Was this article helpful?

0 out of 1 found this helpful



Article is closed for comments.