Good afternoon,
Z-Push 2.0.7 has been built at RPM Fusion for Fedora Rawhide, 18, 17 as well as for Red Hat Enterprise Linux 6 and 5 - and should be pushed to the testing updates repository within the next days at latest.
IMPORTANT: If you did not yet upgrade from Z-Push 1.5.x series, this is a major update which requires manual work, like configuration file changes: http://lists.fedoraproject.org/pipermail/zarafa-announce/2012-November/00003...
Z-Push 2.0.7 [1690] ===================
Notes =====
- In this version new features like the support for S/MIME signing and encryption/decryption of messages on the mobile have been implemented. - Reply/Forward flags sync from the server to the mobile was implemented. - Several fixes from 2.1 were also merged into this release - Heartbeat connections should work as expected now and not cause sync on every folder.
S/MIME ======
The following refers to Zarafa backend only: In order to use S/MIME for email signing and/or encryption on your mobile device there are some requirements. First of all you will need an email certificate. Acquiring it is beyond of the scope of this document. Configuring certifications in AD/LDAP is also not covered here but there are various sites covering it. Later the will be a more extensive configuration manual available. The private key must be imported to the mobile device. It can be achieved either sending yourself an email with the key or uploading it onto the storage card. The key must be in PKCS-format (.p12). It can be exported e.g. using windows mmc console. It is also possible to retrieve the key using Firefox certificates' backup (if you have installed the certificate using Firefox). Once you've imported it, in your active sync account settings there's security options where you can select the key. It might be possible that PHP functions require CA information in order to validate certs. Therefore the CAINFO parameter in the line 101 of config.php must be configured propertly. The public keys for encryption are retrieved either from the global address book or the contacts. In Active Directory the public key for contacts from GAB is saved in PR_EMS_AB_TAGGED_X509_CERT (0x8C6A1102) property and if you save a key in a contact it's PR_USER_X509_CERTIFICATE (0x3A701102). In LDAP public key for contacts from GAB is saved in userCertificate property. It should be mapped to 0x3A220102 in ldap.propmap.cfg (0x3A220102 = userCertificate). Make sure it looks like this in LDAP: userCertificate;binary:: MIIFGjCCBAKgAwIBAgIQbRnqpxlPa... Currently only Android 4.X and higher and iOS 5 and higher devices are known to support encryption/signing of emails.
New Features ============
- ZP-396: Merge into 2.0.x: Reply/Forward flags are not synced from the server to the mobile - ZP-401: Merge into 2.0.x: Implement S/MIME
General =======
- ZP-345: Merge into 2.0.x: Status is missing in Settings->deviceinformation - ZP-348: Merge into 2.0.x: Example for specialLogUsers in config.php - ZP-349: Merge into 2.0.x: SGSII sends different user agents repeatedly - ZP-354: From field get set to broken-from@z-push.local in saved draft - ZP-355: Heartbeat connections log ProcessLoopDetectionPreviousConnectionFailed - ZP-392: Merge into 2.0.x: User log files should also contain the initial log lines - ZP-393: Merge into 2.0.x: Warnings in loop detection code - ZP-397: Merge into 2.0.x: Update copyright dates 2013 - ZP-404: Merge into 2.0.x: SYNC_SEARCH_LONGID operation does not work - ZP-406: Merge into 2.0.x: Heartbeat response is followed by sync on all folders
Zarafa ======
- ZP-356: Delegating meeting request are forwarded instead of delegated - ZP-395: Merge into 2.0.x: Task created in iOS 6 reminder app does not set owner name in WebAccess - ZP-398: Merge into 2.0.x: RTF formatted mail gets synced to device but can not modify content and forward - ZP-399: Merge into 2.0.x: Attachment from a meeting request is not available in calendar - ZP-403: Merge into 2.0.x: Unable to resolve group or distribution list - ZP-405: Merge into 2.0.x: Typo in mapiprovider.php
You should be able to update to Z-Push 2.0.7 by using
yum update --enablerepo=rpmfusion-free-updates-testing '*z-push*'
on all Fedora and Red Hat Enterprise Linux releases once it's pushed to the repository. If you should find bugs or issues, please fill a bug report in RPM Fusion Bugzilla as described here:
http://fedoraproject.org/wiki/Zarafa#Bugs
Your feedback is very much appreciated.
Greetings, Robert