How can we improve Kerio Connect?

Provide native Exchange Server compatibility in the server

It's been a few years since Microsoft released the MAPI documentation.

Although Kerio does provide an exchange connector, it would be better if there was native Exchange Server compatibility. It would mean that our Windows users could connect to Kerio Connect server without installing software on their machine.

The connector causes the following problems:
1. It uses memory and CPU resources
2. On big mailboxes, it just about kills disk access because it hogs so much (in some cases we've had to upgrade the client to use SSD because of Kerio)
3. It doesn't play nicely when the client needs to connect to other servers (especially true Exchange servers)
4. When we upgrade the server with a new version, a number of the clients don't upgrade automatically (they need to be told in advance how to get to the downloads etc so they can do it manually)

A number of Opensource projects (e.g. OpenChange, Zarafa, Zentyal) are already well on the way to providing native compatibility for Outlook. IMO Kerio is vastly superior to many/most of these solutions except when it comes to Outlook clients.

189 votes
Vote
Sign in
Signed in as (Sign out)
You have left! (?) (thinking…)
Roger IvyRoger Ivy shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

8 comments

Sign in
Signed in as (Sign out)
Submitting...
  • howiehowie commented  ·   ·  Flag as inappropriate

    I'm totally on board with this idea. What a shame this has been here for over two years, and no one from Kerio has commented on it.

  • Jan Lunddal LarsenJan Lunddal Larsen commented  ·   ·  Flag as inappropriate

    Native Exchange Server compatibility would also be a plus for using Kerio with various phone solutions that connects to Exchange for calendar info.

  • Jon NeillJon Neill commented  ·   ·  Flag as inappropriate

    Ronald - it is true that a user can connect to Kerio Connect via ActiveSync. However, there are significant limitations (some of which are due to Microsoft's implementation of protocol, not Kerio). The real point of this suggestion is for Kerio to offer full Exchange support, such that Outlook and other clients could connect to Kerio Connect as if KC were Exchange itself. In other words, the client is fooled into thinking it is connecting to a Microsoft Exchange server, while the admin gets the financial and functionality benefits of using Kerio Connect.

  • Ronald OttoRonald Otto commented  ·   ·  Flag as inappropriate

    With Outlook 2013 and later this works with Kerio BTW.
    You can connect Outlook with EAS to Kerio. FYI

  • James W HarringtonJames W Harrington commented  ·   ·  Flag as inappropriate

    I'm completely in agreement with this. We've been considering moving our hosting platform to Zentyal for exactly this reason. Openchange would revolutionise Kerio Connect and make a real and true Exchange alternative for business

Feedback and Knowledge Base