IT_Architect
Verified User
- Joined
- Feb 27, 2006
- Messages
- 1,080
Currently people cannot even set up their own auto-responders, maintain their own vacation messages etc. How about something like this:
https://mydomain.com/remote
Rather than logging into SquirrelMail, you would log into a php page that contains links to user-type items. This creates a single point login and the user sees results filtered by his login. Any company with more than 20 or more employees would want something like this and I would think it would be an impediment to DirectAdmin sales not to have it. The database to work from would be the e-mail user database. You could enable and disable it from a parameter in the conf file.
Your customers are not the users, the hosting companies are. Their respect is at risk with every product they sell. There is risk enough simply selling something that isn't a household word. They only need to hear once from a customer, "You mean the domain administrator has to change the passwords, do the auto-repsonders, vacation messages, and forwarders for every user?" It makes the hoster feel foolish for selling DirectAdmin rather than "HouseholdWord", leaves the customer thinking that his hoster isn't the brightest light in the harbor, and the hoster knows that's what the customer is thinking. DirectAdmin competitors could easily convince hosting companies that this shortcoming falls into the show-stopper category.
There are a lot of arguable preferences and trade-offs among control panels. It's rare to find something that is so missing, so clear cut, that has actual revenue enhancing potential, and requires no compromise of DirectAdmin's strengths.
https://mydomain.com/remote
Rather than logging into SquirrelMail, you would log into a php page that contains links to user-type items. This creates a single point login and the user sees results filtered by his login. Any company with more than 20 or more employees would want something like this and I would think it would be an impediment to DirectAdmin sales not to have it. The database to work from would be the e-mail user database. You could enable and disable it from a parameter in the conf file.
Your customers are not the users, the hosting companies are. Their respect is at risk with every product they sell. There is risk enough simply selling something that isn't a household word. They only need to hear once from a customer, "You mean the domain administrator has to change the passwords, do the auto-repsonders, vacation messages, and forwarders for every user?" It makes the hoster feel foolish for selling DirectAdmin rather than "HouseholdWord", leaves the customer thinking that his hoster isn't the brightest light in the harbor, and the hoster knows that's what the customer is thinking. DirectAdmin competitors could easily convince hosting companies that this shortcoming falls into the show-stopper category.
There are a lot of arguable preferences and trade-offs among control panels. It's rare to find something that is so missing, so clear cut, that has actual revenue enhancing potential, and requires no compromise of DirectAdmin's strengths.