From bernhard at intevation.de Tue Jan 13 17:40:06 2009 From: bernhard at intevation.de (Bernhard Reiter) Date: Tue, 13 Jan 2009 17:40:06 +0100 Subject: [Kolab-announce] New native Windows and Mac OS Clients: first beta of Kontact Enterprise 4 Message-ID: <200901131740.09986.bernhard@intevation.de> Hello Friends of the Kolab Groupware Solution, as a christmas present the new server files.kolab.org was unveiled on kolab-devel@ on the 19th of December and it already had 'beta-huge-debug' versions of Kontact Enterprise 4 for Windows and Mac OS X. The available betas are huge, because they contain all debugging files, everything and the kitchen sink. Still, why should we have waited longer? You know it is a beta and bad things might happen, but you get to make the choice if you want to try it anyway. In best tradition of early publication in Free Software development you the Software now, despite some known problems. Go to https://wiki.kolab.org/index.php/Kontact_for_Windows_(beta-huge-debug) https://wiki.kolab.org/index.php/Kontact_for_MacOS_(beta-huge-debug) We will polish the installation packages during the next months. Feedback is highly appreciated, e.g. on the public mailinglists! Best Regards, Bernhard -- Managing Director - Owner: www.intevation.net (Free Software Company) Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com. Intevation GmbH, Osnabr?ck, DE; Amtsgericht Osnabr?ck, HRB 18998 Gesch?ftsf?hrer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 206 bytes Desc: This is a digitally signed message part. Url : http://kolab.org/pipermail/kolab-announce/attachments/20090113/7174303f/attachment.bin From thomas at intevation.de Fri Jan 16 16:57:38 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Fri, 16 Jan 2009 16:57:38 +0100 Subject: [Kolab-announce] Kolab Server Hotfix 20090116 Message-ID: <20090116155738.GF10329.thomas@intevation.de> This hotfix package fixes three issues in the groupware functions of Kolab Server 2.2.0. Users of 2.2 release candidates or beta versions should upgrade to 2.2.0 first, users of Kolab Server 2.2.1-beta1 must _not_ apply this hotfix since the issues are already fixed here. kolab/issue3074 (Freebusy trigger fails for other users' calenders) kolab/issue3236 (automatic acceptance, Attendee status email not recognized by Outlook 2003) kolab/issue3284 (Webclient or resmgr might send invitations that Outlook 2003 does not understand (unquoted CN with Umlauts)) Visit http://issues.kolab.org/ and enter the corresponding issue numbers to view more details. The hotfix is available from the Kolab download mirrors in the directory server/release/kolab-server-2.2.0/hotfix-20090116 (see http://kolab.org/mirrors.html for a list of download mirrors) While the mirrors are catching up, you can also get the hotfix files via rsync: # rsync -tvP rsync://rsync.kolab.org/kolab/server/release/kolab-server-2.2.0/hotfix-20090116/iCalendar.php . # rsync -tvP rsync://rsync.kolab.org/kolab/server/release/kolab-server-2.2.0/hotfix-20090116/kolab-issue3074.patch . SHA1 sums: 5294eab5f874cfa4d76415a5e20a5122d5e86b3a iCalendar.php 4eb16659513c07c38e4a7a7e5d1ed75d262ef3f6 kolab-issue3074.patch The hotfix can be installed on your Kolab Server with the following commands executed as user 'root' or 'kolab': # cp iCalendar.php /kolab/lib/php/Horde/ # patch -s -p0 -d /kolab/lib/php < kolab-issue3074.patch -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 206 bytes Desc: not available Url : http://kolab.org/pipermail/kolab-announce/attachments/20090116/e767a289/attachment.bin From thomas at intevation.de Thu Mar 5 17:26:47 2009 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Thu, 5 Mar 2009 17:26:47 +0100 Subject: [Kolab-announce] Kolab Server 2.2.1 Release Candidate 1 Message-ID: <20090305162647.GA1490.thomas@intevation.de> Hi! I just uploaded Kolab Server 2.2.1-rc1 which contains about 60 enhancements and fixes compared to beta1. Please make sure to follow the upgrade instructions in 1st.README, especially if upgrading from server 2.2.0 or older. Again many thanks to all the people who helped with this! Documentation and OpenPKG source packages will soon be available in the directory server/beta/kolab-server-2.2.1-rc-1/ of the mirrors listed on http://kolab.org/mirrors.html for example: http://ftp.gwdg.de/pub/linux/kolab/server/beta/kolab-server-2.2.1-rc-1/ ftp://ftp.gwdg.de/pub/linux/kolab/server/beta/kolab-server-2.2.1-rc-1/ rsync://rsync.kolab.org/kolab/RSYNC.txt explains how to get (or mirror) the files via rsync. All files updated since 2.2.1-beta1 are available in the directory server/development-2.2/20090305-since-20081212/ You can check the integrity of the downloaded files with: $ gpg --keyserver hkp://subkeys.pgp.net --recv-key 5816791A or import the key from https://www.intevation.de/~thomas/gpg_pub_key.asc (the same key that I used to sign this email) $ gpg --verify SHA1SUMS.sig $ sha1sum -c SHA1SUMS Binary packages for Debian GNU/Linux (etch/stable) on x86 platforms can be found in the ix86-debian4.0 directory next to the sources. Please look at 1st.README and release-notes.txt (attached for your convenience) for install instructions and more information about this release. Please report any problems you encounter in our issue tracker: https://issues.kolab.org/ Regards, Thomas Arendsen Hein -- thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998 Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner -------------- next part -------------- Kolab Server 2.2 Install and Upgrade Information ================================================ (Version 20090305, Kolab Server 2.2.1-rc1 See http://kolab.org/ for general information about Kolab, or look at http://wiki.kolab.org/ for specific topics. It is recommended to subscribe to the announcement mailing list at http://kolab.org/mailman/listinfo/kolab-announce to receive security advisories and release announcements. Quick install instructions -------------------------- Kolab server and the Kolab web client (based on Horde) will use about 1GB of disk space for the initial install. By default the directory /kolab will be used, which should be an empty directory or a symbolic link to an empty directory. If this directory does not yet exist, it will be automatically created. For production use it is recommended to create a separate partition for /kolab (2GB to have some spare) and partitions for /kolab/var (at least 2GB for log files, virus filtering and caches) and /kolab/var/imapd/spool (with enough space for your users' mails). For evaluation you could start with the 2GB partition for /kolab (or 2GB free space on / if you only have one big partition for your test system) and create the other partitions when needed. Do _not_ use an NFS mounted drive! Make sure that the following names are not in /etc/passwd or /etc/groups, as OpenPKG will want to create them: "kolab" "kolab-r" "kolab-n" To install the Kolab server, you need to download the files from the directory containing this file (1st.README) to some local directory. You can check the integrity of the downloaded files with: $ gpg --keyserver hkp://subkeys.pgp.net --recv-key 5816791A or import the key from https://www.intevation.de/~thomas/gpg_pub_key.asc $ gpg --verify SHA1SUMS.sig $ sha1sum -c SHA1SUMS Then as root, cd into that local directory and run # sh install-kolab.sh 2>&1 | tee /root/kolab-install.log to build and install packages in /kolab. The command output will be logged to install-kolab.log so that you have a reference in case an error occurs during installation. The install script needs to store some files and creates a subdirectory below /tmp (or $TMPDIR if set) for this purpose. The web client might create much load on your server if there are many concurrent users, so you can choose to not install it by adding the option "-x kolab-webclient" to the call to install-kolab.sh. Installing the web client on a separate host is possible, but not discussed here. If you do not want to install the free/busy view tool, add the option "-x kolab-fbview". The binary packages distributed via kolab.org are compiled with the web client and the free/busy view tool. Currently you need to compile from the source packages to install without these features, see kolab/issue2440 for details. By default, the Kolab server will now be started at boottime, so you have to bootstrap the server configuration now to prevent unconfigured components from being started, see kolab/issue1745 for details. Please run: # /kolab/sbin/kolab_bootstrap -b and follow the instructions. Check http://www.openpkg.org/documentation/ for additional documentation about the OpenPKG packaging system. General update instructions --------------------------- Generally an update of the Kolab server works as described in this section, but often you will need to deviate from these instructions as described in the sections below. Please read the release specific update instructions for all releases newer than the one you already have before you start the update, e.g. for upgrading from 2.2.0 to 2.2.1-rc1 you have to follow the instructions for upgrading from 2.2.0 to 2.2.1-beta1, too. In any case you should completely read *all* relevant update instructions *before* starting the upgrade procedure. Always make sure you have a recent backup of your /kolab directory before you attempt the upgrade. The installation of the new packages works just as for the initial installation. Download the files as described above and run # sh install-kolab.sh 2>&1 | tee /root/kolab-update.log If you installed without kolab-webclient or kolab-fbview you need to add the corresponding -x options again. install-kolab.sh will usually automatically determine which packages need to be built. If you have made changes to configuration files or an updated package includes configuration files which are usually regenerated from files in /kolab/etc/kolab/templates/ the old configuration file will be saved with the extension .rpmsave. For files generated from templates you just have to remove the rpmsave file, because services will refuse to start if there still is an rpmsave file, e.g.: # rm /kolab/etc/clamav/*.conf.rpmsave For other changed files (e.g. the template files themselves) you may want to transfer your changes from the .rpmsave backup to the new files. Then regenerate the configuration and restart all Kolab services with: # /kolab/sbin/kolabconf -n # /kolab/bin/openpkg rc all restart Or alternatively if the Kolab server was stopped before the upgrade: # /kolab/bin/openpkg rc openldap start # /kolab/sbin/kolabconf -n # /kolab/bin/openpkg rc all start Upgrade from 2.2.1-beta1 to 2.2.1-rc1 ------------------------------------- Nothing special has to be done for this upgrade. Upgrade from 2.2.0 to 2.2.1-beta1 --------------------------------- 0. Make a backup of your installation and data stored inside /kolab 1. The Kolab server must be stopped: # /kolab/bin/openpkg rc all stop 2. Save the current LDAP data: Copy the contents of the openldap database, use a different output filename if you want. You should make sure that no other users can read the sensitive data contained in the ldif file, e.g. with umask (limited to the slapcat call by using parentheses): # (umask 077 && # /kolab/sbin/slapcat > ~/kolab-2.2.0.ldif) 3. Start the standard upgrade: (as described in the General update instructions) # sh install-kolab.sh 2>&1 | tee /root/kolab-update.log 4. /kolab/etc/kolab/kolab.conf will be saved as kolab.conf.rpmsave, please move it back to the original name: # cd /kolab/etc/kolab && mv kolab.conf.rpmsave kolab.conf 5. Look at *.conf.rpmsave files in the subdirectories of /kolab/etc/, transfer your changes and remove these files. (as described in the General update instructions) 6. Before starting the LDAP server the database must be restored from the ldif (with Horde preferences filtered out, since these are now stored in files): # rm /kolab/var/openldap/openldap-data/* # /kolab/bin/awk '!/^ / {ok=1;} /^objectClass: horde(Person|Group)$/ {ok=0;} /^([a-z]*Prefs|turba(Contact|Members|PGPPublicKey|Type)):/ {ok=0;} {if(ok) print;}' ~/kolab-2.2.0.ldif | /kolab/sbin/slapadd 7. Start the OpenLDAP, generate the configuration files and start the Kolab server: # /kolab/bin/openpkg rc openldap start # /kolab/sbin/kolabconf -n # /kolab/bin/openpkg rc all start Upgrade from 2.2-rc3 to 2.2.0 ----------------------------- Nothing special has to be done for this upgrade. Upgrade from 2.2-rc2 to 2.2-rc3 ------------------------------- You should regenerated the free/busy cache again, as described in the upgrading instructions from 2.2-rc1 to 2.2-rc2. The IMAP annotation /vendor/kolab/xfb-readable (introduced in 2.2-beta3) was renamed to /vendor/kolab/pxfb-readable-for to reflect the actual meaning. After the upgrade the old annotations are still readable, but unused by the server. If you still need to write this annotation for some reason, you have to add it to imapd.annotation_definitions.template and run kolabconf. Upgrade from 2.2-rc1 to 2.2-rc2 ------------------------------- You have to regenerated the free/busy cache, which now can be done automatically. First (optional, but recommended) step is to remove the current cache below /kolab/var/kolab-freebusy/cache: # su - kolab-n $ rm -r /kolab/var/kolab-freebusy/cache/* Now you can use the following command (still as user kolab-n): $ PHP_AUTH_USER=manager PHP_AUTH_PW='managerpassword' /kolab/bin/php \ -c /kolab/etc/apache/php.ini /kolab/var/kolab/www/freebusy/regenerate.php As this will show the manager's password on the command line, you can alternatively open https://yourserver.example.com/freebusy/regenerate.php in a web browser and login as "manager". This needs "Allow unauthenticated downloading of Free/Busy information" to be disabled, which is the default. Upgrade from 2.2-beta3 to 2.2-rc1 --------------------------------- Updating the free/busy cache has to be triggered for all calendar folders of all accounts: - Users need to create or update an appointment in their folders. - Resources can be invited to a new appointment or send them an update to an existing appointment. Upgrade from 2.2-beta2 to 2.2-beta3 ----------------------------------- After upgrading, you should remove the package "kolab-horde-framework", which is no longer needed: # /kolab/bin/openpkg rpm -e kolab-horde-framework Upgrade from 2.2-beta1 to 2.2-beta2 ----------------------------------- Before running install-kolab.sh, you should stop the running Kolab server and remove some packages which got renamed or will no longer be needed by running this command: # /kolab/bin/openpkg rc all stop # /kolab/bin/openpkg rpm -e --nodeps apache2 apache2-php getopt proftpd \ pth sharutils kolab-horde-fbview kolab-resource-handlers Ignore errors about pth or sharutils not being installed, these were included in the beta1 release but not installed by default. Upgrade from Kolab server 2.1 or before --------------------------------------- Instructions for upgrading from Kolab server 2.0 will be added in a future version of this document. These instructions are for upgrading from Kolab server 2.1.0 to 2.2.1: 0. Make a backup of your installation and data stored inside /kolab 1. Before upgrading the Kolab server must be stopped: # /kolab/bin/openpkg rc all stop 2. Save the current LDAP data: Copy the contents of the openldap database, use a different output filename if you want. You should make sure that no other users can read the sensitive data contained in the ldif file, e.g. with umask (limited to the slapcat call by using parentheses): # (umask 077 && /kolab/sbin/slapcat > ~/kolab-2.1.ldif) 3. Some of the old Kolab packages must be removed to avoid conflicts during the upgrade process: # /kolab/bin/openpkg rpm -e --nodeps \ kolabd kolab-webadmin kolab-horde-fbview kolab-horde-framework \ kolab-resource-handlers getopt patch proftpd sharutils 4. New versions of openpkg and openpkg-tools are needed for the upgrade, so you have to install them manually beforehand. As root, cd into the directory of kolab server 2.2 binary packages and run: # /kolab/bin/openpkg rpm -Uvh \ ./openpkg-20071227-20071227.--kolab.rpm # /kolab/bin/openpkg rpm -Uvh \ ./openpkg-tools-1.4.6-20071231.--kolab.rpm If you do not have binary packages for you platform, you have to build them from source first. As root, cd into the Kolab server 2.2 source directory and run: # /kolab/bin/openpkg rpm --rebuild ./openpkg-20071227-20071227.src.rpm # /kolab/bin/openpkg rpm -Uvh \ /kolab/RPM/PKG/openpkg-20071227-20071227.--kolab.rpm # /kolab/bin/openpkg rpm --rebuild ./openpkg-tools-1.4.6-20071231.src.rpm # /kolab/bin/openpkg rpm -Uvh \ /kolab/RPM/PKG/openpkg-tools-1.4.6-20071231.--kolab.rpm ( and must be replaced by the correct values for your system). 5. Start the standard upgrade (as described above): # sh install-kolab.sh 2>&1 | tee /root/kolab-update.log 6. Before starting the LDAP server the database must be restored from the ldif: # rm /kolab/var/openldap/openldap-data/* # /kolab/sbin/slapadd -l ~/kolab-2.1.ldif 7. The format of the TLS session cache changed, therefore you have to truncate it to zero length: # > /kolab/var/imapd/tls_sessions.db 8. /kolab/etc/kolab/kolab.conf will be saved as kolab.conf.rpmsave, please move it back to the original name. # cd /kolab/etc/kolab && mv kolab.conf.rpmsave kolab.conf 9. Remove all *.conf.rpmsave files in the subdirectories of /kolab/etc/ as described above. 10. Start the OpenLDAP, generate the configuration files and start the Kolab server: # /kolab/bin/openpkg rc openldap start # /kolab/sbin/kolabconf -n # /kolab/bin/openpkg rc all start 11. After the successful upgrade some cleanup can be done, by removing obsolete files/directories: # rm -r /kolab/etc/resmgr # rm -r /kolab/etc/proftpd # rm -r /kolab/var/kolab/www/freebusy/cache/* 12. The free/busy cache has to be regenerated for all calendar folders of all accounts, see "Upgrade from 2.2-rc1 to 2.2-rc2" in this file. Additional hints may be available in the Kolab wiki: http://wiki.kolab.org/index.php/Kolab2_Upgrading Direct upgrade from Kolab1 is not supported. We suggest that you back up your IMAP store, install Kolab2 and manually recreate user accounts and then restore the IMAP data from the backup. Known regressions compared to Kolab Server 2.2.0 ------------------------------------------------ The following issues affect the current prerelease, but are expected to be fixed for the final release: kolab/issue3438 (kolabFreeBusyPast is not used) Generating your own 00INDEX.rdf for installations or upgrades ------------------------------------------------------------- The source and binary downloads contain the 00INDEX.rdf file needed by the "openpkg build" command used by install-kolab.sh to install or upgrade a Kolab server. If you already have your own set of binary packages from a previous build, you can use these to create a full binary installer (e.g. to install the packages on a second machine) or or a partial binary installer (for upgrades where you only want to compile the new .src.rpm files instead of everything). To generate this file, you always need all .src.rpm files, so link or copy them in a new directory (needs to be writable by the kolab user of your installation). After this you can link/copy the install-kolab.sh file and your binary rpm files (e.g. from /kolab/RPM/PKG/) into this directory and run the following command as user kolab or root to create the new 00INDEX.rdf file: $ sh install-kolab.sh -X If you want a pure binary installer, you can remove the .src.rpm files now. To be able to use this directory for fresh installations (i.e. not only for upgrades), you need to put the OpenPKG bootstrap file (openpkg-*.src.sh or openpkg---kolab.rpm) into this directory, too. Index generation tries to cache information about source RPMs in the file /kolab/RPM/DB/00INDEX-cache.db, you might want to remove it to save some disk space or restore it after new installations to save some time. Known problems and workarounds ------------------------------ - Compiling openpkg-20071227-20071227 does not work with gcc 4.3, e.g. on Debian/lenny. As a workaround you can install the gcc-4.2 package, but you have to make sure that OpenPKG calls this version by passing the --use_cc option to it via the -O flag of install-kolab.sh, e.g.: # sh install-kolab.sh -O --use_cc=gcc-4.2 ... See kolab/issue2871 (openpkg-20071227-20071227 does not compile with gcc 4.3) for details. - Your system (C library) has to support all languages you want to have available in the web admin interface, the web client and fbview. For most languages you have to use the non-UTF-8 and non-euro locales, i.e. de_DE, fr_FR, it_IT, nl_NL instead of e.g. de_DE at euro. For fbview some languages need a UTF-8 locale, e.g. ja_JP.UTF-8 for Japanese. The web client needs UTF-8 locale in addition to the non-UTF-8 ones in some situations. So it's best to install all variants for every language which shall be supported. See kolab/issue2732 (Horde and Web Admin Interface Language Selection depends on OS locale support) for details. - If login on https://yourserver.example.com/fbview and triggering free/busy regeneration does not work, try as user kolab: /kolab/bin/php -r 'imap_open("{localhost:143/notls}", "" ,"");' If it yields "Segmentation fault (core dumped)", then there probably is a conflict between a dynamically loaded libdb3 from your system and a statically linked libdb4 from the OpenpPKG php package. If it yields a "PHP Warning: ...", this part of the system works correctly. One reason for such a conflict could be the mere presence of /lib/libnss_db.so.*, which is installed on some distributions by default. On Debian systems it is contained in the package "libnss-db". If you really need this library, you could work around the loading of libdb3 by placing a symbolic link with the correct name in /kolab/lib, e.g.: ldd /lib/libnss_db.so.2 libnss_files.so.2 => /lib/tls/libnss_files.so.2 (0xb7f16000) ---> libdb3.so.3 => /usr/lib/libdb3.so.3 (0xb7e6b000) libc.so.6 => /lib/tls/libc.so.6 (0xb7d36000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000) ln -s /dev/null /kolab/lib/libdb3.so.3 See kolab/issue1607 (need to replace gdbm for pfbcache, because of license clash gdbm vs php) for details. - /kolab/sbin/kolab_bootstrap -b fails to start the temporary slapd on Linux 2.4 kernels if binaries compiled on Linux 2.6 (as provided on kolab.org) are used. See kolab/issue1795 for details. - Under some circumstance the Kolab server may not create or delete users or update the configuration after changes have been made in the web interface. This happens most often immediately after the bootstrap. In that case restart the kolabd: /kolab/bin/openpkg rc kolabd restart If user accounts are still not created or deleted, you can try removing the file /kolab/var/kolab/mailbox-uidcache.db and restarting kolabd. See kolab/issue1068 (Mailboxes are not created until kolabd restart) and kolab/issue1098 (Changes in the service tab are not accepted after bootstrap) for details. - If modifying or deleting of address book entries doesn't work, restarting openldap can help, see kolab/issue854 for details. - There is a report that the manager can only see users in the primary domain, see kolab/issue1485. We can't reproduce this problem, please tell us if you can. - Calendar folders for group/resource accounts can't be created for domains which were added after bootstrap, i.e. via the web admin interface. See kolab/issue1313 for details. - When deleting domains via the web admin interface, the corresponding LDAP data and IMAP spool stay on the server and have to be deleted manually. See kolab/issue1571 and kolab/issue1576 for details. - A domain maintainer can not always edit the email aliases for a user, even if the user and the alias is in domains the domain maintainer has access to. See kolab/issue2825 for details. $Id: README.1st,v 1.109 2009/03/05 14:46:04 thomas Exp $ -------------- next part -------------- Kolab Server 2.2 Release Notes ============================== (Version 20090305, Kolab Server 2.2.1-rc1 For upgrading and installation instructions, please refer to the 1st.README file in the package directory. Differences between Kolab 2.1 and 2.2: - Upgrade of central Kolab server components The Apache server shipped with the Kolab server has been upgraded to Apache-2.2.*. At the same time the system was switched to PHP5. Postfix got upgraded to 2.4.* which removes the need for special Kolab patches which were integrated upstream. The Cyrus IMAP server was updated to 2.3.* also removing the need for some, though not all, Kolab specific patches. - Inclusion of the web based Horde Groupware client The Kolab server now provides a web client that supports all the groupware features known from Outlook and Kontact. Thus users are less dependent on their local client and can access their groupware data from anywhere in the world provided they have a standard browser available. - Structural improvements Several components of the Kolab server got restructured so that porting the Kolab server to distributions other than OpenPKG got easier. This also improves the development model in general. - Improvements, bugfixes and upgraded software components The 2.2 release received many improvements and bugfixes for issues found in earlier versions. Additionally all software components have been upgraded to new upstream versions. The specifics are described below. Changes between 2.2.1-beta-1 and 2.2.1-rc-1 - apache-php-5.2.8-20081209_kolab2 Updated Kolab server patches. - imapd-2.3.13-20081020_kolab1 kolab/issue3175 (Cyrus IMAPd 2.3.13 Released) - install-kolab.sh Fixed two problems reported by martin.schulte at guug.de: Repair option -E to not require an argument. Abort cleanly on -c or -X if no OpenPKG environment is found. Cache source RPM information in $PREFIX/RPM/DB/00INDEX-cache.db when generating 00INDEX.rdf - Horde_Notification-0.0.2-20090223 New package needed for running unit tests of Kolab PHP packages. - Horde_Prefs-0.0.3-20090223 New package needed for running unit tests of Kolab PHP packages. - Kolab_Filter-0.1.4-20090303 kolab/issue3192 (Forwarding an invitation with Outlook failed) kolab/issue3299 (Kolab_Filter: big.eml is too big) kolab/issue3364 (manpages for kolabfilter and kolabmailboxfilter) kolab/issue3426 (php error when sending mail with enabled mail filter checking) kolab/issue3441 (Resources with policy "always accept" do not work if domain != kolabhost) kolab/issue3435 (Delivery of invitations fails with no "kolabInvitationPolicy" in ldap) - Kolab_FreeBusy-0.1.2-20090226 kolab/issue3313 (free/busy regeneration as manager broken in 2.2.1-beta1) - Kolab_Server-0.4.0-20090224 New upstream release. Fixed objectClass evaluation to respect case-insensitivity (Horde bug: #7694) Fixed initialization of parameters retrieved from LDAP. Fixed addrsForIdOrMail to return only lowercased mail addresses (as mentioned in kolab/issue3426) Fixed notices when retrieving LDAP attributes. kolab/issue2207 (Make it possible to enable and disable users to be able to use the webclient) kolab/issue2546 (Horde should use name and email from ldap as defaults) - Kolab_Storage-0.4.0-20090224 New upstream release. Fixed list driver to prevent overwriting folder data when authenticating twice (relevant for testing). Allow to supress triggering (relevant for testing). - kolabd-2.2.1-20090304 Add a redirection for the newer horde install location. Add LDAP attribute postfix-message-size-limit and adjust main.cf.template to allow central configuration of the postfix parameter "message_size_limit". Add user attribute kolabHomeServerOnly to create user mailbox on the kolabHomeServer only. Add ldapserver_statedir to kolab.globals to fix kolab_bootstrap on slave servers. Add kolab_cafile to kolab.globals to specify filename for kolab_bootstrap to copy the generated CA certificate. Allow to configure resmgr and freebusy logging via dist_conf Updated doc/README.outlook for Kolab Server 2.2.1. kolab/issue1001 (/kolab/etc/kolab/workaround.sh expects manager password on command line) kolab/issue3331 (kolabfilter uses incorrect delivery backend) kolab/issue3322 (freebusy.conf.template: ldap server can be on another machine) kolab/issue3387 (dist_conf configuration in kolab webclient templates) kolab/issue3408 (Template for inclusion in shell scripts) kolab/issue3447 (Heavy information leak from webclient directories) - kolab-fbview-1.2.0-20081227 kolab/issue3318 (kolab-fbview-1.2.0-20081212 fails to compile on solaris 10) - kolab-webadmin-2.2.1-20090304 Improved Dutch translation. kolab/issue3404 (Present the options in "Action to take for messages that fail the check" nicer) - kolab-webclient-1.2.0-20090226 Fixed a potential IE XSS issue. Fixed handling of folder "owner" for shared user folders with Dovecot. Correct iTip option handling for dimp. kolab/issue2207 (Make it possible to enable and disable users to be able to use the webclient) kolab/issue2546 (Horde should use name and email from ldap as defaults) kolab/issue2738 (horde should allow a setting to suppress groupware folders) kolab/issue3309 (Can not login directly in to dimp) kolab/issue3318 (kolab-fbview-1.2.0-20081212 fails to compile on solaris 10) kolab/issue3328 ([Webclient] DIMP groupware folder names display bug) kolab/issue3329 ([WebClient] Can not accept/deny invitations in Dimp) kolab/issue3387 (dist_conf configuration in kolab webclient templates) kolab/issue3439 (FreeBusy display in web client and fbview depends on kolabHomeServer in LDAP) - PEAR-Horde-Channel-1.0-20090119 kolab/issue2441 (/kolab/RPM/TMP/pear/temp created owned by root) kolab/issue3315 (PEAR-Horde-Channel-1.0 fails to compile on solaris 10) - PEAR-PHPUnit-Channel-1.0-20090119 kolab/issue2441 (/kolab/RPM/TMP/pear/temp created owned by root) kolab/issue3315 (PEAR-Horde-Channel-1.0 fails to compile on solaris 10) - perl-kolab-2.2.1-20090304 Create user mailbox on the kolabHomeServer only, if attribute kolabHomeServerOnly is true. Continue sync if connecting the IMAP server fails, just skip actions that would need it. Improved the ssh handling for slave setups in kolab_bootstrap. Add retry (every minute for 10 times, then every five minutes until successful) to syncrepl configuration. kolab/issue3225 (Remove unused kolab_upgrade script) kolab/issue3321 (slapd.replicas.template and slapd.access.template can be absent) kolab/issue3355 (POD manpages for perl-kolab) kolab/issue3407 (kolab_bootstrap: improve message about importing the CA certificate) - perl-ldap-5.10.0-20081028_kolab1 New upstream version (perl-ldap 0.39) and two patches for syncrepl support, see kolab/issue1755 (syncrepl support (for OpenLDAP >=2.4.6)) - php-5.2.8-20081209_kolab2 Updated Kolab server patches. Packages in the OpenPKG based Kolab server release: - Kolab packages: Added: Horde_Notification-0.0.2-20090223 Horde_Prefs-0.0.3-20090223 Updated: Kolab_Filter-0.1.4-20090303 Kolab_FreeBusy-0.1.2-20090226 Kolab_Server-0.4.0-20090224 Kolab_Storage-0.4.0-20090224 PEAR-Horde-Channel-1.0-20090119 PEAR-PHPUnit-Channel-1.0-20090119 kolab-fbview-1.2.0-20081227 kolab-webadmin-2.2.1-20090304 kolab-webclient-1.2.0-20090226 kolabd-2.2.1-20090304 perl-kolab-2.2.1-20090304 perl-ldap-5.10.0-20081028_kolab1 Unchanged: Horde_Argv-0.1.0-20081209 Horde_Auth-0.1.1-20081209 Horde_Browser-0.0.2-20081209 Horde_CLI-0.0.2-20081209 Horde_Cache-0.0.2-20081209 Horde_Cipher-0.0.2-20081209 Horde_DOM-0.1.0-20081209 Horde_DataTree-0.0.3-20081209 Horde_Date-0.1.0-20081209 Horde_Framework-0.0.2-20081209 Horde_Group-0.1.0-20081209 Horde_History-0.0.2-20081209 Horde_LDAP-0.0.2-20081209 Horde_MIME-0.0.2-20081209 Horde_NLS-0.0.2-20081209 Horde_Perms-0.1.0-20081209 Horde_Secret-0.0.2-20081209 Horde_Serialize-0.0.2-20081209 Horde_SessionObjects-0.0.2-20081209 Horde_Util-0.1.0-20081209 Horde_iCalendar-0.1.0-20081209 Kolab_Format-1.0.0-20081212 PEAR-Auth_SASL-1.0.2-1 PEAR-Date-1.4.7-1 PEAR-HTTP_Request-1.4.3-1 PEAR-Log-1.11.2-1 PEAR-Mail-1.1.14-1 PEAR-Mail_mimeDecode-1.5.0-20081209 PEAR-Net_LMTP-1.0.1-1 PEAR-Net_SMTP-1.3.1-1 PEAR-Net_Socket-1.0.9-1 PEAR-Net_URL-1.0.15-1 PHPUnit-3.3.3-1 clamav-0.94.2-20081212 openldap-2.3.43-20081212 php-smarty-2.6.20-20081212 sqlite-3.6.4-20081212 - OpenPKG packages: Updated: apache-php-5.2.8-20081209_kolab2 imapd-2.3.13-20081020_kolab1 php-5.2.8-20081209_kolab2 Unchanged: amavisd-2.5.3-20080101 apache-2.2.10-20081111 apr-1.2.12-20080101 autoconf-2.61-20080101 automake-1.10-20080101 bc-1.06-20080101 binutils-2.18-20080101 bison-2.3-20080101 bzip2-1.0.5-20080318 config-20060923-20080101 curl-7.17.1-20080101 db-4.5.20.2-20070628 diffutils-2.8.7-20080101 expat-2.0.1-20080101 file-4.23-20080101 flex-2.5.34-20080101 freetype-2.3.5-20080101 fsl-1.7.0-20080101 gawk-3.1.6-20080101 gcc-4.2.2-20080101 gd-2.0.35-20080101 gettext-0.17-20080101 gmp-4.2.2-20080101_kolab grep-2.5.3-20080101 groff-1.19.2-20080101 gzip-1.3.12-20080101 imap-2006k-20080101 jpeg-6b-20080101 libiconv-1.12-20080101 libmcrypt-2.5.8-20080101 libxml-2.6.31-20080111 libxslt-1.1.22-20080101 lzo-2.02-20080101 m4-1.4.9-20080101 make-3.81-20080101 mhash-0.9.9-20080101 mm-1.4.2-20080101 ncurses-5.6.20080112-20080113 openpkg-20071227-20071227 openpkg-tools-1.4.6-20071231 openssl-0.9.8g-20080101 pcre-7.5-20080110 perl-5.10.0-20080103 perl-comp-5.10.0-20080110 perl-conv-5.10.0-20080101 perl-crypto-5.10.0-20080101 perl-db-5.10.0-20080118 perl-dns-5.10.0-20080101 perl-ds-5.10.0-20080104 perl-locale-5.10.0-20080112 perl-mail-5.10.0-20080117 perl-module-5.10.0-20080101 perl-net-5.10.0-20080101 perl-openpkg-5.10.0-20080109 perl-parse-5.10.0-20080117 perl-ssl-5.10.0-20080101 perl-stats-5.10.0-20080101 perl-sys-5.10.0-20080101 perl-term-5.10.0-20080116 perl-text-5.10.0-20080101 perl-time-5.10.0-20080101 perl-util-5.10.0-20080116 perl-www-5.10.0-20080103 perl-xml-5.10.0-20080101 pkgconfig-0.23-20080117 png-1.2.24-20080101 postfix-2.4.6-20080101_kolab procmail-3.22-20080101 readline-5.2.12-20080101 sasl-2.1.22-20080101 sed-4.1.5-20080101 spamassassin-3.2.4-20080107 texinfo-4.11-20080101 zlib-1.2.3-20080101 Changes between 2.2.0 and 2.2.1-beta-1 - apache-2.2.10-20081111 New upstream version, fixes various security issues. - apache-php-5.2.8-20081209_kolab New upstream version, fixes various security issues. Added sqlite2 support for SyncML support in kolab-webclient. - bzip2-1.0.5-20080318 New upstream version, fixes CVE-2008-1372 (denial of service) - clamav-0.94.2-20081212 New upstream version, fixes various security issues. kolab/issue765 (openpkg "junk" warnings) - gawk-3.1.6-20080101 New package, build (not runtime) dependency of sqlite. - gmp-4.2.2-20080101_kolab kolab/issue2928 (gmp-4.2.2-20080101 does not compile on Debian lenny/amd64) - Horde_iCalendar-0.1.0-20081209 kolab/issue3284 (Webclient or resmgr might send invitations that Outlook 2003 does not understand (unquoted CN with Umlauts)) - Kolab_Filter-0.1.3-20081212 A new package replacing kolab-filter (from http://pear.horde.org/index.php?package=Kolab_Filter) Added LDA (dovecot) backend. kolab/issue839 (problem when kolabHomeServer is missing) kolab/issue3074 (Freebusy trigger fails for other users's calenders.) kolab/issue3208 (Free/Busy list is always empty) kolab/issue3256 (resmgr responses should reflect server revision in PRODID) kolab/issue3260 (kolabfilter does not allow empty sender (and therefore MAILER-DAEMON)) kolab/issue3289 (resmgr dies when it should accept, but has not Calender folder access) - only partial fix - Kolab_Format-1.0.0-20081212 New package (from http://pear.horde.org/index.php?package=Kolab_Format) - Kolab_FreeBusy-0.1.2-20081212 A new package replacing kolab-freebusy (from http://pear.horde.org/index.php?package=Kolab_FreeBusy) Fixed handling of extended free/busy information. Fixed identification of the corresponding free/busy server. kolab/issue3208 (Free/Busy list is always empty) kolab/issue3256 (resmgr responses should reflect server revision in PRODID) - Kolab_Server-0.2.0.20081114-20081114 New package (from http://pear.horde.org/index.php?package=Kolab_Server) - Kolab_Storage-0.3.0-20081205 New package (from http://pear.horde.org/index.php?package=Kolab_Storage) - kolabd-2.2.1-20081212 Added configuration option in resmgr.conf for local delivery backend. (Makes it possible to activate the new LDA backend) Activated sqlite support in PHP. Updated the configuration for the newer Kolab_Filter package. kolab/issue765 (openpkg "junk" warnings) kolab/issue936 (kolabquotawarn: system cron used, and firing when server stopped) kolab/issue1310 (kolabquotawarn runs via cron before server was bootstrapped) kolab/issue1755 (syncrepl support (for OpenLDAP >=2.4.6)) kolab/issue2351 (horde doesn't present attachment stuff while compose a message) kolab/issue2440 (Installing binary packages of 2.2 fails without Horde) kolab/issue2446 (Make the used syslog facility configureable (kolabd, kolabconf)) kolab/issue2550 (kolabconf should make some others postfix maps) kolab/issue2910 (obsolete definition of schemacheck in slapd.conf) kolab/issue2911 (Change comments around the idletimeout definiton in the file templates/slapd.conf.template.in) kolab/issue2961 (added smtpd_sasl_authenticated_header = yes for simpler authorization) kolab/issue2994 (Duplicated kolab.conf files in cvs, one should be removed) kolab/issue3005 (Remove specific TLSCertificate code by using new bootstrap_config conditional in slapd.conf.template) kolab/issue3006 (Surround the horde schema include in slapd.conf.template with @@@ conditionals) Remark: this actually added only the code that allows to use @@@if exists(=2.4.6)) kolab/issue2981 (kolab_bootstrap: re-use kolabconf code to read the config file) kolab/issue3006 (Surround the horde schema include in slapd.conf.template with @@@ conditionals) Remark: this actually added only the code that allows to use @@@if exists( for forms in webadmin) kolab/issue1615 (Use