I did some more investigation of this problem. Basically, I ran the same test on windows using the windows mapi client.
As expected, the test worked and the message was created on exchange. I tested with exchange 2003, 2007 and 2010. The call to IMAPIProp::SetProps succeeded and the problem count, returned by SetProps, was greater than zero. For any read-only prop, like PR_ACCESS, the returned problem code was MAPI_E_COMPUTED (0x8004011A). The call to IMAPIProp::SaveChanges returned MAPI_E_SUCCESS. Presumably, the windows mapi client uses the same MAPI/RPC as OpenChange. So what's interesting is that IMAPIProp:SetProps returns a non-zero problem count but OpenChange's SetProps does not. It returns zero problems. So, is there a different SetProps that windows uses? Or a flag or option that's not being set? Is it possible that after OpenChange's SetProps "successfully" sets some read-only props, exchange 2010's SaveChangesMessage fails because you can't set read-only props? It would be interesting to see what is being sent over the wire on windows. Do you have a network monitor that can interpret MAPI/RPC?
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
