These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Squirrel Mail or horde IMP on the new forum.
Web Hosting and Cloud Computing Control Panels
Either one will work fine with Virtualmin, although the officially-supported e-mail client is the built in Usermin application.
To answer your second question, you can install both SquirrelMail and Horde either per server or system wide. If you want to use the built-in script installers and you want your virtual servers to have individual customizations, then per server is the way to go. However, my preference is a single consistent system-wide implementation of both SquirrelMail and Horde. I think this is much easier to maintain and makes more sense than having multiple copies of it running in each domain. See my post on this topic:
<A HRef="http://www.Virtualmin.com/forums/message-view?message_id=40857">Re: virtual server mail alias</A>
I agree, a system wide install would be much easier to maintain than individual installs.
although individual install would be better if there was an option to upgrade all the squirrel mail installs as one unit.
I read your post, thank you, do you know if your idea was implemented to use the login manager, or is that something I would have to manually install.
To install squirrel mail system wide what would I do?
Hey guys,
As Alan noted, a system-wide install is a good option for the webmail scripts, if you want to provide a webmail system other than Usermin.
You can still use Install Scripts to perform the installation, however. Just create some sort of "admin" domain (e.g. "tools.hostingprovider.tld", or whatever you wanna call it), and install all of your preferred extra tools (a lot of folks would put phpMyAdmin and phpPgAdmin in as well) into that. I'm actually thinking along those lines for the default install--we get an awful lot of requests for some sort of standard install of phpMyAdmin, so it might make sense to automatically create a first host and drop a bunch of "favorite" scripts into it, preconfigured for all users.
For the individual install upgrade question: It is possible to upgrade all instances, though there can be problems if the upgrade is not straight-forward (we don't really have any control over how complex the upgrade process is for these scripts, since they aren't ours).
For something like webmail and database administration scripts, a system-wide install is perfectly reasonable...and they are designed to be workable for all users on the system, so you don't actually have to do much to alter the configuration. In some cases, you could add proxy rules or aliases for each new domain to allow the user to reach these tools on their own domain (again, something like tools.newdomain.tld). The options for what you can do are pretty wide open. Possibly too wide open, since we get a lot of question in this area! ;-)
--
Check out the forum guidelines!