Feature Suggestions
Please provide here your suggestion for new functionality for Plesk. We encourage you to review and vote for suggestions of others. The top-ranked suggestions are likely to be included in the next versions of Plesk.
Please write in English so that voters from all over the world can read and support your request.
Off-topic posts will be removed from here
6 results found
-
Manage greylist from Plesk CP
Allow management of greylist filters and configuration from the Plesk control panel instead of only from command line as is currently the case.
207 votes -
More control of DKIM
We could really do with more control of DKIM, for example...
Ability to control key length 1024Bit or 2048Bit (server wide)
Enable subdomain signing, while you can't create email accounts for subdomains in Plesk, it's often the case that the server is named as a subdomain eg: mail.example.com Which means unsigned mail leaving the server (cron etc) even when example.com is hosted.
The standard OpenDKIM package allows you to add it to nonsmtpdmilters so sendmail mail gets signed.
Ability to change the selector.
We really can't have mail leaving servers not being signed...it defeats the whole point in…
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
-
disable automatic greylisting activation for new domains
If i add a new domain in a subscription, greylisting is automaticly activated, just because it's enabled on the server.
It would be much better if customers have to activate greylisting manually in their settings, like the spamfilter.
A workaround with Event Manager is possible but a bit inconvenient.
39 votesThank you for your input! We will consider this functionality in upcoming releases.
We have created internal document with ID PPM-569 for your reference.
Everyone, please continue voting for this feature if you consider it important.
—
ET -
Create only mail accounts when mail is actually enabled, instead of on domain creation
As soon as any account is created in Plesk, a mail account is setup in Smartermail, used for managing the mail domain. This is one of the few minor issues for those using Plesk in a load balanced solution (which is actually remarkably possible!). It is also tricky for those running a limited smartermail license (e.g. 250 accounts, many of which are now unwanted Plesk management accounts).
It should not be so difficult to setup the mail account only when mail is enabled on a domain, and have Plesk just leave the mail server alone for domains that do not…
34 votes -
Custom Email Server Help Tips
The settings for mail servers have a help tip in the email addresses management page, and in the users' Plesk Account pages.
If a Plesk server is set up strictly as a mail server, and has DNS handled remotely, the settings in the Help Tips can be incorrect.
Currently the tips only show the server as the root domain even if the mail server's actual DNS points (as an example) mail.domain.tld to the server, requiring the settings to include the subdomain.
If I add the domain as "subdomain.domain.tld" in settings, then the server tips are correct but the email addresses…
14 votesHi,
We’re looking into adding this functionality in one of the upcoming releases.
—AK
-
Enable mail accounts password encryption(or have possibility to enable it via Plesk) for MailEnable
Currently all mailbox passwords(MailEnable) are stored in AUTH.TAB in plain text that is not secure.
MailEnable has an option to enable password encryption in AUTH.TAB13 votesThank you for report. We are going to implement this feature in Plesk Obsidian soon.
—
IG
- Don't see your idea?