Facebook
Twitter-
Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring. We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design. If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
-
Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations. -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
I am not at all a Plesk-for-Windows expert, but think that you'll need to set filtering rules in IIS for that. The general approach including where to find this is described in the official docs of IIS
and an example of a "ruleset" is described here
social.msdn.microsoft.com
Maybe it helps.
HTTP Headers for Filtering Rules <scanHeaders>
Overview The <scanHeaders> element of the <filteringRule> element defines a collection of HTTP headers that a request filtering rule will scan fo...
learn.microsoft.com
Request Filtering to block bad bots / crawlers
social.msdn.microsoft.com
@Jean-LucP this has to be done within IIS and Request Filtering. Perform this on the main server/site. Once in Request Filtering, click on the Rules tab and a new Filtering Rule which scans the User-Agent within the headers and then deny strings such as MJ12bot, there are lots of other bots you may want to block too.
