Hi,
I can confirm the problem in the Android-Gmail app for Android – EAS is broken in latest gmail-app update (Happened to 10+ customers in our environment). Temporary fix: We switched to Samsung Email Android App. Since they still didn't release a fix it is recommended that as many people as possible report the problem (Send Feedback) in the Gmail application (Gmail-App ->Menu Icon -> Help & feedback -> Send feedback). Br, Aris Dizdarević VCP-DCV|VMware Certified Professional, FCP-NS|Fortinet Certified Professional, CCT|Certified Cybersecurity Technician ISO 9001, ISO 14001, ISO 45001, IATF 16949|Certified Internal Auditor From: [email protected] <[email protected]> On Behalf Of Raffael Sent: Monday, December 1, 2025 8:25 PM To: [email protected] Subject: Re: [SOGo] ActiveSync problem I have sogo on iredmail. And I have the same problem. So it looks to me as well like a problem with Gmail. On 12/1/25 14:32, Terry Brummell ([email protected] <mailto:[email protected]> ) wrote: Also having problems with SOGo/Mailcow ActiveSync. For me, the problem started after a Gmail app update. I've since downgraded Gmail to make sync work again. On 2025-11-28 04:25, qhivert ([email protected] <mailto:[email protected]> ) wrote: Hello, I’m currently on different activesync problems so this is the right time! But please create an account on https://bugs.sogo.nu (then tell me because I have to manually give rights to your account) And create an issue there, it will be way easier to debug than here. Cheers, -- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache 69002 Lyon www.alinto.com <http://www.alinto.com> From: [email protected] <mailto:[email protected]> <mailto:[email protected]> <[email protected]> On Behalf Of Lars Kumbier Sent: vendredi 28 novembre 2025 09:55 To: [email protected] <mailto:[email protected]> Subject: [SOGo] ActiveSync problem Hey everyone, I've been using SOGo for the past years as part of the mailcow package for family and friends, and for the past few weeks, our android calendars are wreaking havoc. New events do not reach the online calendar, but get deleted on the next sync. This problem only happens on Android, and with different Android apps (tested Etar as well as Google Calendar). In both apps, the calendar events suddenly disappear (completely, including the ones that are on the server) and are then re-synced - overwriting the local storage and wiping out any events. This happens for the primary users calendar as well as shared calendars of other users. The SOGo version packaged is 5.12.3, and it seems that the ActiveSyncDispatcher decides to send an erroneous push-content command to the client (username and clientIP was replaced for privacy reasons), before the events from the Android device can be properly synced. Nov 28 09:27:51 82a45ece1c0c sogod [53]: <0x0x560ff9851550[WOHttpAdaptor]> notified the watchdog that we are ready [...] Nov 28 09:28:38 82a45ece1c0c sogod [53]: <0x0x560ff96b1b60[SOGoCache]> Cache cleanup interval set every 900.000000 seconds Nov 28 09:28:38 82a45ece1c0c sogod [53]: <0x0x560ff96b1b60[SOGoCache]> Using host(s) 'memcached' as server(s) Nov 28 09:28:38 82a45ece1c0c sogod [54]: <0x0x560ff9deccb0[NGImap4Client]> Note: no key found for sorting, using 'DATE': (null) Nov 28 09:28:39 82a45ece1c0c sogod [53]: <0x0x560ff9cb8db0[SOGoWebDAVAclManager]> entry '{DAV:}write' already exists in DAV permissions table Nov 28 09:28:39 82a45ece1c0c sogod [53]: <0x0x560ff9cb8db0[SOGoWebDAVAclManager]> entry '{DAV:}write-properties' already exists in DAV permissions table Nov 28 09:28:39 82a45ece1c0c sogod [53]: <0x0x560ff9cb8db0[SOGoWebDAVAclManager]> entry '{DAV:}write-content' already exists in DAV permissions table Nov 28 09:28:39 82a45ece1c0c sogod [53]: <0x0x560ff9a349b0[SOGoActiveSyncDispatcher]> Sleeping 45 seconds while detecting changes for user [email protected] <mailto:[email protected]> in Ping... [...] Nov 28 09:29:25 82a45ece1c0c sogod [53]: <0x0x560ff9a349b0[SOGoActiveSyncDispatcher]> Sleeping 45 seconds while detecting changes for user [email protected] <mailto:[email protected]> in Ping... Nov 28 09:29:38 82a45ece1c0c sogod [9]: [WARN] <0x0x560ff9958290[WOWatchDogChild]> pid 53 has been hanging in the same request for 1 minutes [...] Nov 28 09:30:10 82a45ece1c0c sogod [53]: <0x0x560ff9a349b0[SOGoActiveSyncDispatcher]> Change detected using Ping, we let the EAS client know to send a Sync. Nov 28 09:30:10 82a45ece1c0c sogod [53]: [ERROR] <0x0x560ff9837580[WOHttpTransaction]> client disconnected during delivery of response for <WORequest[0x0x560ff9596c00]: method=POST uri=/SOGo/Microsoft-Server-ActiveSync?Cmd=Ping&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android app=SOGo rqKey=Microsoft-Server-ActiveSync rqPath=(null)> (len=51): the socket was shutdown Nov 28 09:30:10 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Ping&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 51/327 91.502 - - 9M - 12 Nov 28 09:30:11 82a45ece1c0c sogod [53]: <0x0x560ff965f1a0[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:11 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 542/94 0.628 - - 684K - 13 Nov 28 09:30:12 82a45ece1c0c sogod [53]: <0x0x560ff96e34a0[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:12 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 77/59 0.079 - - 0 - 13 Nov 28 09:30:12 82a45ece1c0c sogod [53]: <0x0x560ff9cbd4c0[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:12 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 4858/94 0.450 - - 928K - 13 Nov 28 09:30:13 82a45ece1c0c sogod [53]: <0x0x560ff9cbccb0[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:13 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 75/57 0.040 - - 0 - 13 Nov 28 09:30:14 82a45ece1c0c sogod [53]: <0x0x560ff9c90110[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:14 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 5038/92 0.505 - - 4M - 13 Nov 28 09:30:15 82a45ece1c0c sogod [53]: <0x0x560ff9d56120[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:15 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 2761/100 0.368 - - 792K - 13 Nov 28 09:30:16 82a45ece1c0c sogod [53]: <0x0x560ff9867b20[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:16 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 76/58 0.058 - - 0 - 13 Nov 28 09:30:17 82a45ece1c0c sogod [53]: <0x0x560ff9c83ea0[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:17 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 554/93 0.185 - - 0 - 13 Nov 28 09:30:17 82a45ece1c0c sogod [53]: <0x0x560ff9a1e160[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:17 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 73/55 0.029 - - 0 - 13 Nov 28 09:30:18 82a45ece1c0c sogod [53]: <0x0x560ff97249e0[SOGoActiveSyncDispatcher]> Change detected during Sync, we push the content. Nov 28 09:30:18 82a45ece1c0c sogod [53]: 11.22.33.44 "POST /SOGo/Microsoft-Server-ActiveSync?Cmd=Sync&User=user0%40domain1.tld&DeviceId=androidc111111111&DeviceType=Android HTTP/1.0" 200 4387/90 0.312 - - 0 - 13 Nov 28 09:30:21 82a45ece1c0c sogod [53]: <0x0x560ff9d9e240[SOGoActiveSyncDispatcher]> Sleeping 45 seconds while detecting changes for user [email protected] <mailto:[email protected]> in Ping... [...] I see messages like this all over the place. This behavior is also consistent across different Android devices and versions. The update to 5.12.3 happened in October, and the problems have started appearing then. Config-wise, SOGoURLEncryption was enabled, no other sogo changes that I can see from the changelog: ## file: /var/lib/sogo/GNUstep/Defaults/sogod.plist <key>SOGoURLEncryptionEnabled</key> <string>YES</string> <key>SOGoURLEncryptionPassphrase</key> <string>${SOGO_URL_ENCRYPTION_KEY}</string> (source: https://github.com/mailcow/mailcow-dockerized/compare/2025-09b...2025-09c#diff-68f6a9b5f4588a9c9597d782de654b22e2dbbd62f8f36f9e6699226a3906adabR53-R56 ) Since this problem started to occur, the calendars have become effectively unusable on Android devices. I'm really at a loss of what to do next. Any help appreciated, my family is breathing down my neck... ;) Best, Lars Be careful with this message: it is coming from an external sender Do not open attachments nor click on links, unless you are sure that the content is safe Scanned by Alcad Security System
