As always - please read the full Release Notes before upgrading
Added descriptive WARN message for unavailable shared folder
In isZimbraObjectInSyncInterval treat no response as false
Fix processing of zimbraMailAlias to handle string if exactly one alias
Fix ChangeMessage to strip input Categories from shared folder items
Renamed constructor function of mime.php, mimePart.php and z_RTF.php
Added hash to Primary folder stats to improve virtual folder change detection
Added logic to clear cache on Logoff where folder changes are detected
Updated comment and removed extra debug logging from recent fixes
As always - please read the full Release Notes before upgrading
Changes Made To Revision 67:
- Allow for iPxx device meeting modification request with shadow data
- Changed ZIMBRA_DEBUG logging of folder setup to only fire on word 'setup'
- Move GetMailboxSearchResults() Log line to avoid warning on no folder Id
- Tidy up logging in GetMailboxSearchResults()
- Add debug logging of unidentified incoming Timezone in ChangeMessage()
- unset $preModAppt->recurrence->premodtype after using it to fix type
- Log error and return false if GetMsgResponse is not present in response
- Add config.php option ZIMBRA_DISABLE_BIRTHDAY_SYNC
- Don't allow difference in dtstamp of appointment exceptions cause an issue
- Keep original Organizer for Tasks in ChangeMessage
- Check for service.PROXY_ERROR in Login and ChangesSink in multi-server setup
- If no Change Token is returned from CreateWaitSet then delay and return
- Updated comment on FakeOutbox
As always - Please read the full Release Notes before upgrading
Changes Made To Revision 66:
There are some recent changes to iOS 9.3.x and 10 that are breaking things in z-push. The z-push guys are fixing them as they are reported. However, some of these require backend changes. My old iPhone 4 cannot run these iOS releases so I am unable to test these issues/fixes.
If anyone has an old iPhone 5 lying around that they would like to donate for a good cause, please get in touch.
As always - please read the full Release Notes before upgrading
Changes Made To Revision 65:
Changes Made To Revision 64: z-push-2 version ONLY
These changes are for the z-push-2 version ONLY
The z-push-1 and as12.1 versions are still at Revision 54
Changes Made To Revision 63: z-push-2 version ONLY
These changes are for the z-push-2 version ONLY
The z-push-1 and as12.1 versions are still at Revision 54
Changes Made To Revision 62: z-push-2 version ONLY
These changes are for the z-push-2 version ONLY
The z-push-1 and as12.1 versions are still at Revision 54
Changes Made To Revision 61: z-push-2 version ONLY
These changes are for the z-push-2 version ONLY
The z-push-1 and as12.1 versions are still at Revision 54
Changes Made To Revision 61: z-push-2 version ONLY
These changes are for the z-push-2 version ONLY
The z-push-1 and as12.1 versions are still at Revision 54
Changes Made To Revision 60:
These changes are for the z-push-2 version ONLY
The z-push-1 and as12.1 versions are still at Revision 54
Changes Made To Revision 58:
These changes are for the z-push-2 version ONLY
NEW FOR RELEASE 56 - Use with z-push 2.0.7 or later
NEW FOR RELEASE 56 - An issue has been identified with the list sorting method utilized
by z-push in conjunction with zimbra. The basic sort method used in the diffstate.php
module (which Zimbra backend utilizes) is a numeric comparison. While this works fine
for a zimbra user with no shared folders - it does not work once the user has folder
shares in their sync floder list. Zimbra precedes the message IDs from shared folders with
the GUID of the sharing user. This GUID is non-numeric - so the sorting breaks down. This
can result in duplication of appointments/contacts/tasks when used in conjunction with
virtual folders on devices that need to virtually include all items into a single calendar/
contact list/task list. Devices that support multiple folders (such as iPxxx devices) are
not affected. Mail folders are unaffected as they all get synched individually. The
solution for this is to allow the sorting method to be overridden. I have requested a
change in z-push to allow this. In the meantime, a change is needed to the baseline
/lib/default/diffbackend/diffstate.php in the function RowCmp() to allow the sorting to
work correctly. The function should be changed as follows :-... read more
This is the first formal release for z-push-2
The download also includes updated backends for z-push-1 and the svn as12.1 branch
Release 52 has been uploaded to the main project downloads page.
In addition, the SVN has been updated with Release 52 for the z-push SVN "as12.1" branch.
A new branch, "z-push-2-alpha", has been added to the SVN for the z-push-2 version. This is a first alpha release and is FOR TESTING PURPOSES ONLY - NOT FOR PRODUCTION
Please use "z-push-2" Tracker to report any issues found in your testing. Thanks.... read more
If you cannot wait for z-push 2 to get HTML emails on your device, along with Email Search and Out-of-office functionality - check out the as12.1 branch in the SVN. When used in conjunction with the as12.1 branch in the z-push SVN it provides a richer ActiveSync experience. Please read all the notes in the README files.
Release 51 has been uploaded to the main project downloads page.
I have added an SVN branch for HTML email support. It is only in the SVN - not available as a download archive. Use the files in Code\SVN Browse\zimbra-backend\branches\as12.1 in conjunction with the z-push as12.1 branch from their SVN.
As we continue work on the Zimbra backend, it is coming more clear to me that we need some way that users can customize exactly what they want pushed to their device and how.
A Zimlet would be nice but involves a lot. What I envision that is what I think a simple solution is a PHP web page that the user logs into (verified against their ZImbra account), allows them to see all their folders in Zimbra (using SOAP to pull this information), allows the user to select which folders to include/exclude, and allows the user to set a few other options. All this information would then be stored in an XML file that the backend would load and use.... read more