[Zarafa] Z-Push 2.1.1 has been built at RPM Fusion

Thu Dec 12 22:16:21 UTC 2013

Good evening,

Z-Push 2.1.1 has been built at RPM Fusion for Fedora 20, 19, 18 as well as
for Red Hat Enterprise Linux 6 and 5 - and should be pushed to the testing
updates repository likely before or at latest after christmas.

IMPORTANT: Even this is only a minor update, some manual work is required.

Upgrade from Z-Push 2.0.x to 2.1.x
==================================

- Stop your HTTP server, e.g. "service httpd stop"
- Note that mobiles devices might receive a temporary synchronization error
  (only visible if you explicitly click "refresh" on the mobile devices)
- Update your z-push files to the new version, e.g. "yum update 'z-push*'"
- Run upgrade script "php /usr/share/z-push/tools/migrate-2.0.x-2.1.0.php"
- Review the result output of the script; it can be run multiple times, but
  normally there is no need to do so
- Start your HTTP server again, e.g. "service httpd start"
- Mobile devices will continue synchronizing without any re-synchronization

Upgrade from Z-Push 1.x to 2.1.x
================================

https://lists.fedoraproject.org/pipermail/zarafa-announce/2012-November/000039.html

Z-Push 2.1.1 [1788]
===================

Important notes
---------------

There were several reports in the last weeks about broken meeting requests
where the "attendee becomes the organizer". Upstream could limit that to
the combination of Z-Push 2.0.8 and iOS 7. If you use these versions you
are strongly encouraged to update.

If your users see broken items in their calendars, there is a python script
available to fix these. You can get this script at:
http://svn.berlios.de/wsvn/z-push/trunk/tools/fix-meetings-2.0.8%2B2.1.0-ios7.py
Upstream doesn't give any support on this script. Use it at your own risk.

Upstream also had reports about several issues related with the BlackBerry
10 OS.
1. if you see "?" in a senders name on the mobile you should upgrade your
   BB firmware to version 10.2.0.415 or higher.
2. in replied or forwarded emails high characters are broken
3. in some occasions there was no body displayed on the mobile for emails
   with attachments
Issues 2 and 3 are fixed in this release.

Also the issue that if meeting request was sent from a mobile device, free
busy information in the organizer's calendar was not available in Outlook
or Webapp, has been fixed.

New features
------------

- ZP-460: Make max picture size configurable via the config file

General
-------

- ZP-455: Hierarchy Resync StatusException is not correctly processed
  during heartbeat
- ZP-456: FatalMisconfigurationException on a fresh 2.1.0RC installation
- ZP-458: Empty/Heartbeat removes states
- ZP-461: Notes that have been modified and synced with iOS7 contain html
  markup
- ZP-463: Galaxy Note 3 sends empty options tag in ItemOperations
- ZP-476: Wrong SyncXXXXRecurrence for dayOfWeek

Zarafa
------

- ZP-464: BB 10 does not show email body when mail has attachments
- ZP-465: Attendee is set as organizer with iOS7
- ZP-470: BB 10 high characters broken in replied/forwarded emails
- ZP-472: username is being shown when an item is created on a mobile
  device
- ZP-474: BB 10 sending â‚¬ sign eats high characters
- ZP-475: Email with meeting request responses sends wrong organizer to
  phone

Z-Push 2.1.0a [1776]
====================

Important notes
---------------

There were several reports in the last weeks about broken meeting requests
where the "attendee becomes the organizer". Upstream could limit that to
the combination of Z-Push 2.0.8/2.1.0 and iOS 7. If you use these versions
you are strongly encouraged to update immediately.

If your users see broken items in their calendars, there is a python script
available to fix these. You can get this script at:
http://svn.berlios.de/wsvn/z-push/trunk/tools/fix-meetings-2.0.8%2B2.1.0-ios7.py
Upstream doesn't give any support on this script. Use it at your own risk.

A detailed explaination of this issue can be found at the Zarafa community
hub:
https://community.zarafa.com/pg/blog/read/22607/ios-7-meeting-request-hijacking

Zarafa
------

- ZP-465: Attendee is set as organizer with iOS7

Z-Push 2.1.0 [1750]
===================

Notes
-----

Z-Push 2.1 contains several new features like S/MIME support and
administration features. Microsoft Windows 8 ActiveSync is now also
supported. There are various general fixes regarding S/MIME, BlackBerry 10
and calendaring. Zarafa 7.0.6 or later is required when the Zarafa backend
is used.

New features
------------

- ZP-36: Feature to resynchronize a single folder or folder type of a user
- ZP-43: Implement ValidateCert command
- ZP-44: Implement ResolveRecipients command
- ZP-45: Implement S/Mime
- ZP-237: Show if folders are fully synchronized in z-push-admin device
  details
- ZP-272: Command MoveItems should check if messages are in sync interval
- ZP-328: Proxied Z-Push could show remote IP instead of proxy IP
- ZP-379: Reply/Forward flags are not synced from the server to the mobile

General
-------

- ZP-196: Windows Sharepoint Services on Android 4.0.3 lead to multiple
  errors.
- ZP-231: Heartbeat with polling triggers full resync after incoming change
- ZP-243: Pass ContentParameters to Importer Interface
- ZP-265: Update copyright dates 2013
- ZP-273: ConfigContentParameters() has to be added to IImportChanges and
  all implementing importers
- ZP-298: Typo in namespaces of wbxmldefs.php (ValidateCerts instead of
  ValidateCert)
- ZP-299: Change backend file structure to allow better packaging
- ZP-300: From field get set to broken-from at z-push.local in saved draft
- ZP-302: Remove phone number from a contact on a mobile is not reflected
  to the server
- ZP-304: z-push-top creates log files as root
- ZP-308: Windows 8 sends different device ids for same client
- ZP-315: WBXML endtag processing of FolderSync
- ZP-322: Merge contribution - Mail_mimeDecode rebase to 1.5.5
- ZP-336: Status is missing in Settings->deviceinformation
- ZP-337: Example for specialLogUsers in config.php
- ZP-338: SGSII sends different user agents repeatedly
- ZP-339: z-push-admin: reports no devices found but devices are present
- ZP-340: Heartbeat connections log
  ProcessLoopDetectionPreviousConnectionFailed
- ZP-357: Migration tool should not be executable from the browser
- ZP-358: Migration tool creates user and settings file as root
- ZP-361: Server not overwritten with SYNC_CONFLICT_DEFAULT -
  SYNC_CONFLICT_OVERWRITE_SERVER
- ZP-362: Appointment appears twice on an android device
- ZP-369: Warnings in loop detection code
- ZP-370: Heartbeat response is followed by sync on all folders
- ZP-380: Implement EqualTo in Search
- ZP-383: SYNC_SEARCH_LONGID operation does not work
- ZP-384: Logging may use too much memory
- ZP-385: Duplicates from the device user agent history should be removed
- ZP-386: User log files should also contain the initial log lines
- ZP-389: If no pingable folders are found, an empty ping is stuck in
  checking policy changes only
- ZP-390: Some folders do not have a last synchronization time
- ZP-414: Null attachments flood the log file
- ZP-419: Typo in syncappointment.php
- ZP-425: z-push-admin: clean up functionality
- ZP-429: Force using the user certificate login on authentication
- ZP-433: Error "exporter not available status 12" when doing heartbeat on
  folders of different stores
- ZP-438: Non stop sync if no changes on empty sync
- ZP-447: WBXML exception when deleting mail from BB 10
- ZP-449: Race condition might invalidate HierarchyCache
- ZP-450: Errorlog always has an updated modification timestamp even
  without having new messages
- ZP-456: FatalMisconfigurationException on a fresh 2.1.0RC installation
- ZP-457: Windows phones are not able to sync

Zarafa
------

- ZP-53: Unable to resolve group or distribution list
- ZP-256: Remove obsolete SendMail code for older Zarafa versions
- ZP-260: Delegating meeting request are forwarded instead of delegated
- ZP-306: In the GAL search also lookup email address
- ZP-310: RTF formatted mail gets synced to device but can not modify
  content and forward
- ZP-341: Attachment from a meeting request is not available in calendar
- ZP-351: Task created in iOS 6 reminder app does not set owner name in
  WebAccess
- ZP-364: Forwarding an email loses attachments
- ZP-366: Typo in mapiprovider.php
- ZP-381: Remove unused functions required by previous versions of SendMail
- ZP-391: Downloading embedded attachment does not work
- ZP-416: Recurrent Meeting Request on iOS breaks
- ZP-418: CLONE - Changed note of an occurrence of a recurring appointment
  won't be synced to the mobile
- ZP-436: Issues with appointments on IOS 6.1.3
- ZP-441: Email flagged on an iPhone is without subject in task view
- ZP-442: Reminder still active for completed tasks
- ZP-445: S/MIME Mails with larger attachments are not able to be fully
  downloaded (on IOS)
- ZP-446: A contact's picture is not updated
- ZP-452: Reply/Forward on email of public folder does not work

IMAP
----

- ZP-448: Unconfigured IMAP_EXCLUDED_FOLDERS cause warnings

Finally I also want to say "thank you" to Zarafa Brazil for implementing my
suggestions and contributions upstream to allow more flexible RPM packages.

Another huge "thank you" goes to the ETES GmbH (www.etes.de) who allowed me
to prepare and perform this RPM package update during my working time. The
ETES GmbH is a longtime and experienced Zarafa partner - contact us in case
you need any kind of commercial Zarafa or Z-Push support.

You should be able to update to Z-Push 2.1.1 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/zarafa-announce/attachments/20131212/d3f02eb5/attachment.sig>