Hi everyone and first of all a big "thank you!" to the developers, I enjoy using ISPConfig and just moved from ISPman - a huge improvement in usability Here's my question: I'd like to use squirrelmail (which I set up with no problems as debian package 1.4.9a-1 in /usr/share/squirrelmail) as a subdomain á la http://webmail.domain1.de http://webmail.domain2.de http://webmail.domain3.de *and* use webmail at http://www.domain1.de/webmail *and* use php safe mode ON *and* leave squirrelmail at /usr/share/squirrelmail to keep easy maintainability (one apt-get update updates the stuff, no hassles). different approaches I tried: 1. make a softlink "ln -s /usr/share/squirrelmail /var/www/web1/web/webmail", use "webmail" as a co-domain and point it to the directory webmail. Disadvantage: doesn't work with php safe mode 2. create a separate web (with safe mode off), "rm /var/www/web2/web", create a softlink like "ln -s /usr/share/squirrelmail /var/www/web2/web". Disadvantage: 2 webs per user (= two traffic stats) 3. use a global alias in the httpd.conf and point a co-domain to it. Disadvantage: doesn't work at all (http://web1.de/webmail works, but http://webmail.web1.de complaints about a nonexistant webmail/ directory...) To me it seems, that I tried all possible configurations (by the way: .htaccess redirects don't help me here because of the web-statistics) but if anyone knows hot to better implement squirrelmail and php safe mode: please write
Have you thought about using the ISPconfig squirrelmail package? http://www.ispconfig.org/downloads.htm
Yes I thought about the package Disadvantages for me: updating depends on someone updating the pkg-file (with the debian ap-get way I know that I'll get a security fixed stable version - in a production environment this is really important for me. The .pkg squirrelmail is "SquirrelMail 1.5.1, 2006-02-19 - This is the second release of our new 1.5.x-series, which is a DEVELOPMENT release") it will install itself to ...:81 which means: no traffic-control for me which i need to pin down to customers it would require a redirect which is as much work as I have now, so no improvement... In the thread http://www.howtoforge.com/forums/showthread.php?t=4964 is a nice Apache VirtualHost setting described - but that won't help me either
