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
5 results found
-
Allowing additional email addresses for mailuser
This would allow mail users to perform a password reset on their own. Currently this is not possible, because the email with the reset link would be sent to the own address. (To which the users usually have no more access without a password)
For reasons of data protection, it would make sense that the email passwords can be reset independently and not by the provider.
2 votesFor each mailbox an external-to-domain mail address can be stored to which a password reset mails will be sent should the "forgot password" link be used by the mailbox user. This additional address can be configured on the mailbox configuration page.
-- PD
-
do not use the external email address of the user as the sender of Let`s Encrypt renewal notifications.
Appearantly Plesk is using the Administrators EXTERNAL email address whenever sending Let's Encrypt renewal notifications to the certificate "owners".
Since its not uncommon that a Plesk server is NOT an authenticated sender for an EXTERNAL email domain these messages tend to end up in the spam folder of the receipient if accepted by their email server (which might be external too) at all.
I'd like my Plesk Installtion to use the admins/users standard email address as the sender address instead, chances are that the server is indeed an authenticated sender for those email adresses.
1 votePlesk uses the email address for certificates that is set in the email address input line on the dialog where you can issue a certificate. The user can freely choose which email address is entered.
-- PD
-
to allow an alias to be associated to more than one email account.
It's an useful (and optimal) way to associate more than one organisation account to an external (public official) email alias.
EG
internal account 1: john@myorg.net
internal account 2: mary@myorg.net
internal account 3: jules@myorg.net
public account (showed in websites, company papers, etc.): sales@myorg.net (this is the alias, not an real email account).
If John and Jules are the sales officers, it would be useful to link the alias to both accounts.
Note: It cannot be implemented using forwarding in a clean way.
Because the mail engine forwards the mails to John and Jules but the headers are tricky: the local account…1 voteWhen forwarding mails through a forwarding list, the sender remains unchanged. Replies to a forwarded mail are not sent to the forwarder, but to the original sender. Also, there is such feature like ambiguous aliases in mail servers like Postfix. The current solution of using forwarding lists is the correct technical approach.
-- PD
-
Notification "WordPress site vulnerabilities found" should be sent ro customer by default
Notification "WordPress site vulnerabilities found" should be sent to customer by default. Since customers are the ones who deploy their WordPress websites and should be notified to fix it.
1 voteThe Plesk "admin" can set who receives the notification in Tools & Settings > Plesk > Notifications in the configuration entries
"WordPress site vulnerabilities found (administrator's digest)"
"WordPress site vulnerabilities found (reseller's digest)"
"WordPress site vulnerabilities found (customer's digest)"
-- PD
-
please use two Two-factor authentication for plesk
please use two Two-factor authentication for plesk.
1 voteTwo-factor authentication was implemented in Plesk many years ago – https://support.plesk.com/hc/en-us/articles/115004010653-Is-it-possible-to-configure-multi-factor-authentication-to-access-Plesk-
—
IG
- Don't see your idea?