View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003955SOGoBackend Generalpublic2016-12-19 09:192016-12-19 14:44
Reporterbrunt82 Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
Status newResolutionopen 
Platform[Server] LinuxOSDebianOS Version8 (Jessie)
Product Version3.2.4 
Summary0003955: Incompatibility between SOGo and Z-Push
Description

Today I tried to use Z-Push with SOGo because of some synchronization errors while using the SOGo implementation of Exchange Active Sync (EAS). Besides Z-Push offers to assign policies to the devices. However.

With implementation of Z-Push 2.3.x it is possible to connect every CalDav/CardDav backend with Z-Push. Unfortunately there seems to be an incompatibility between SOGo 3.2.4 and Z-Push 2.3.x. Since 2.3.x Z-Push streams the bodies of mails and calendar entries directly from the input to the output to reduce the memory consumption.

There is a small description here:
https://forums.zarafa.com/showthread.php?12749-Backward-incompatibility-for-custom-backend-with-asbody-object-on-2-3-0

Would it be possible to "fix" this, because I think the combination of SOGo and Z-Push would be much better than using OpenChange.

Steps To Reproduce
  1. Install SOGo
  2. Install Z-Push and configure it to use SOGo as backend.
  3. Create an appointment on device (or server) and sync it.
  4. The server (or device) will not display the description of the appointment. Instead it will be synchronized something like "Resource id 0000087".
TagsNo tags attached.

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2016-12-19 09:19 brunt82 New Issue
2016-12-19 14:44 ludovic Severity major => feature