When i try to login to roundcube with username@domain.com for Virtual server user it says login failed.
But login with only the username is working.
Also loging in with created email user is working. like: john@domain.com etc.
Can not login with email alias of the default created virtual server user such as: webmaster@domain.com, postmaster@domain.com.
Any help is appreciated.
When a new virtual server is created, a new default user along with an email is created.
When i try to login into roundcube, i can only login with the username like, not with the default email.e.g example@example.com additional emails also doesn’t work as roundcube login user.
The problem is when i login as the user without the domain name, I log in as example@localhost on the roundcube but i would like to log in as example@example.com by default. Otherwise i have edit the user identities of every new virtualserver from the roundcube to user@domain.com for them to use it properly.
By log in as example@localhost user can not send any email outside localhost. gmail doesn’t accept it.
The username is the only thing RoundCube can authenticate with.
For email users within a domain, the username will actually be user@domain.tld (though this is configurable in a variety of ways). But, the user that owns the domain will just be domain. It will always be so, and it can’t be domain@domain.tld, because the same username is used for stuff that won’t allow an email address.
Generally speaking, you’d want to simply not use that user for email. Usermin can accept the domain@domain.tld form of the user name if you’re logging into Usermin on https://domain.tld:20000, but only because it has some logic that understands Virtualmin domains. Software that doesn’t know about those domains will need to use the actual user name. An email address is not a user, though the user may have the same user name as their email address.
I agree with not using the user’s account for email so I made a feature request to be able to have the primary email address to be disabled at virtual server creation via the server template system.
This issue went on track and ended up getting a lets encrypt email notification upgrade
