Skip to main content

Valid Email Account Password Characters

Comments

8 comments

  • cPanelMichael
    Apparently a couple of the passwords I tested had invalid characters. I was able to use the API to set the password, but entering it during login said invalid login. When I removed the symbols like * ; and, and used an @ symbol, it worked properly.

    Hello, Could you let us know what method you are using to login to the email account? For instance, did this happen with a specific email client, or can you reproduce it everywhere (e.g. Roundcube, Horde)? Thank you.
    0
  • swbrains
    Hi, This was logging in via the browser using the RoundCube webmail client.
    0
  • cPanelMichael
    Hello, Could you open a support ticket using the link in my signature so we can take a closer look? This isn't something I've been able to reproduce on a test system. Thank you.
    0
  • swbrains
    Thanks for looking at it. Since I'm not able to provide access to my server, I won't open a ticket via WHM as support will surely ask for access, especially since you couldn't duplicate it. This was reported to me by a customer and I duplicated her experience trying to log into the same webmail account. Her password (a test password) was in the form: x;um2`*TR My guess was that the semicolon, backtick, or asterisk was the problem, but I didn't test individually which one caused the issue. I just removed them all and added in an @ symbol and it worked fine. Resetting the password to the one above failed again. Perhaps the problem has to do with the way I update the password via the API. I use a command in my script like this: $URI = "$g_cpanelapiurl/Email/passwd_pop?email=$popuser&domain=$host&password=$poppass"; Perhaps special characters require some type of encoding since they're being used in a URL?
    0
  • sparek-3
    Chances are it's with the API call you used - although I'm not exactly sure what API system you are using. You probably need to URI encode that values that you are passing in order for them to be read properly. If you are passing them just in plaintext, it's probably not reading the full value that you are passing.
    0
  • swbrains
    Thanks. I believe that is probably the case. The API I am using is the UAPI Function: Email::passwd_pop
    0
  • cPanelMichael
    Perhaps the problem has to do with the way I update the password via the API. I use a command in my script like this: $URI = "$g_cpanelapiurl/Email/passwd_pop?email=$popuser&domain=$host&password=$poppass"; Perhaps special characters require some type of encoding since they're being used in a URL?

    Hello, Yes, it's important to URI-encode the values to avoid issues like the one you described (it may work without encoding in some cases, but it's generally a good practice to a URI encode the values to avoid these types of issues). I confirmed the specific password you provided as an example needs to be URI-encoded during the UAPI password call (not when authenticating). For example, the "x;um2`*TR" password should be written like this: %20x%3Bum2%60*TR
    Thank you.
    0
  • swbrains
    Thanks!
    0

Please sign in to leave a comment.