> other things for you.  But it does have some limits.  First, Kolab as it
> stands right now does not support virtual domains.  Second, it installs
> into a chrooted environment (good for security), and this environment
> captures port 80, as well as the various email/pop3/imap ports.  This means
> that you cannot easily install Kolab onto a box with an existing web
> server.  Ideally though, email should be on a separate server anyways, so
> this may not be much of a problem for some.
>

That is actually not true.  Kolab supports virtual domains ... because postfix 
does.  Kolab does not support multiple virtual domains in the default setup 
in the current stable release of the server.  You have to configure the setup 
yourself as you normally would with a postfix server.  It does become 
slightly more complicated to setup because you have to know how Kolab works 
internally.  Many people have done it already, but it is not the easiest task 
to accomplish.  

Multiple domain support is available in the development snapshots, and beta 
releases for version 2.1

As for the ports ... it is quite simple to change the ports Kolab services run 
on to avoid this conflict.  I do it all the time.  It runs apache, so just 
like any other apache configuration, you can modify the Listen directives and 
the host settings to use an alternate port.

As for mail + web running on the same server ... that's perfectly acceptable.  
Should we run a different server for ftp, and a different server for DNS, and 
a different server for samba shares or SVN or CVS as well?  If you have the 
resources and ability to combine services onto the same machine I would think 
you would make use of that instead of having underutilized machines.  If the 
situation demands a dedicated server ... by all means.  There is no harm is 
running them all together though.

Andy


_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to