This is the final release of ZCP 7.0.0. Please read the release notes on this final release at http://doc.zarafa.com/7.0/Release_Notes/en-US/pdf/Zarafa_Collaboration_Platform-7.0-Release_Notes-en-US.pdf
IMPORTANT: Please read the upgrade section in the Administrator manual. Make sure you do a back-up before upgrading.
In this version Zarafa included the ability for IMAP and POP gateway access per user organized via zarafa-admin and the upgrade-tool for 6.40 to 7, the security audit logging introduced in 6.40.7 is included in 7.0.0 s well. The zarafa-upgrade tool is more efficient to use as it presents a progress of the upgrade and also is transaction safe, requires less resources on the database, and causes a lesser peak in database size required. To publish the zarafa cache statistics to terminal and replacing the former SIGUSR1 signal, the statistics can now only be displayed by using: zarafa-stats --system. The use of the SIGUSR2 signal was removed in favor of a new command in line with other administrative command structures, to clear the internal zarafa cache issue the command: zarafa-admin --clear-cache. In this release we did one graphical update on the Webaccess login screen.
Please login to add feedback.
This update has been submitted for testing by robert.
This update has been pushed to testing
Big -1. Doesn't work: [root@luther ~]# zarafa-restart Stopping zarafa-server: [ OK ] Starting zarafa-server: [ OK ] Stopping zarafa- spooler: [ OK ] Starting zarafa-spooler: /usr/bin/zarafa-spooler: symbol lookup error: /usr/lib/libinetmapi.so.1: undefined symbol: ZTIN5vmime10exceptions14sasl_exceptionE [SELHALO] Stopping zarafa- monitor: [ OK ] Starting zarafa-monitor: Warning: Terminal locale not UTF-8, but UTF-8 locale is being forced. Screen output may not be correctly printed. [ OK ] Stopping zarafa-gateway: [ OK ] Starting zarafa- gateway: /usr/bin/zarafa-gateway: symbol lookup error: /usr/lib/libinetmapi.so.1: undefined symbol: _ZTIN5vmime10exceptions14sasl_exceptionE [SELHALO] Stopping zarafa- ical: [ OK ] Starting zarafa-ical: [ OK ] Also (from /var/log/zarafa/server.log): Thu Jun 30 15:16:28 2011: Listening for pipe connections on /var/run/zarafa Thu Jun 30 15:16:28 2011: Listening for TCP connections on port 236 Thu Jun 30 15:16:28 2011: Startup succeeded on pid 18515 Thu Jun 30 16:00:18 2011: Caught SIGABRT (6), out of memory or unhandled exception, traceback: Thu Jun 30 16:00:18 2011: 0x000000080e2b57 /usr/bin /zarafa-server(_Z7sigsegvi+0xa7) [0x80e2b57] Thu Jun 30 16:00:18 2011: 0x000000004b3400 [0x4b3400] Thu Jun 30 16:00:18 2011: 0x000000004b3416 [0x4b3416] Thu Jun 30 16:00:18 2011: 0x00000000cded71 /lib/libc.so.6(gsignal+0x51) [0xcded71] Thu Jun 30 16:00:18 2011: 0x00000000ce064a /lib/libc.so.6(abort+0x17a) [0xce064a] Thu Jun 30 16:00:18 2011: 0x00000000cd7df8 /lib/libc.so.6(__assert_fail+0xf8) [0xcd7df8] Thu Jun 30 16:00:18 2011: 0x00000008210a43 /usr/bin/zarafa- server(_ZN16ECFileAttachment6CommitEv+0x183) [0x8210a43] Thu Jun 30 16:00:18 2011: 0x00000008237f9b /usr/bin/zarafa- server(_Z16DeleteObjectHardP9ECSessionP10ECDatabaseP19ECAttachmentStoragejRSt4listI10DELETEITEMSaIS6_EEbS9+0x16fb) [0x8237f9b] Thu Jun 30 16:00:18 2011: 0x0000000823cd74 /usr/bin/zarafa- server(Z13DeleteObjectsP9ECSessionP10ECDatabasePSt4listIjSaIjEEjjbb+0x204) [0x823cd74] Thu Jun 30 16:00:18 2011: 0x0000000810b144 /usr/bin/zarafa- server(_Z15PurgeSoftDeleteP9ECSessionjPjS1_S1+0x1514) [0x810b144] Thu Jun 30 16:00:18 2011: 0x0000000810b886 /usr/bin/zarafa- server(_Z17SoftDeleteRemoverPv+0x1a6) [0x810b886] Thu Jun 30 16:00:18 2011: 0x000000007d39e9 /lib/libpthread.so.0(+0x69e9) [0x7d39e9] Thu Jun 30 16:00:18 2011: 0x00000000d920fe /lib/libc.so.6(clone+0x5e) [0xd920fe] Thu Jun 30 16:00:18 2011: When reporting this traceback, please include Linux distribution name, system architecture and Zarafa version. 3. When accessing I get in the browser only this (I think the error message might be wrong, caused by the above): Warning: date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are required to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /etc/zarafa/webaccess/config.php on line 153 Not Found: PHP mapi extension not found If you have upgraded zarafa, please restart Apache Zarafa WebAccess can't start because of incompatible configuration. Please correct above errors, a good start is by checking your '/etc/php.ini' file. Or if you wish, you can disable this config check by editing the file '/usr/share/zarafa- webaccess/config.php', but this is not recommend.
Better formatting than above is https://bugzilla.redhat.com/show_bug.cgi?id=717968
see the development on the bug ... with some reservations I have packaged zarafa working.
This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by robert.
This update has been pushed to stable