It is related to the zimbra backend. It is not relevant for autodiscover. If I get time I will look to see if I can hide that message if the backend is called from autodiscover.
Coming back to this topic I read in the autodiscover log the following line stating that the composer autoload is not found: [ INFO] [#unknown] Zimbra->Logon(): Composer autoload for halaxa/json-machine not found! - Setting _getMessageListUseRestApi for server to [false] [ INFO] [#unknown] ZPushAutodiscover->createResponse(): server URL: 'https://mail.website.it/Microsoft-Server-ActiveSync' [ INFO] [#unknown] ZPushAutodiscover->createResponse(): server URL: 'https://mail.website.it/Microsoft-Server-ActiveSync'...
Coming back to this topic I read in the autodiscover log the following line stating that the composer autoload is not found: 22/02/2026 01:06:08 [ 1459] [ INFO] [#unknown] Zimbra->Logon(): Composer autoload for halaxa/json-machine not found! - Setting _getMessageListUseRestApi for server to [false] 22/02/2026 01:06:08 [12362] [ INFO] [#unknown] ZPushAutodiscover->createResponse(): server URL: 'https://mail.website.it/Microsoft-Server-ActiveSync' 22/02/2026 01:06:08 [ 1459] [ INFO] [#unknown] ZPushAutodiscover->createResponse():...
I am seeing the exact same after updating to Outlook 2021. Oddly enough deleting *and editing appointments still works. edit: I just noticed this in z-push.log 20/02/2026 07:46:03 [ 4245] [ INFO] [user] Zimbra->GetMessageListRestApi(): START GetMessageListRestApi { folderid = f539201; zimbrafolderid = 539201; cutoffdate = 0; offset = 0 } 20/02/2026 07:46:03 [ 4245] [ INFO] [user] Zimbra->GetMessageListRestApi(): Appointments Not Being Handled by REST API - md field not available - Use SOAP } 20/02/2026...
I am seeing the exact same after updating to Outlook 2021. Oddly enough deleting *and editing appointments still works.
I am seeing the exact same after updating to Outlook 2021. Oddly enough deleting appointments still works.
Resolved. Just followed the release notes instructing how to run the composer command.
Hello I am on latest z-push and zimbra backend v.75 and in the log file I read a warning: /usr/share/z-push/backend/zimbra/zimbra.php:592 include(backend/zimbra/vendor/autoload.php): Failed to open stream: No such file or directory (2) /usr/share/z-push/backend/zimbra/zimbra.php:592 include(): Failed opening When looking into the /z-push/backend/zimbra directory I don' t have the 'autoload.php" file present. Am I missing some files or doing something wrong? Z-push is working fine apparently. Thank...
Hello I am on latest z-push and zimbra backend v.75 and in the log file I read a warning: /usr/share/z-push/backend/zimbra/zimbra.php:592 include(backend/zimbra/vendor/autoload.php): Failed to open stream: No such file or directory (2) /usr/share/z-push/backend/zimbra/zimbra.php:592 include(): Failed opening When looking into the /z-push/backend/zimbra directory I don' t have the 'autoload.php" file present. Am I missing some files or doing something wrong? Z-push is working fine apparently. Thank...
Support for Gmail 2025.11.02.828149635.Release
Client issue, now resolved. Closing ticket.
I confirm it works as expected. You can close this issue.
sync loop
Client issue, now solved by the latest update. Closing ticket.
I confirm, GMail version is 2025.12.01.843385623
mb_detect_encoding change charateristic
Final fix released in Release 74, with ZIMBRA_USE_MB_CHECK_ENCODING left in place even though it is not needed for the latest PHP versions. Closing ticket.
Z-Push creating too many SOAP requests from a single device
OP reported the issue was resolved. Closing ticket.
empty inbox after installing the latest version 2.7.1
No further updates. Closing ticket.
ZIMBRA_MALDUA_2FA config option
Closing ticket.
LoopDetection PHP FATAL
No further response. Closing ticket.
Gmail app searchs results only 10 mesages
Solution provided - and subsequently released. Closing ticket.
Question regarding JSON Machine package
Explanation provided. Closing ticket.
Calendar appointment sync issue
Fixed in Release 75.
The latest update to GMail appears to have fixed the issue. Please confirm
The latest update to GMail appears to have fixed the issue. Please confirm
The latest update to GMail appears to have fixed the issue. Please confirm
Marking as fixed. Closing
Calendar appointment issues with alert setting of "At time of event"
Interesting find .... almost 15 years later ... :-) The MS Spec says this is a number of MINUTES before an appointment to show a reminder. So for 5 minutes, zimbra returns the value as [0] => Array ( [neg] => 1 [m] => 5 [related] => START ) However, if you set the reminder to "At the time of the event" meaning 0 minutes before, for somereason zimbra returns it as a number of seconds - so 0 SECONDS before [0] => Array ( [neg] => 1 [s] => 0 [related] => START ) The code was not expecting that. A fix...
Great. Thanks for confirming
The latest update to GMail appears to have fixed the issue. Please confirm
Seeing this same behavior on Pixel 6 / Android 16 / Android-Mail/2025.11.09.830318519. Sync behavior is strange, email read-status/delete/move not working right but inbox sync with server-state works fine. Family members with Andoid-Samsung and Apple clients not seeing issues.
+1
It is probable that your issue has nothing to do with your Carbonio update. There appears to be an issue in the latest GMail clients https://support.google.com/mail/thread/388700940/
It is probable that your issue has nothing to do with your Carbanio update. There appears to be an issue in the latest GMail clients https://support.google.com/mail/thread/388700940/
Reverted the app back to 2025.01.05.71.. and the problem is gone.
@liverpoolfcfan thanks, I lost a lot of time debugging this. ps: wouldn't it make sense to add a note on the summary page about this? There are probably quite a lot of affected users.
You appear to be using the GMail client. There is an issue with the recent updates https://support.google.com/mail/thread/388700940/
sync loop
Documentation was updated to reflect that link. You can close this feature request. Thank you for this integration!
It is checked in to this folder https://sourceforge.net/p/zimbrabackend/code/HEAD/tree/zimbra-backend/misc/
Check in
I didn't want to have that document tied to a Release as I envisaged having to update it independently whenever you made changes to the Maldua projects. Maybe I can create a separate folder in the code repository for the non Release specific stuff.
So I would like to link to 'Adding-2FA-to-a-working-Zimbra-Z-Push-environment.txt' file from https://sourceforge.net/p/zimbrabackend/code/HEAD/tree/zimbra-backend/branches/z-push-2/ but it's not there. The file is not in https://sourceforge.net/p/zimbrabackend/code/HEAD/tree/zimbra-backend/release/75.1/ either. It's only found in the download links. Can you upload it there so that I can link to non-downloaded version of it from my documentation? Thank you!
Thanks for the link
Consider up-voting: https://support.google.com/mail/thread/388700940/
Someone already did - https://github.com/Z-Hub/Z-Push/issues/176
Let me know when I should create an issue at the Z-Push level. Thank you!
See also https://sourceforge.net/p/zimbrabackend/support-requests/196/ Certainly looks to be a GMail client issue at this time.
Z-Push is reporting Hierarchy Changes when it is trying to start Pinging the server 21/11/2025 10:32:25 [1491352] [ INFO] [myuser@mydomain] [androidc313717990] ExportChangesDiff->InitializeExporter(): Found '73' changes for 'hierarchy' This is causing a FolderSync and a full resync. I suspect this will need looking at by Z-Push. I will look closer myself when I get some time.
Gmail version '2025.11.02.828149635.Release' no longer syncs properly. Extra data: ZPUSH_VERSION is: 2.6.4+0-0 Z-Push Zimbra Backend Revision: 75 (75.1 actually because it includes the latest fix regarding ActiveSync Auth). ActiveSync Auth is not being used. Right now halaxa/json-machine is turned on but when it was turned off it did not work properly either.
Gmail version '2025.11.02.828149635.Release' no longer syncs properly. Extra data: ZPUSH_VERSION is: 2.6.4+0-0 Z-Push Zimbra Backend Revision: 75 (75.1 actually because it includes the latest fix regarding ActiveSync Auth). ActiveSync Auth is not being used.
Support for Gmail 2025.11.02.828149635.Release
I am going to reply, as I have also been having sudden issues om a ActiveSync with Android-Mail/2025.11.09.830318519.Release Gmail App clien, not being able or looping to sync mail messages. Keeps running the getting mail icon spinning and not syncing. I got the feeling it has to do with Gmail app, as the Outlook Android ap seem to be having its limited functionality. $ zmcontrol -v Release 10.0.16.GA.1001.UBUNTU20_64 FOSS edition. [root@zpush02 ~]# php --version PHP 8.2.29 (cli) (built: Jul 1 2025...
Just tested 75. Looks like this is fixed. Thanks, again!
Hi "Fan", I am running Zimbra 8.8.15. I have not upgraded anything because, "If it ain't broke, don't fix it.". My suspicion is a corruption in my Zimbra mail archive, but I have no idea how to reindex, and the AI chatbots all advise me with commands that do not work on 8.8.15. I REALLY don't want that "excitement" of upgrading Zimbra to the current open source version. My best strategy is PHP and z-push have evolved to ignore Zimbra fragility. I will take your advice to upgrade PHP. I know from...
"After years of quiet operation" ... Wow! You're not kidding - Backend Release 68 came out in May 2018! PHP 5.6.38 has been out of support for years. Which Zimbra release are you running? If possible, you should really update your setup to begin with. This is the new home of Z-Push - https://github.com/Z-Hub/Z-Push - 2.7.6 is the current release I suggest you use PHP 8.2 at a minimum
Which Release of the Zimbra backend are you using?
Caught in a sync loop, I think.
Good catch, Adrian. It would likely only affect completely new installations as the installer script does not modify the config.php file - it asks the installer to manually compare the settings. I have updated the code in the repo and in the tgz file just to be safe.
Good catch, Adrian. It would likely only affect completely new installations as the installer script does not modify the config.php file - it asks the installer to manually compare the settings. I have updated the code in the repo and in the tgz file.
Tag Release 75.1
Commented out
Release 75 has been just published - https://sourceforge.net/projects/zimbrabackend/files/Release75/ and it has the Maldua's 2FA support building. However you should revert this release or either release 75.1 or 76. // define('ZIMBRA_CUSTOM_AUTH_PAGE','ZetaActiveSyncAuthRequest'); has ended up in the final config.php as commented out. define('ZIMBRA_CUSTOM_AUTH_PAGE','ZetaActiveSyncAuthRequest'); which will make the installation to fail to anyone that does not have Maldua's ActiveSync Auth insta...
Tag Release 75
75
Better late than never. :D Thanks in advance for the fix.
Calendar appointment issues with alert setting of "At time of event"
Interesting find .... almost 15 years later ... :-) The MS Spec says this is a number of MINUTES before an appointment to show a reminder. So for 5 minutes, zimbra returns the value as [0] => Array ( [neg] => 1 [m] => 5 [related] => START ) However, if you set the reminder to "At the time of the event" meaning 0 minutes before, for somereason zimbra returns it as a number of seconds - so 0 SECONDS before [0] => Array ( [neg] => 1 [s] => 0 [related] => START ) The code was not expecting that. A fix...
Calendar appointment sync issue
I have no idea about how compatible Z-Push is with Carbanio. None of the info about Carbonio is helpful in tryng to debug the issue. From your info about ending up with lots of Dummy appointments, I would suspect that somehow your Calendar permissions have changed such that you have write access to create appointments but your Delete permission is gone so it is unable to delete them again. The Z-Push backend creates a dummy appointment in order to retrieve the configured timezone for the server/user....
Screenshot after sync has "finished"
Sync being weird after upgrade of Carbonio
Calendar appointment issues with alert setting of "At time of event"
Thanks for the explanation! I have installed the backend via your shell script which also installed json-machine. Enabled ZIMBRA_GETMESSAGELIST_USE_REST_API.
Sorry if the description wasn't clear. If you only upgrade to Release 74 over an existing release, it will continue to work as it previously did, using Soap requests for all folder enumerations (as well as other requests) If you upgrade to Release 74 AND do not install json-machine, it will continue to work as it previously did, using Soap requests for all folder enumerations (as well as other requests) If you upgrade to Release 74 AND install json-machine AND set ZIMBRA_GETMESSAGELIST_USE_REST_API...
Question regarding JSON Machine package
This will be added for Release 75
ZIMBRA_MALDUA_2FA config option
Tag Release 74