I installed ISPConfig3 on Ubuntu9.04 server following the tutorial: http://www.howtoforge.com/perfect-server-ubuntu-9.04-ispconfig-3 My question is related to squirrelmail, which did install and I did check if it worked at http://xx.xxx.xxx.xxx/webmail. Which did display the login page. I didnt bother to try to login because I hadnt set anything up at that point. Since then I have created 3 websites, but I can not get squirrelmail login page to come up. For some reason it just defaults to the home page of one of the websites? Have tried to reconfigure squirrelmail as in the TUT, but no good same problem. One thing I did change was to alter ISPConfig from http to https for login. There is nothing showing in the mail error log. Show mail warning log: Dec 2 09:41:44 xxxxxxxx postfix/smtpd[27251]: warning: 118-167-21-4.dynamic.hinet.net[118.167.21.4]: SASL LOGIN authentication failed: authentication failure Dec 2 09:42:15 xxxxxxxx last message repeated 11 times Dec 2 09:43:05 xxxxxxxx last message repeated 8 times Show mail log: Dec 3 10:45:01 xxxxxxxxx postfix/smtpd[26130]: disconnect from localhost.localdomain[127.0.0.1] Dec 3 10:50:02 xxxxxxxxx pop3d: Connection, ip=[::ffff:127.0.0.1] Dec 3 10:50:02 xxxxxxxxx pop3d: Disconnected, ip=[::ffff:127.0.0.1] Dec 3 10:50:02 xxxxxxxxx imapd: Connection, ip=[::ffff:127.0.0.1] Dec 3 10:50:02 xxxxxxxxx imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0 Any ideas?
Thats normal. You can access the default vhost of a apache webserver only as long as you did not assign this IP address to another website, what you did. There are 3 solutions: a) Dont assign the IP to a website, instead use * in the websites. b) Add another IP to your server and use this for accessing webmail. c) Create a dedicated vhost for webmail e.g. webmail.yourdomain.com in ispconfig and install a copy of squirrelmail or any other webmail client into this vhost. the recommended solution is c.
Ah thanks till will give option c a go. I take it I will need to set up a webmail.yourdomain.com for each website. And as an afterthought I suppose I could do the same thing for monitoring software too. I installed Nagios3 before vhosting and that was working but gets error500 messages now, because the permissions have altered in apache. Set up a client and website for that too yeah?
Normally you dont do that, as in most cases the domain of the provider is used for that and not the domain of a client. If you really want to use client domains for that, create the website with the domain of your company and add the client subdomains as aliases. Yes.
