Hello, On mar, 2015-06-09 at 14:56 +0000, nerdl...@comcast.net wrote: > I understand that this is not really what this list is for. If there > is a better forum, please let me know. > I think you posted the question in the right place. > > I want to develop a program running on a Linux box that extracts > information (folder counts, email headers, etc) from an Exchange > server. It would appear that mapiproxy would allow that, even if it > is not exactly it's intended purpose. > The MAPI client library is called libmapi and it can serve to build up a MAPI client. There are, at least, three programs that acts as MAPI clients in OpenChange code tree.
* mapitest: To test MAPI operations against a MAPI server like OpenChange or Exchange Server. * openchangeclient: it is a CLI standalone MAPI application [0] * mapiprofile: a CLI application to set up MAPI profiles. Likewise Mail application in Windows, it creates and manages MAPI profiles. > > I have been reading the documentation selectively, trying to pick out > what I need and what I can skip, and apparently making a hash out of > it. You can read libmapi C code to know how to build up your application and check what other programs do like utils/openchangeclient.c or utils/mapitest/modules/*.c. Using the latter, you have to know Exchange protocols but the documentation may be good enough. > > Is there an instruction set that addresses this limited use? Which > parts are needed in this case? I am unsure where the samba piece fits > in this scenario. samba is not required but its libraries to build up your application, see how openchangeclient or mapitest are built. > Any guidance is appreciated. Don't hesitate to ask further if you have any doubt. Best, [0] http://tracker.openchange.org/projects/openchange/wiki/HowTo_Setup_OpenChange_Client --- sixstone _______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel