• 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 315 duplicate DKIM Signatures in one Email Header

When is plesk 17.8 planned to be released?
Until now this bug is only fixed in the upcoming new version (17.8), but not in the current stable (17.5). Right?
What about backporting the fix to the 17.5 branch?
 
Same issue here on Plesk 17.5.3.
When will it be fixed?
Backporting this bugfix to 17.5 is quite complex and looks too risky for Plesk mailservers already working in the production. There is serious mailhandlers refactoring.
 
Backporting this bugfix to 17.5 is quite complex and looks too risky for Plesk mailservers already working in the production. There is serious mailhandlers refactoring.

Right now this makes Plesk unusable if you want to send out an e-mail to larger groups of people: Many mail servers refuse e-mails where the header exceeds a specific size or if it contains too many DKIM signatures. We experienced this with e-mails e.g. to 70 or 1000 recipients (using mailman Issue - Multiple DKIM-Signatures per Mail (when using mailman) and sending individual e-mails)... Disabling DKIM is not an option! Thus, it is required that this will be fixed for the productive Plesk versions (e.g., 17.5) ASAP!
 
Right now this makes Plesk unusable if you want to send out an e-mail to larger groups of people: Many mail servers refuse e-mails where the header exceeds a specific size or if it contains too many DKIM signatures. We experienced this with e-mails e.g. to 70 or 1000 recipients (using mailman Issue - Multiple DKIM-Signatures per Mail (when using mailman) and sending individual e-mails)... Disabling DKIM is not an option! Thus, it is required that this will be fixed for the productive Plesk versions (e.g., 17.5) ASAP!
Hey @B_P I clearly understand your problem, this DKIM Issue does exist for more than two years now. I have switched DKIM ON on domains only where I know they will not send mails to many addresses, this is not a solution of course. Plesk 17.8 will be released around March 2018 as far as I know therefore I think they will not fix it in Plesk 17.8 I think the only solution you have is switching to Plesk 17.8 Preview 9 as soon as possible, because it should be fixed there.
 
Is there now a scheduled date for the release of 17.8 available?
I'm now waiting for more than one year to get a bug fixed by plesk.

To get me right: We're talking about a bug within the implementation of a security function, not a new feature. For more than a year now. What do you do with a technical device which does not work as expected? You bring it back to the dealer. Or get some money because of malfunction. I'll try this now.
 
I just upgraded to the early adopters version 17.8.11 Update 1.
For me this issues is still not fixed. Sending an eMail to multiple receipients still results in as many DKIM signatures as are receipients in the eMail. Such emails are not accepted by major mail providers.

As @IgorG pointed out, a backport to 17.5 was rated as too risky. Now that it is not fixed in 17.8, will there be any chance to get this issue fixed in this release?
 
Interesting - that article was just updated.... I swear when I read it it sounded like it was resolved already....
 
I can also confirm this bug is still present after upgrade today to Plesk Onyx 17.8.11 Update #5 on CentOS 6.9.

Very disappointing since we have been waiting for fix promised with this Plesk update.

E-mail messages with too many repeated DKIM signatures are rejected by many recipient mail servers, so this effectively prevents use of DKIM by Plesk mail servers, especially on dmains using Mailman ro other mailing list servers.
 
Guys, if you see this problem on your new Plesk Onyx 17.8, I advise you to contact support for more detailed investigation directly on your server.
 
Back
Top