Hi Matt, > However, qmailadmin does not appear to support this. Only [EMAIL PROTECTED] > is able to log in via qmailadmin. > > Shouldn't the user also be able to authenticate as [EMAIL PROTECTED]
I can't reproduce this behaviour (using vpopmail 5.2.1 with qmailadmin 1.0.6), however, qmailadmin always switches to the main domain, i.e. you log in as [EMAIL PROTECTED], qmailadmin shows "bob.com" at the main menu, not "bobsmith.com". This may cause trouble. If you have had a customer with an-ugly-domain.com, having a zillion of alias domains, and then one day telling you, hey, I don't need an-ugly-domain.com anymore, you're in the bad situation that you can't kill an-ugly-domain.com because that would break every single alias domain. Furthermore, creation of ezmlm mailing lists will always succeed in creating <listname>@an-ugly-domain.com, even if you logged in as [EMAIL PROTECTED] To get rid of the "the customers wants to close its main domain" problem, I tried creating dummy hostnames for customers' accounts, e.g. "<login-id>.internal", then having _all_ domains as aliasdomains for "<login-id>.internal", thus being able to create and delete every single domain without trouble. Unfortunately, this creates more confusion - think about "Hi. I'm the ezmlm program on <login-id>.internal.". Is anybody aware of this? Unfortunately I'm no C programmer, but I would highly appreciate if qmailadmin took the domain name from the customer's login instead of switching to the "real" domain right after login. Does anybody have a hint on this? Jonas
