Frank
My feedback
41 results found
-
5 votesFrank supported this idea ·
-
6 votesFrank supported this idea ·
-
425 votes
This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.
The original request contains a manual solution, so, we consider to automate it. Please, add a comment if your case will not be solved with that solution.
Thanks in advance!
— rk
Frank supported this idea ·An error occurred while saving the comment -
404 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
Frank supported this idea · -
454 votesFrank supported this idea ·
-
430 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IGFrank supported this idea · -
94 votes
"1. Ability to control [DKIM] key length 1024Bit or 2048Bit (server wide)"
is available since Plesk 18.0.55, published August 29th, 2023
https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18055
"4. Ability to change the [DKIM] selector"
is available since Plesk 18.0.56, published Ocotber 10th, 2023
https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18056
Stay in the loop for more to come.
-- PD
Frank supported this idea · -
27 votes
One good reason why it is important to use own DKIM key is that for sending mail from different servers that service the same domain (e.g. during a migration) the key on the target needs to be the same as on the source.
We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
-- PD
Frank supported this idea · -
201 votes
Thank you for your input! We are planning to implement this functionality in upcoming releases. The request is registered as: PPM-2517
Everyone, please continue voting for this feature if you consider it important.
— ES
Frank supported this idea · -
230 votesFrank supported this idea ·
-
233 votesFrank supported this idea ·
-
286 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— IB
Frank supported this idea · -
549 votesFrank supported this idea ·
-
208 votesFrank supported this idea ·
-
78 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— rk
Frank supported this idea · -
93 votes
Thank you for your input. We will consider this functionality in upcoming releases, if it will be popular.
Everyone, please continue voting for this feature if you consider it important.- SU
Frank supported this idea · -
45 votes
Thank you for your input, we will consider this functionality in upcoming Plesk releases.
—AK
Frank supported this idea · -
70 votes
This is a valid request, so we’ll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features. Thanks in advance!
— rk
Frank supported this idea · -
31 votesFrank supported this idea ·
-
34 votesFrank supported this idea ·
In my case not only me as admin want SFTP for all users/connections, also clients want this. This security is important. Please, Plesk, do something.