I have a number of dedicated server clients who have ISPConfig. I was turned on to it a couple of years ago by an article online. For the most part, it works very well!
My biggest beef is that it does things the *old* way. Why prefix everything web webX_? Postfix, Dovecot, MySQL and ProFTPd all support it, even if they have to be custom compiled for authentication via MySQL.
I would use ISPConfig in a production environment where I have my hosting clients if I didn't have to prefix everything with webX_. I know that "web" is just the default and can be changed. But that's not the point. I shouldn't have to tell firstname.lastname@example.org
that his username has to be web5_bob. He should be able to log in as email@example.com
, and firstname.lastname@example.org
should be able to log in as email@example.com
Are future versions of ISPConfig expected to use this functionality?
I read the ISPConfig 3 feature request sticky post, and I didn't see this listed. I did see some *very* impressive features listed and I would be interested in deploying it if it were to use virtual users instead of Unix users for everything.
Thanks for your time.
PS- Obviously there'd have to be at least one Unix user per account, and I understand that. I am VERY familiar with cPanel and (sadly) Plesk and while I think that they both have merits, they are both lacking in many ways. cPanel is good but inflexible in many ways, and don't even get me started on Plesk!