Hello!

I am exploring the possibility of using mapiproxy to act as a gateway
between Outlook and a third-party groupware suite, translating MAPI RPC
messages to the third party groupware's API, thus allowing Outlook to
communicate with the groupware suite natively.

As I understand from the documentation, I would have to use mapiproxy in
proxy mode, and write a module which has the norelay option set on its
hooks, and it constructs the corresponding RPC message to the third-party
groupware server, then it receives the response and translates it to the
appropriate MAPI messages. I haven't looked at the sources yet, but based on
what I have read, this seems to be a straight-forward task.

However, I have some questions that I can't find the answer for, and I've
thought that I'd better ask the developers before spending days on finding
them. First, regarding the maturity of mapiproxy: does the current version
in the repository has all features developed that this gateway module would
need? When is the first stable release of mapiproxy to be expected?

And most importantly, I think that the most difficult problem with
implementing this module would be the authentication process, and whether or
not Samba is the domain controller is a cardinal question regarding this
issue. If Samba is the domain controller, then the correct way would be to
connect Samba's authentication database with the groupware suite's, so users
could log in to the domain with their groupware credentials. I suppose this
would'nt be too hard to accomplish, because Samba4 has a modular database
backend, am I right?

But what if I don't want to use Samba as a domain controller? How is
authentication handled in mapiproxy? Does it use Samba's authentication
backend? I have noticed that I couldn't log on to an Exchange server through
mapiproxy unless I had the same username for my Windows profile and for the
Exchange server. And in the example configuration at
mapiproxy.openchange.org, the username and password is "hard coded" in the
config file. Is it because mapiproxy's authentication component is not
written yet?

Thank you for your answers!
Regards,
Miklos Balazs
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to