Hi Guys,
All of my customers get a username like this: S1581, S1592 etc..
Today I found that users with that kind of usernames cannot login to webmail or imap/pop3:
All these users are created trough the API, and that is interesting, because when I try to create a user with that kind of username trough the directadmin web interface i get a error: Invalid username.
So i take a look at the username requirements:
And this is the definition of alphanumeric:
So, i don't understand why:
1. There is no mail user when I create such user trough the API.
2. Why is a username in that format incorrect for creating a user trough the web interface?
Kind regards,
DJVG
All of my customers get a username like this: S1581, S1592 etc..
Today I found that users with that kind of usernames cannot login to webmail or imap/pop3:
Apr 9 10:31:03 neophron dovecot: auth: shadow(s1581,127.0.0.1): unknown user
Apr 9 10:31:03 neophron dovecot: auth: passwd-file(s1581,127.0.0.1): no passwd file: /etc/virtual//passwd
All these users are created trough the API, and that is interesting, because when I try to create a user with that kind of username trough the directadmin web interface i get a error: Invalid username.
So i take a look at the username requirements:
The User's username. 4-8 characters, alphanumeric
And this is the definition of alphanumeric:
The alphanumeric character set consists of the numbers 0 to 9 and letters A to Z.
So, i don't understand why:
1. There is no mail user when I create such user trough the API.
2. Why is a username in that format incorrect for creating a user trough the web interface?
Kind regards,
DJVG