• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

DomainKeys

W

wsani

Guest
You have got to add DomainKey support to the next version of Plesk.
 
AMEN! I think a lot of us have said this, but I don't think anyone is listening, or gives a ****!
 
You're right, they don't give a **** but yet we're feeding this company our hard earned dollars...
 
How do you get the public key that needs to go in the DNS record to enable valid DomainKeys lookups?
 
Once you have everything upgraded, you can go to the domain > Mail > under Preferences there is an option to enable DomainKeys. Keep in mind that you have to first enable the feature under Server > Mail.
 
Yep I understand that.

But DomainKeys doesn't work properly unless you add a public key to your DNS record. Plesk isn't doing that so the status of your DomainKey will be marked as unknown and untrusted by most mailservers.

What we need to make this work properly is the public key (it should be the same for every domain on the server) and to attach the appropriate record to DNS.
 
Actually I see a _domainkey DNS entry has now been created by the server and it works.

Well done Parallels on finally implementing this :)
 
Back
Top