If a warning message "DKIM issue - Sender email address domain differs from the subscription site domain" appears during newsletter sending, the cause is usually that the sending domain does not match the domain used on the subscription and unsubscribe pages.
Why does this error occur?
LianaMailer checks that the sender email address domain and the domain used on the subscription and unsubscribe pages match each other.
If the domains do not match, the system displays a DKIM warning. This reduces the reliability and deliverability of messages, which is why the system blocks sending in this situation.
How to check the settings
1. Check the subscription and unsubscribe page domain
Open the Settings tab during the message sending process.
Make sure that the domain defined under the site settings is the same as the sender email address domain.
Example:
Sender: newsletter@company.com
Site domain: newsletter.company.com
Both must match.
2. Check DNS settings
If the domains are correct but the error still appears, check the domain’s DNS settings.
Go to: LianaMailer → Settings → Domain settings
From there you can verify:
Whether DKIM records are correctly configured
Whether all required DNS records exist
Whether the domain is verified for sending
Missing DNS records will be shown in the interface.
Missing or incorrect DNS records may prevent DKIM authentication from working properly.
You can copy the missing DNS records and send them to your company’s IT support or domain administrator to be added.
Once the records have been added, we recommend contacting our technical support at support@lianatech.com. We will verify the configuration and finalize it if needed.
Summary
A DKIM warning usually occurs when the sender domain and the subscription/unsubscribe page domain do not match.
When the domains are the same and DNS records are correctly configured, sending will work normally and DKIM authentication will succeed.
If you have any questions, you can contact our technical support at support@lianatech.com.
Comments
0 comments
Article is closed for comments.