• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue DKIM signature unverified

Netbela

New Pleskian
Server operating system version
Ubuntu 20.04.4 LTS
Plesk version and microupdate number
Version 18.0.44 Update #3
Hi all,

I am trying to setup DKIM on my Plesk server however if I use the mxtoolbox email deliverability tool to chekc compliance I keep getting the 'DKIM Authenticated' failed. Due to the lack of DKIM signature some of the emails I send end up in customers mail spam boxes.

The domains are hosted on the Plesk server so I do not use any external DNS servers. The DKIM records are automatically created on the domain and seem to be OK, I have tested this with multiple DKIM checker tools. The MX records of the domains point to mail.<domainName>. This MX Record points to an A-record that in turn points to the IP of the Plesk server. I am using Postfix as mailserver and am running Plesk Obsidian Web Pro edition (Version 18.0.44 Update #3). Has anyone else encountered these issues with DKIM before? Should I change the MX-records to point to 'mail.pleskserver.com'?

This is what is seen in the Plesk mail log browser:
9E7C53E740: DKIM verification (d=tdomain-name.nl, 1024-bit key) failed: signature verification failed


If you need me to provide any more details then please let me know.

Kind regards,

Tom
 
Related to this question, a mxtoolbox report can be found here:

I've just noticed this in the 'Authentication-Results':
Authentication-Results: ttwl.nl (amavisd-new); dkim=fail (1024-bit key)
reason="fail (bad RSA signature)" header.d=tinux-it.nl

Can it perhaps be that my amavis is not setup correctly or does something with the email body? If so, how do I correctly setup the anti-spam/anti-virus for Plesk mail server running postfix?
 
Back
Top