• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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