The modify time of the file is just the moment as the email account stop working, for example, right now both .lck files at 14:53.
I am running 24.5.2
The file in mailbox user is 46kb and the one in lockfiles has 0kb. Sometimes I can open the one in mailbox users: 2025-02-10T20:53:03.237Z
SessionID:27A6C848. the other one says that is locked and cannot be opened.
There are no errors in IMAP logs.
We have this issue with almost every user using ActiveSync. Right now just few users still use ActiveSync, I switched everyone to IMAP to avoid this situation.
250210 145302767 I [27A6C82C] 0x41330080 Connection: IP:52.96.40.173 SRV:mail.mobiltechglobal.com RM:POST SSL:On UA:Outlook-iOS-Android/1.0 QS:Cmd=Sync&User=margarita.contreras%40mobiltechglobal.com&DeviceId=73fa25d64a3f4b37a76e02d9738a1988&DeviceType=Outlook LNG:en CT=application/vnd.ms-sync.wbxml CL=103 TID:0x00021174
250210 145302767 I [27A6C82C] 0x41310044 Connection: Client Info: Outlook (73fa25d64a3f4b37a76e02d9738a1988)[14.0] PK:<not sent> MP:No CMD:0
250210 145302767 I [27A6C82C] 0x41330008 Authenticated: margarita.contreras@mobiltechglobal.com
250210 145302767 I [27A6C82C] 0x41310518 Operation: Sync
250210 145302772 I [27A6C82C] 0x4131169E CID:CI-00000000000000000000000000002 CSK:2025-02-10T20:44:27.436Z Get:Yes Submit:No
250210 145303174 I [27A6C82C] 0x4131160C CID:CI-00000000000000000000000000002 Server Items to Sync:1
250210 145303174 I [27A6C82C] 0x41311600 Add 1 items
In IMAP logs there are no info about that specific time, for that user.
The .lck file eventually removed by them self. With other users I saw the file stuck for hours until I restart webmail. But as I said before, I moved the users from ActiveSync to IMAP. There are just few still using ActiveSync.
When I got the report from this users, the first thing I asked was if she was using ActiveSync, but I was told that she was not. But today I found her account in ActiveSync client Management.
Here is link from my previuos post about this issue: https://mdaemon.com/community/forums/topic/114235/active-sync-synchronization-issues#post-249666
Thank you!