• 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 Validation Errors

Zach

New Pleskian
Has anyone else been having issues with DKIM validation recently ? I believe it cropped up for us around the time of our 17.5 to 17.8 upgrade... I've already verified that the keys as seen in the Plesk DNS manager are propagated / have tried switching DKIM signing off and back on for the domains with issues. Several different DKIM errrors depending on the mail recipient's provider / sending domain. Historical DMARC reports seem to indicate no DKIM coverage issues previously


Error Type One:

X-ZohoMail-DKIM: fail (identity @************.com: invalid key for signature: Syntax error (duplicate tag): p)


Error Type Two:

X-ZohoMail-DKIM: fail (Header signature does not verify)

Error Type Three:

dkim=neutral (bad format) header.i=@****************.com header.s=default header.b=I2uPoVhb;


Does anyone have any advice for any further configs or options to check ? Currently have DKIM disabled for the affected domains as there was an increase in being marked as spam...


OS: OS‪CloudLinux 7.4 (Georgy Grechko)‬ProductPlesk Onyx
Plesk: Version 17.8.11 Update #7, last updated on May 10, 2018 03:47 AM
MTA: Postfix


As far as my memory serves there have been no changes to the Plesk config on this server other then the changes described in the KB article titled Outlook fails to send an email: SASL authentication failure
 
Bump - Sorry if this breaks forum rules - Cant seem to submit an actual support ticket due to having a Plesk licences from OVH - if nobody has any ideas I guess I will just go purchase another license to submit a ticket lol
 
Has anyone else been having issues with DKIM validation recently...
We're on a different server setup than you (and are still on Plesk 17.5.3 not 17.8.19) We have no OVH involvment and we were trying to solve a different challenge, so had a different set of DKIM challenges than you're having when we posted things, but... you may find THIS earlier thread could possibly be helpful, as some of the validation errors appear common and they can be fixed.
 
Cant seem to submit an actual support ticket due to having a Plesk licences from OVH
Even with a license from OVH you may be able to purchase the Plesk support subscription to get Plesk support directly, so they can investigate for you the issue: How to get technical support for Plesk? & How to get support directly from Plesk?

Take into consider to check your DKIM record here > Check a DKIM Core Key or DKIM, SPF, and Spam Assassin Validator - dkimvalidator.com or DomainKeys Identified Mail (DKIM) Record Lookup - DKIM Check - MxToolBox and share the result
 
Last edited:
Back
Top