• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Weak passwords on mail accounts

R

Ragefast

Guest
Hello people,

Recently I've been target of spammers which upon further investigation, were using authenticated mail accounts to send mail thru my server, where all these exploited accounts had weak passwords like '123456'.

Although I force my clients with the good-password policy, they are able to change their password from Horde, which doesn't seem to make any checks on the password typed in. I can change their passwords to a safe one, but I feel that it is not right to just change it, because if the user doesn't notice the vulnerability, he will still try to change back to the weak one, which is easy to remember, for example.

Is there a way to block users from being able to change their password to weak ones from the Horde interface? Or even Plesk interface? Because Plesk, even with the dictionary checking turned one, still allows passwords like 123456.

Thanks.
 
Thanks for the reply, but the problem isn't really Plesk, but Horde. From some testing I did, even if Plesk refuses the password, you can still set it from Horde interface.

What I'd like to know if we can somehow force Horde to check these passwords too, so the user can't set them.

Thanks
 
Back
Top