b.pedini
My feedback
8 results found
-
72 votes
An error occurred while saving the comment -
9 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment b.pedini
commented
Igor, sorry to be honest, but 1 hour of even an entry-level engineer, is in my opinion worth a security issue that bugs every Plesk server in existance.
How many votes would you need to consider using a tini tity bit of your team time, to implement something that you can touch with your own hands? Because the Plesk UserVoice is full of things well-voted but never even taken into not even remote consideration
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/5284370-synchronize-plesk-servers-failover
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/4078720-add-clamav-as-module-in-plesk-to-protect-better-th
- https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/4565504-block-the-ip-of-the-selected-country-in-firewall
respectively, one with more than one thousand paying customers asking for, and two relatively easy-to-implement tasks with more than 9 hundred and 5 hundred respectively, yet not even remotely taken into account.
Are those enough proof that your copypaste default reply just irritates people and serves nothing?b.pedini
shared this idea
·
-
40 votes
An error occurred while saving the comment b.pedini
commented
Checkbox to ask the user "Create aliases for this email account too" during the email account creation, maybe?
It doesn't directly solve the issue of creating an alias-only address, or using an alias address as sender, but it opens the ability to have only some emails have all the other domains as aliases configured, instead of having to disable the mail service completely when you would like just "info@" having all the aliases and no other inbox.Or, as there is the ability to select which domain (ex. "@example.com" or "@example.net") to create the account for, include the aliases too in the domain selection dropdown.
b.pedini
supported this idea
·
-
160 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.
—
IGb.pedini
supported this idea
·
-
9 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment b.pedini
commented
I would also like to add that security issues like these, in 2020, should have been addressed already long time ago, since we're in v18 of the software!
+1 !!
b.pedini
supported this idea
·
-
17 votes
Thank you for the update! 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.
—
IGb.pedini
supported this idea
·
-
13 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGAn error occurred while saving the comment b.pedini
commented
That's why I have purposely crafted an autodiscover subdomain on Plesk with an xml forged by hand.
I agree it would be better off served by Plesk itself, in the correct manner.b.pedini
supported this idea
·
-
2 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IGb.pedini
supported this idea
·
1 man hour job to implement + 3 man hours job to test and verify:
add an optional checkbox (like the ones for securing "www" and "webmail"), to "Force DNS-01 verification", maybe under an "Advanced features" section.