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 are starting to get requests from the field from customers who wish to use a 3rd party spam filter system. This feature would help us stay automated as each of these requests must be implemented manually on the MTA, and complicates migrations across plesk nodes, and prevents our customers from reconfiguring their setting for this themselves.
the ui should enable plesk admins and customers to set domain and mailbox-level transport rules. Our web developers are wanting to force email addresses used for web form notifications to use outgoing filtering, while also asking that some of the other addresses not be filtered (ceo, marketing addresses, etc)
934 votesopen discussion · 107 comments · Feature Suggestions » Plesk (general) · Flag idea as inappropriate… · Admin →
just adding my 2 cents-
we've had to move away from plesk in some of our hosting efforts so we can have better HA.
we've had to build large clustered web systems, which is not ideal.
we lose the primary tools our customers have grown to love, and our staff understands: plesk.
we would love to see some solution around plesk being clustered.
if we had a this, it would allow us to shutdown a plesk node, and keep the services up- we would probably drop our complex beast in favor for it.
there are many options, and we've even done labs to see if we could trick plesk into being this way. We fault at IP failover, there's not an easy way to create a floating IP setup.
We have looked at software load balancer to address this- but to make the whole thing slick, and keep the plesk updates flowing we would need a vendor-supported solution- so we stopped in our efforts.
For future reference (if needed), we were looking at this: http://securityrouter.org/
the interface is easy enough for most plesk admins, or IT generalists to deploy and use.
Hopefully you guys will get this feature up and running one day!
Since Plesk Onyx you will be able to install memcache as a Docker container and configure http(s) proxy rule for it to map to your web app.
Docker and proxy rules are available in Plesk Onyx Preview already, you can try it here https://talk.plesk.com/threads/plesk-onyx-preview-and-feedback.337172/
i would suggest to use couchbase to supply memcached services. it would be easier to integrate and is protocol compatible with memcached.
It would also allow the plesk node to participate in a couchbase cluster (possibly using other plesk nodes as members)- meaning a plesk node can reboot and the cache would not need to be re-saturated.
if you have many sites that rely on caching on a single node, this is helpful, as cachestorms from a reboot could cripple a dense plesk node.