Nope - i checked. Everything is set to Berlin. Mailcow config, Sogo Settings and Linux Server

17 days later

The issue is due to an arithmetic overfow within outlook while sending the “new” event as mentioned in this comment of this bug ticket bugs.sogo.nu Icon 0005921: Oulook 2021 (365) stoped syncing via EAS with latest SoGo - SOGo | BTS

bugs.sogo.nu Icon bugs.sogo.nu
0005921: Oulook 2021 (365) stoped syncing via EAS with latest SoGo - SOGo | BTS
AndreyEversebastienqhivert

It is very annoying for us as well. Please vote for the issue to raise awareness on Microsoft side on the following two sites:

I think you are right! I upvoted it.

14 days later

Wohooo! It seems to be solved with the 2410 Update!

Hey @sut,
what Office Version exactly do you have? I just updated to the latest release

learn.microsoft.com
Update history for Microsoft 365 Apps (listed by date) - Office release notes
Provides IT Pros with a complete list of Microsoft 365 Apps releases, organized by date, with links to release notes.
Microsoft Learn
after your post but with my Office Professional Plus 2019 Version 2410 (Build 18129.20116) it ist stilll not working. Also still not working for a friend of mine with Office 365 and the same build.

Edit: Also what version of mailcow are you running? I’ve got version 2024-08a

Sorry - i am dumb…
I tested with the wrong account. I have one account with Caldav Synchronizer and one with eas. Eas still doesnt work.

Sorry for giving false hope.

Microsoft® Outlook® für Microsoft 365 MSO (Version 2410 Build 16.0.18129.20100) 64 Bit

Did you ever try the 32 Bit version? Works flawlessly for me

FYI, I just upgraded to

Microsoft® Outlook® für Microsoft 365 MSO (Version 2410 Build 16.0.18129.20100) 32 Bit

and tested the calendar sync both ways, works like a charm for me. But as I said, it’s the 32Bit version, I think we had this problem once in another thread which also used the 64Bit version

Thanks for the info @DocFraggle! It makes sense that it may only affect the 64bit version since the exception thrown is an arithmetic overflow. Could be a difference here with 64bit and 32bit version.

    Undecided9954 It makes sense that it may only affect the 64bit version since the exception thrown is an arithmetic overflow

    Yes, that could be possible. So give it a try then with the 32Bit version, waiting for an update 🙂

      No one is typing