zarafa-announce July 2011

zarafa-announce@lists.fedoraproject.org

1 participants
2 discussions

Zarafa 6.40.10 has been submitted for testing updates (EPEL 4 only)
by Robert Scheck 29 Jul '11

29 Jul '11

Good evening, Zarafa 6.40.10 has been submitted to the testing updates for EPEL 4 only. As mentioned something like a month ago, EPEL 4 will stay on 6.40 series until Red Hat Enterprise Linux 4 reaches end of lifetime at 2012-02-29. I recommend to upgrade to a newer version of Red Hat Enterprise Linux, if you would like to use Zarafa 7 and its new features. Here is the full list of changes in Zarafa 6.40.10 [28214]: Changelog 6.40.10 Final [28214] =============================== Backend: - Improvement: Archive on delivery, dagent can deliver a message to both the normal store and archive store. - Improvement: Zarafa-archiver --detach # to force detachment of an archive. - Improvement: Zarafa-archiver -L to list all users attached to a archive. - Fix #7826: python fails on unixtime(time.time()) in 6.40.x. - Fix #7792: Body of task request will get messed up in finish language.: - Fix #7847: Public folder not translated correctly in German. - Fix #7577: Update cache naming. - Fix #6203: Opening meeting request in ical will make it a not current meeting in Webaccess or Outlook. - Fix #6993: Zarafa-admin man page says you can add email address to groups with --update-group. - Fix #7499: Unable to change settings of a shared store without email address in ADS. - Fix #7521: Search via indexer on mailaddress is slow on large folders. - Fix #7548: BES can't see the difference between aliases and default email addresses. - Fix #7568: Segfault zarafa-server 6.40.7 during ldap down. - Fix #7577: Update cache naming. - Fix #7580: BES resolve breaks sometimes. - Fix #7604: Uninitialized memory in ECNamedProp::GetIDsFromNames. - Fix #7635: Man page zarafa-admin is out of date. - Fix #7638: Zarafa-license will fail when some old base files are found in license directory. - Fix #7641: Zarafa-admin --copyto-public doesn't work in multi-server setup. - Fix #7645: zarafa-ical segfault on 6.40.8 during curl ics import. - Fix #7672: Spooler does not process queue after receiving signal 1 (SIGHUP). - Fix #7699: Database error after copying a folder with (broken) message. - Fix #7666: zarafaAccount attribute is not part of zarafa-contact objectClass. - Fix #7726: Uninstall.sh doesn't uninstall zarafa correctly. - Fix #7820: Wrong version number in the windows installers. - Fix #7598: Deadlock on syncedmessages table when there is a large changes table. - Fix #7657: Blackberry Enterprise Server 5.0.3 doesn't work with Zarafa. - Fix #7732: Dagent will stop accepting email in lmtp after getting email for group without members. - Fix #7740: Segfault zarafa-ical 6.40.8. - Fix #7743: Zarafa archiver error detach archive of non-existing store. - Fix #7753: The archiver can fail for unclear reasons. - Fix #7755: GetServerDetails 'fails' when invalid flags are passed. - Fix #7756: licensed will give errors when ssl is configured wrong. - Fix #7763: spelling mistake in force resync option. - Fix #7770: Out of office may not work correctly in multiserver environment. - Fix #7782: Indexer does not index stubbed archived messages. Webaccess: - Fix #7464: Reminders of older recurring items pop-up after you delete an occurence in the future. - Fix #7693: Sending meeting request from public folder will bounce. - Fix #5720: Propose new time will duplicate after accepting the update. - Fix #7693: Sending meeting request from public folder will bounce.: - Fix #3316: Adressbook in dropdown in GAB is in English even when other language is selected. - Fix #6620: Add option to only send copy of meeting request only to delegate and not to me. - Fix #7094: Meeting request is seen as recurrence after accepting a new proposed time. - Fix #7104: Proposed new time not shown in scheduling tab when window is opend from propose new time mail. - Fix #7251: Webaccess no longer refreshes the message pane. - Fix #7268: Sub folders of the public folders will remain in English. - Fix #7449: New window loses focus on new email notification. - Fix #7462: Meeting request busy status is changed for the organizer, after the attendee accepts the meeting. - Fix #7464: Reminders of older recurrent items pop-up after you delete an occurence in the future. - Fix #7503: Able to send a meeting request in a shared calendar with view folder permissions only. - Fix #7519: Inline images will lose size and properties after they are moved to sent items folder. - Fix #7562: Unable to edit contact from webaccess when double clicking the contact in the GAB. - Fix #7630: Deleting all day meeting request will not ask to send update. - Fix #7665: Rules wizard available on the public folders. - Fix #7573: Meeting request not properly deleted by delegate. - Fix #7094: Meeting request is seen as recurring after accepting a new proposed time. - Fix #7104: Proposed new time not shown in scheduling tab. - Fix #7407: Zarafa-webaccess package in ubuntu repo does not contain fckeditor. You should be able to update to Zarafa 6.40.10 by using yum update 'zarafa*' on EPEL 4 once it's pushed to the repository. If you should find bugs or issues, please fill a bug report in Red Hat Bugzilla as described here: http://fedoraproject.org/wiki/Zarafa#Bugs Your feedback is very much appreciated. Greetings, Robert

1 0

Support for PHP 5.3 in RHEL 5 via new php53-mapi RPM package
by Robert Scheck 28 Jul '11

28 Jul '11

Good evening, Red Hat introduced with with Red Hat Enterprise Linux 5.6 a new PHP version for users, which whish to migrate to a more current PHP release. This new version was packaged as "php53" and replaces the regular "php" (PHP 5.1.x) if the user chooses to migrate. Unfortunately, PHP 5.1 and PHP 5.3 are ABI incompatible, that means that PHP modules that were compiled for PHP 5.1 can not be run using PHP 5.3. Every PHP module that shall work with PHP 5.3 needs to be recompiled from source. What does that mean for Zarafa? There is "php-mapi" which was compiled for PHP 5.1.x by default and thus you can not use Zarafa WebAccess or any other PHP MAPI related software which requires the PHP MAPI module - till today: Thanks to Erik Jacobs (who complained about this issue) and Matej Cepl (who did the Fedora Package Review), I am able to let you know that I submitted the new RPM package "php53-mapi" in Bodhi as an official update for EPEL 5. This new package is available until it has been pushed to the EPEL testing repository via Bodhi (via Koji) using the following URL: https://admin.fedoraproject.org/updates/php53-mapi-7.0.0-1.el5 If you use "php53" on RHEL 5 (or derivates) already, just get it and test it. And please add afterwards positive or negative karma to the package in Bodhi. Some notes for PHP 5.3 users on RHEL 5: It does not matter whether you use the PHP 5.3 RPM packages from RHEL 5 (or derivates) or these from the IUS Community Project. Things go even that far that you can use this php53-mapi RPM package together with the official Zarafa RPM packages - of course, it will be unsupported by Zarafa. But if you really have the need, you do not need to compile this extension any longer by yourself and you do not need to use some of the untrusted "mapi.so" binaries for PHP 5.3 that were made available by some people on the Internet. But there are caveats for now, if you want to use PHP 5.3 on RHEL 5: Due to a packaging bug of Red Hat, you need to install the "zarafa-webaccess" RPM package until Zarafa 7.0.1 using "rpm -Uvh --nodeps <package>". So starting with 7.0.1 final release, I will work around this issue by a hackish trick. Nevertheless, if you are also a "zarafa-z-push" or "z-push" user (from RPM Fusion), I have to disappoint that the packaging trick from WebAccess does not apply for Z-Push. Instead, please help to get the source of the issue fixed, the packaging bug in RHEL 5, by opening a "Service Request" in your Red Hat Network account. https://bugzilla.redhat.com/show_bug.cgi?id=717158 is the URL that needs to be mentioned in the ticket and if possible, please add also a comment to the bug report with the ID of the Service Request. As RHEL is mostly customer-driven, official requests from paying customers via the Red Hat customer portal are the best way to priorize this issue. And if you should find bugs or issues, please fill a bug report in Red Hat Bugzilla as described here: http://fedoraproject.org/wiki/Zarafa#Bugs Your feedback is very much appreciated. Greetings, Robert

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

zarafa-announce July 2011