Sergio Manzi
My feedback
8 results found
-
285 votes
Please note, Plesk has supported the version of Mailman provided by OS vendor by default.
The Mailman 3 is shipped by default on Ubuntu 18 and Debian 10.
Please keep voting if this request is still actual for you.
—
AAAn error occurred while saving the comment An error occurred while saving the comment Sergio Manzi
commented
Commenting "Admin" response of October 31, 2019:
I think probably all signatories of this request have a clear view about how Mailman is supported by Plesk (leveraging the version provided by the OS vendor), but I also think this is the very reason why this request have been brought forward in the first place, more than 3 years ago.
Of course I can speak only for myself, but I also think I'm not much off thinking that what we all would like to see is an OS independent implementation of Mailman 3, directly provided and supported by Plesk, together with all required components (Python, Django, Hiperkitty, Postorius).
I look forward for support of this clarification by all interested parties...
Sergio Manzi
supported this idea
·
An error occurred while saving the comment Sergio Manzi
commented
please...
-
675 votes
-
44 votes
-
386 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
-
532 votes
We have serious doubts this function can really increase server security:
1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.
As for concerns that default password requirement is set in “weak”, that fail2ban module is not…
-
22 votes
Thank you for your input. We will consider the possibility of implementing this feature in upcoming releases.
— ES
An error occurred while saving the comment Sergio Manzi
commented
I love it... Give it a try...
Sergio Manzi
supported this idea
·
-
1,580 votes
We hear you and see a clear demand for this feature.
I want to say that implementing these features requires a lot of investment, and in 2021 Plesk team keeps focusing on the delivery of other improvements (sad, but true).
We will back to the re-evaluation of these features at the beginning of the next year.
Please continue to share your use cases and requirements, and it would really helpful if you point to existing solutions that we can review and check before implementation.
Your feedback is important to us. Thank you, everyone.
—
AASergio Manzi
supported this idea
·
-
87 votes
An error occurred while saving the comment Sergio Manzi
commented
ah, yes, another one: a button for white-listing current client IP address (maybe permanently, maybe timed, for a day or whatever...)
An error occurred while saving the comment Sergio Manzi
commented
Other possible (related) improvements:
- sort by date (not by IP address which is almost useless...)
- query whois (maybe by clicking on IP address itself, or with a dedicated button/field in each row)Sergio Manzi
supported this idea
·
... let me add that personally I would also gladly give up any migration mechanism from Mailman 2 to Mailman 3, if this is an impeding factor: just "package" Mailman 3 as a newly supported Plesk component, please.