LianaPress, instructions for IT support

  • Updated

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

The reason for messages ending up in spam is often the insufficient identification of the sending address and inconsistencies between the sender and the content (links) of the message.

In this guide, we will explain how you can take the necessary steps to ensure the delivery of your messages if you want to use your own address or domain as the sending address.


This validation determines which servers can use the specified domain as the sender address.


This is a digital signature that assists the receiving server in identifying the sender and indicates that the message has been sent from a reliable source.

DKIM authentication informs the receiving server that the LianaPress sending server is authorized to use the address as the sender. To ensure that press releases reach recipients as effectively as possible, it is recommended to add guidance to the sending domain's DNS records for DKIM and, if necessary, SPF, and to create a dedicated subdomain for subscription and unsubscribe pages. These actions enable consistency in both the second-level sending domains and envelope-sender throughout the message.

DKIM authentication is, naturally, only applied to the customer's own LianaPress account.


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 includes a built-in reporting mechanism that generates XML-formatted reports on both passed and failed messages. DMARC ensures that the sender's domain in the message matches the domain used in SPF and DKIM validations, so both DKIM and SPF configurations must be in order when implementing DMARC.

How to proceed if you want to use your own address, your own domain as the sender address:

For these purposes, we would like you to make the following additions to the DNS records of the domain (



Envelope Sender IN CNAME


_dmarc IN TXT v=DMARC1; p=none;


The record is added to the DNS records of the domain ( If the domain does not already have a DMARC record, it is advisable to start with the setting p=none, where p stands for DMARC policy and indicates what action should be taken if DMARC conditions are not met (DMARC = FAIL).

Once it has been verified that everything is working correctly and the necessary SPF and DKIM information is available for all applications used for sending, p=none should be changed to p=quarantine or p=reject. This ensures that messages are delivered even to users of Microsoft's email services.

After you have added these DNS records (taking into account any necessary internal and external network considerations), we would appreciate it if you could inform our support services, so that we can finalize the settings.



In press releases, the sender address is set as, and the default URL for subscription and unsubscribe pages is In this case, the message's envelope-sender is, and the links in the message also refer to that address. Therefore, the receiving server may detect inconsistencies between the sender and the message, potentially preventing the message from being delivered altogether or directing it to the recipient's spam folder.

If the sender is and the subscription page URL is, for example,, then the envelope-sender would be In this case, the links in the message also start with the same URL, increasing the likelihood that the message will be successfully delivered to the recipients.

Was this article helpful?

0 out of 0 found this helpful



Article is closed for comments.