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.
what does netstat -tlp say? what do the apache logs in /kolab/var/log/ say? > I'm running several sites with apache2 on port 80 already if that matters. what about the ssl port? > There are a couple of things that I'm unclear on, though. First is the > master/slave thing. Do I need a slave? no. not unless you need a hot-fail-over system > Second, is my TLD good enough for the master TLD or do I have to ad a > subdomain to it? should be ok. it's recommended mostly as a best practices thing from what i understand. > Lastly, certificates. Do I need one? I don't know anything about how to > answer those questions during the install. no. let it generate them for you. > 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. yeah. the people making kolab are a little end-user clueless at times =) btw.. check this out: ---------- Forwarded Message ---------- Subject: [Kolab-devel] [Announcement] Native kolabadmin application Date: Monday 29 May 2006 06:17 From: Tobias Koenig <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hi, the kolab administration webfrontend is nice for small installations, but as soon as you want to manager several hundred users or even more you have real usability problems. For example if you want to add a new member to the distribution list you have to input the email addresses, but with hundreds of users you have to lookup them first. A better way would be to provide a combobox with all users listed in it. However when your distribution list contains 12 members, your browser needs to load 12x1000 combobox entries. In this case a native client application which provides the same functionality like the web frontend could help. So instead of providing comboboxes, the administrator could search in a ldap search dialog for the members he wants to add. Also people like native applications better than web applications, that's a fact ;) Over the last month I wrote such an application in Qt4/C++, so it is portable on every Unix and should also work on Windows when libopenldap is installed. The current limitations are: - uses only CRYPT passwords (can be fixed by an additional dependency to QCA) - no sieve based functionality yet (can be fixed by implementing a sieve tool, which is planned for KDE4 anyway) Otherwise it should work fine, you can add/edit/delete - users - addressbook entries - shared folders - distribution lists - administrators - maintainers and configure the services of kolab. To check it out, just download the source from SVN via svn co svn://wgess16.dyndns.org/kolabadmin/trunk kolabadmin cd into kolabadmin and execute qmake make make install For comments, bug reports and suggestions you can send me a private mail. Ciao, Tobias -- Separate politics from religion and economy! The Council of the European Union is an undemocratic and illegal institution! ------------------------------------------------------- -- Aaron J. Seigo Undulate Your Wantonness GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
pgpj9i4fMfmYs.pgp
Description: PGP signature
_______________________________________________ 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
