@deisenlord said in outlook crashes at archive mails:
both of u refuse to man up and tell the OP it doesn’t work, isnt supported.
That’s a load of nonsense. Let’s get you on the same page: 1. Arguably there are some users for which it works, as @fb reported. 2. OP already knows his setup, for some reason, is not working at present; there is no need for us to tell him again what he already knows. 3. The debugging experience sucks, thanks to Outlook, or Windows in general, not being open source. Crashes can occur outside the context of zarafa6client, for example when a bad pointer from z6c is not immediately used, but kept for later, by outlook/mapi32.dll. Then the stack trace is totally useless. Because of that, investigating that path I consider not worth the time. 4. If zarafa6client works somewhere in some form, then switching the server side version ought not to change that situation. If it changed, that is something I would want to investigate.
These opinions and goals are my own. Those may not be shared by others, giving rise to the terms “(totally) unsupported” and “best effort only”.