Facebook
Twitter
W
wsani
Guest
You have got to add DomainKey support to the next version of Plesk.
-
Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
To get into the festive spirit, install the Skins extension. -
The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
-
The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
-
The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.
G
gshelton
Guest
AMEN! I think a lot of us have said this, but I don't think anyone is listening, or gives a ****!
W
wsani
Guest
You're right, they don't give a **** but yet we're feeding this company our hard earned dollars...
W
wsani
Guest
8.4? Is it out already?
yes, it was released today I beleive.
J
joeybutterface
Guest
How do you get the public key that needs to go in the DNS record to enable valid DomainKeys lookups?
W
wsani
Guest
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.
J
joeybutterface
Guest
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.
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.
J
joeybutterface
Guest
Actually I see a _domainkey DNS entry has now been created by the server and it works.
Well done Parallels on finally implementing this
Well done Parallels on finally implementing this
Similar threads
