661 votesopen discussion · 115 comments · Feature Suggestions » Security · Flag idea as inappropriate… · Admin →
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.
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.
An error occurred while saving the commentLiwindo commented
I see here that it depends what kind of failover is requested to be implemented. A manual failover solution or an automatic one. Because for a manual one I do not see that it should be too complicated: Establish a permanent ssh connection between the servers and create a monitoring service who detects changed files. Afterwards they will be synced to the replication server.
Way more complicated might be a multi-node scenario or as said an automatic failover which detects if the primary goes down and starts the takeover based on defined conditions.
Recommendation: Create the manual failover approach for the normal licence and add a more complex solution for extra licensing.
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.
AALiwindo shared this idea ·