• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Password Strength Policy - Strange behavior

Almaz

New Pleskian
Hello everyone,

I have a strange behavior on a Plesk server I manage, I set the Password Strength Policy to high, but sometimes email addresses get their passwords broken and send spam.
When I take a look at the passwords, sometimes users seems to be able to put a weak password.

For exemple :

| [email protected] | | saccoan |
| [email protected] | | CONTACT |
| [email protected] | | PERINE |

How it is possible ? I tried to put passwords like that, the system prevent me to do it.

These are, of course, passwords configured after the security policy change. All weak passwords were changed right after the policy change.

The server infos :

OS ‪Debian 8.11‬
Produit Plesk Onyx
Version 17.8.11 Mise à jour n° 88, dernière mise à jour le 5 Nov 2020 18:59

If someone has the slightest idea, that would be great ! :)

Thanks,

Arnaud
 

Attachments

  • Capture d’écran 2021-07-30 à 19.19.58.png
    Capture d’écran 2021-07-30 à 19.19.58.png
    1.3 MB · Views: 11
How did you change all the weak passwords? Maybe that process didn't or doesn't use the security policy correctly?

Maybe you can try performing that process again and try to set a weak password?
 
Back
Top