Zarafa Client for Outlook to Kopano: how long?

Good morning!

I know, it’s offically no longer supported to access Kopano with the last Zarafa Client for Outlook 365 integration. But, from my experience, it still works. It even works great!

I also understood (faulty?) that Kopano had to quit working on the Zarafa Connector, because Microsoft has set MAPI to deprecated (which I probably understood wrong. MS seems to have terminated MAPI-over-TCP, but still support MAPI-over-HTTP, as this is used by Exchange 2016).

My question is: what will be the point in time when I can no longer access Kopano using the Zarafa client? Is it already a risk to do so, for example, because it does not know about the current data structures on the server, or do I simply lose features of newer versions Outlook, as they can’t be transported to the server through the Zarafa client?

I did already encounter random crashes with newly patched Win7 and Win10 machines, but these affected only the updater - wich I can safely disable, because there will be no updates. Over all, I find Outlook-over-Zarafa-Client far more reliable than Outlook-over-z-push.

So, when can I expect that Outlook -> Zarafa-Client -> Kopano will no longer work?

Thank you very much!

Hi @itserv ,

@itserv said in Zarafa Client for Outlook to Kopano: how long?:

which I probably understood wrong. MS seems to have terminated MAPI-over-TCP, but still support MAPI-over-HTTP, as this is used by Exchange 2016

its not Mapi itself that has been deprecated, its the use of mapi32.dll. And this is the library the old Zarafa client uses for its integration. This was originally slated to be removed in Outlook 2016, but somehow still made the cut. Lets see how it will be in Outlook 2019…

@itserv said in Zarafa Client for Outlook to Kopano: how long?:

So, when can I expect that Outlook -> Zarafa-Client -> Kopano will no longer work?

We are not actively working on breaking compatibility, but we are also not testing it anymore. If you depend on it I’d suggest to test access before rolling it out to your customers.

Luckily enogh, it’s only for ourselves - not for our customers.

So it’s all about this library. Cool, thank you!

Hi all,

I installed Outlook 2016 yesterday and it does not launch anymore after installing the Zarafa Outlook connector. I think this is related to this version of Outlook (16.0.10228.20104). Older versions of Outlook 2016 still work. I realize this connector is not supported anymore but my client at this point is not willing to change his Outlook installations. I will try to get things working with Z-push , KOE and ActiveSync, but my Kopano sales rep pointed out that this is only supported to mailboxes up to 1 GB, which is not a lot in these times. I will report back with the results.

Hi @bcnx71,

there is no hard upper limit for the mailbox size to work. We had customers reporting that Outlook + KOE and Z-Push work with 10GB mailboxes. However there are more issues with larger mailboxes mainly because of Outlook’s ActiveSync implementation as it wasn’t meant to handle such amount of data. If possible, your users should limit the mailbox sync to 1 month in order to reduce the data size.

If you haven’t yet, take a look at our knowledge base article regarding KOE: https://kb.kopano.io/display/WIKI/Setting+up+the+Kopano+OL+Extension.

Manfred

Hi,

the 1 GB limit was mentioned to me by your sales rep Koos. We will see in the probably near future how the performance will be.
Mailbox sync to 1 month: does that mean that older mails are not even visible? That is not an option of course,

thx,

BC

Hi BC

Mailbox sync to 1 month: does that mean that older mails are not even visible? That is not an option of course,

Yes, if the sync is set to 1 month, on the initial sync the items older than 1 month won’t be synced. Later the items older than one month will be removed from Outlook.

Manfred

That is not a realistic business scenario. Which company does not need mails older than 1 month?

Anyway, I got the Zarafa connector working, apparently Outlook had a problem that was fixed by repairing the Office installation. For the time being we will continue to work like that. I finished the Z-push installation, so we are ready to switch to ActiveSync if needed.

BC