today we have released the Z-Push 2.2.8 final version (tag 2.2.8, commit 208e6bbb8e38f4211b4a0afa077a3f8c4dd16163). Once again we thank all contributors for their work on this release.
This version contains some fixes and improvements.
The problem with the device trying to remove a message which was already removed on the server has been resolved.
This version also fixes the issue with LoopDetection getting stuck in some cases.
We added a backwards compatibility for ZCP 7.0.X versions and improved conflict detection for the Zarafa backend.
Autodiscover won’t generate a lot of warnings for PHP 5.4 and higher because of the timezone.
The full change log is available here.
The version is available at: http://download.z-push.org/final/2.2/.
Your feedback is highly appreciated.
Z-Push dev team
I installed the latest version 2.2.8, all right but with a detail in the log does not appear more authentication failure, it is affecting the operation of fail2ban, since I enabled TAG define ( ‘LOGAUTHFAIL’, true); yet the problem persists, in the log I see only the line:
03/04/2016 17:24:19  [FATAL] [ss] FatalNotImplementedException: Can not proceed without a device id. – Code: 0 – file: /srv/activesync/lib/core/devicemanager.php:92
is there anything I can do to solve this little problem ???
Thank you and sorry for bad English.
please post the Z-Push related question at the Z-Push forum: https://forums.zarafa.com/forumdisplay.php?75-Synchronising-%28mobile%29-devices-via-Z-Push