On Tuesday 30 May 2006 18:41, Jon wrote: > I had it installed without error, but I couldn't get the admin interface > to pick up on the port I specified. I changed the Listen to port 550 > (randomly selected) but it would never pick up. I did make the change in > the template and ran kolab config afterwards.
Not sure about the details here - I think there's many places the port number has to be changed.... Andrew has the details on this, if he's monitoring the thread. > I'm running several sites with apache2 on port 80 already if that matters. Shouldn't - once you disable the Listen on port 80 line in the kolab apache config. > There are a couple of things that I'm unclear on, though. First is the > master/slave thing. Do I need a slave? A master should be sufficient for your needs. A slave would be a secondary server that'll sync it's LDAP tables with the master. Useful for larger organizations, or ones that have many geographic locations. > Second, is my TLD good enough for the master TLD or do I have to ad a > subdomain to it? I seem to recall reading a doc somewhere that stated a > subdomain was preferable. However, if I make one up on the fly > kolab.jonwatson.ca) will the kolab scripts configure the apache virtual > server for me? Doesn't seem to work... I just used my TLD, and I have no problems. > Lastly, certificates. Do I need one? I don't know anything about how to > answer those questions during the install. If you want to encrypt the transmission of the data, yes you need a certificate. If not, you don't. The also affects if the corresponding SSL port would be open (i.e. 110 for pop3, and 995 for pop3s). > I have to say, for such a robust application I'm quite surprised that > I've been unable to stumble across any install documentation other than > the three lines on the kolab site or in the doc. Feel like writing some? :) The README file contains the install instructions. But it's basically "run the two scripts in order, follow the instructions when they come up..." Of course, this assumes you have some background knowledge regarding email servers, so there's always room for improvement in documentation. > > I guess I did resurrect this thread... I'll forgive you... this time... :) Shawn _______________________________________________ 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
