![]() If you should be tempted to build them and try them out, please remember to do so in a test environment and that you do so at your own peril! And if you want to track my packaging changes, I’ve put a collection of repositories online, too. Obviously, this work deviates from the “official” Kolab packages, but since it appears that those packages aren’t being refreshed with upstream fixes as often as might be desirable, I’ve decided to put some source packages online. And if you want to install something that gets its services from other computers, kolab-minimal should be all you need. But now, the kolab metapackage is formulated in terms of the “infrastructure” components plus kolab-minimal. If you want to install the complete stack, the kolab metapackage will bring everything you need into the installation and hopefully provide you with a self-contained solution. Here’s where this takes us:Ī dependency diagram for Kolab featuring a kolab-minimal package and the different setup-kolab invocations To support this specific situation, and to eventually move beyond it to support other architectural configurations, I have chosen to introduce a new metapackage called kolab-minimal: the glue components of Kolab plus the Web components minus the “infrastructure” components, those being the components providing the LDAP, IMAP and mail transport services. ![]() The Dovecot work is still very much in progress, however.Īs you may recall, I wanted to deploy an XMPP server – ejabberd – on one host and the rest of the Kolab stack on another host, and yet retain the possibility of configuring these different components using setup-kolab. Supporting a choice of IMAP servers gives everyone a bit more flexibility and should make Kolab a bit easier to adopt. After all, choice is an important motivation for adopting Free Software, and we should at least try and make that choice convenient to exercise where possible. even at supporting Dovecot in setup-kolab as well. Since then, I’ve been looking at making the IMAP server an “unbundled” component – IMAP service still being required, of course – and In my last post about Kolab I hinted about unbundling the LDAP server and using a remote server for LDAP service. In the kolab-webadmin page you can now add a new alias called now enjoy your groupware on your RaspberryPi.įor all of you who just want to download and install the DEBs:īy the way, the docs on are really helpful. Server_host = localhostserver_port = 389version = 3search_base = dc=domain,dc=orgscope = subdomain = ldap:/etc/postfix/ldap/mydestination.cfbind_dn = uid=kolab-service,ou=Special Users,dc=domain,dc=orgbind_pw = ComeOn_I_wont_tell_youquery_filter = mail In the past I loved to have a Catchall for my domain, so I created a new file in /etc/postfix/ldap called virtual_alias_maps_catchall.cf Now I can synch my mobile with my own groupware, including tasks, contacts, appointments. The cool stuff is, on my smartphone (Samsung Galaxy Note with Omni Rom = Android 4.4.2) I create a new account with "Microsoft Exchange", enter my eMail address and password, accepting all SSL certificates and that's it. Now you can create a user and so on and it will receive mails just right after creation. You want to login after that?Go to and login with "cn=directory manager" and the known password. I saw that my MySQL installation needs a password for the root user on localhost (got an error message during the setup) but nevertheless it's working. :-) (write down all the passwords, you'll need them) Now add postfix and cyrus to the ssl-cert group and also to the mail group. Openssl req -new -x509 -nodes -out /etc/ssl/certs/cyrus-imaps.pem -keyout /etc/ssl/private/cyrus-imapd.key -days 3650Īnd change the filenames in the /etc/nf accordingly. Ln -s /var/lib/cyrus/ /var/lib/imapln -s /var/spool/cyrus/ /var/spool/imapln -s /usr/lib/cyrus /usr/lib/imap Kolab needs some IMAP extensions which are available in cyrus-imap 2.5 (patches from kolab which are included un the next upstream) but currently the directories are not setup correctly. Ok, I had some problems but here is a short I had to install apache-2.2 and then compile 389-admin. Yesterday I finished the compilation story and was able to setup kolab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |