• 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 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Strong password security policy isn't accepting strong password

Beau Dilon

New Pleskian
According to the security policy page, a "Strong" password:
These passwords are at least 8 characters long and have at least one occurrence of upper and lower-case characters, digits, and special characters.

However, when trying to create an email account from the CLI, passwords which meet these requirements are being rejected. It seems it needs at least 2 special characters, specifically not just any special character, but one of !,@,#,$,%,^,&,*,?,_,~

This specific requirement should be noted. Here are some example passwords that have been rejected according to the policy:

ahwei.gh6Aih
aeH6doaGeth$
w!9>W9i,6
1]H__O_rW
uNj~4`IZ
 
Last edited:
I wouldn't really call it horribly broken but rather very smart. The only issue it has is that it is not documented correctly. But the approach to dynamically adjust the minimum number of characters based on the variety of the string is some smart piece of software, not just an ordinary algorithm.
 
I wouldn't really call it horribly broken but rather very smart. The only issue it has is that it is not documented correctly. But the approach to dynamically adjust the minimum number of characters based on the variety of the string is some smart piece of software, not just an ordinary algorithm.
I would call accepting 123$%&A (only 7 characters!) as "strong" horribly broken.
 
Agree. A password of 7 characters is from the day before yesterday. I was just wondering why symbols like ~ or > are rejected? There must be a justification behind this, but I cannot figure out any.
 
Back
Top