Thanks. Since I’m only using mapiproxy I’ll go ahead and try to add it.
One followup question. In addition to the configuration of the exising endpoints in dcesrv_mapiproxy.c(samba_init_module), separate shared objects in /usr/local/samba/modules/dcerpc_mapiproxy_server/ are loaded for these endpoints causing the following entries in the log. Are these actually being used if I’m only using mapiproxy? I’m unclear of the architecture. mapiproxy/libmapiproxy/dcesrv_mapiproxy_server.c:98(mapiproxy_server_register): MAPIPROXY server 'exchange_emsmdb' registered mapiproxy/libmapiproxy/dcesrv_mapiproxy_server.c:98(mapiproxy_server_register): MAPIPROXY server 'exchange_nsp' registered mapiproxy/libmapiproxy/dcesrv_mapiproxy_server.c:98(mapiproxy_server_register): MAPIPROXY server 'exchange_ds_rfr' registered From: Julien Kerihuel Sent: Wednesday, June 03, 2015 4:29 AM To: devel@lists.openchange.org Subject: Re: [openchange][devel] Proxying in AsyncEMSMDB On 03/06/15 06:38, Murray McCulligh wrote: Hi, I’m trying to get Outlook 2013 to communicate to Exchange 2010 via MAPIProxy. It seems to be failing after the call to EcDoAsyncConnectEx when it attempts to connect to the 5261574a-4572-206e-b268-6b199213b4e4 endpoint, which I believe is AsyncEMSMDB. I noticed that dcesrv_mapiproxy.c only contains code for the emsmdb, nsp and ds_rfr endpoints. So it would seem like AsyncEMSMDB should be added to this (samba_init_module function specifically). However in the makefile dce_mapiproxy and dce_asyncemsmdb seem to be peers in “mapiproxy” section. So maybe there is a different way I should be doing this. Hi, Indeed. The asyncemsmdb endpoint is independent from mapiproxy in the server architecture, hence the current distribution is: * mapiproxy: emsmdb, nspi, rfr * asyncemsmdb You will not be able to leverage mapiproxy as of today (without modifications) to handle asyncemsmdb. We encountered several constraints at the beginning of the development that has prevented us from integrating asyncemsmdb within mapiproxy. Mainly a workflow concern where mapiproxy had not a sufficient level of control to leverage bind/unbind operations and map/unmap the notification server. I assume that if you are only using mapiproxy, you should be able to add the endpoint without much problems. -- Julien Kerihuel j.kerih...@openchange.org OpenChange Project Founder Twitter: http://twitter.com/jkerihuel GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79 -------------------------------------------------------------------------------- _______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
_______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
