Kerio Connect 10.0.9

Good morning,
I installed / updated Kerio Connect Server on Mac mini to version 10.0.9 over the weekend
Now eM client looses a lot of mail by every start and starts synchronizing thousand of mails again
any idea what´s wrong???

Best regards

Andy, Germany

Now eM client looses a lot of mail by every start and starts synchronizing thousand of mails again
any idea what´s wrong???

Might need an updated version. What version of eM Client are you using ?

Also what type of account is it an IMAP or Exchange ?

Also is this happening with any other mail client or only eM Client ?

version em client is 10.4.4867 (a1d5549)
MacOS is 26.4
Kerio server 10.0.9 on MacMini 3,2 Ghz 6 Core i7 MacOS 15.7.5 ( latest possible)
32GB RAM
the account ist exchange account
Apple mail ist working fine
Kerio connect client ok

Andy

Ok as you then have the latest eM Client version and latest Mac OS version and works fine with Apple Mail, then you would need offical support to investigate your logs.

Could possibly be eg: Kerio connect 10.0.9 is not yet supported, or you might possibly need to adjust something on your mail server end for exchange setup.

So if you have a current active paid Pro, Personal or Business version then suggest to go to the VIP Support page and login and lodge a support ticket and link this thread. If you have run out of your support time you can get another 12months support ext via the following link VIP Support Extension | eM Client

Apart from that others on this free forum who use Kerio server might respond.

I have been having nothing but problems after upgrading to Kerio Connect 10.0.9. I have had to recreate profiles for many of my users who use ActiveSync. My server is crashing almost daily. I think this is a Kerio problem

This might be relevant to your issue.

From reading eM Client threads back in eg: 2024 on Kerio connection problems or crashing problems even with the older Kerio connect 10.0.5, that was traced back “directly with the Kerio EWS implementation which was bad” as @Michal_Burger posted in this thread link and users found “changing to an IMAP setup” fixed the problem as
@a.semenets posted below in that same thread.

So suggest to try an IMAP setup rather than EWS setup and see if that fixes it. Just a thought.