The OpenChange Server Reference

Introduction

This is the online reference for configuring mapiproxy and developing with the OpenChange server code:

  • Users will find documentation on how to setup mapiproxy, mapiproxy modules, openchange server, how to provision samba4 and openchange. User's documentation is tagged with the user icon.
  • Developers will find documentation on OpenChange server internals, design, architecture, implementation and API references. Developer's documentation is tagged with the box icon.

MAPIProxy documentation

mapiproxy_logo.png
MAPIProxy is an endpoint server for Samba4 which proxies ExchangeRPC traffic from MAPI clients (Outlook, openchangeclient, etc.) to Microsoft Exchange Server (and back). It can either act as a transparent proxy, for hacking, monitoring or debugging purposes or modify traffic on the fly and so provide new features. It is primarily developed for - but not limited to - third-party implementors looking for a development framework they can use for MAPI acceleration purposes.
userdoc.png
devdoc.png
Link to MAPIProxy documentation:

MAPIStore documentation

mapistore_logo.png

MAPIStore is the SAL component of OpenChange server. SAL stands for Storage Abstraction Layer. It is the component used by OpenChange Server to push/get information (messages, folders) to/from storage backends. The following document intends to describe the overall/theoretical SAL behavior and contraints we need to consider when dealing with MAPI/EMSMDB. It also describes the semantics and inner working of its storage backends.

devdoc.png
Link to MAPIStore documentation:

Creative Commons License
Creative Commons Attribution icon Creative Commons Share Alike icon
This content is licensed under the Creative Commons
Attribution ShareAlike License v. 3.0:
http://creativecommons.org/licenses/by-sa/3.0/