What I would like is for the SetProps and SaveChangesMessage MAPI/RPC calls on exchange 2010 to work the way they do on 2003 and 2007. SaveChangesMessage fails on 2010 if SetProps sends read-only props. The call does not fail on 2003 and 2007. As far as I can tell, there is a regression in 2010. I don't think there is anything that openchange can do.
My previous emails were just explanations of what I had discovered as I investigated this problem. The equivalent windows test worked because the windows mapi client does not send read-only props. So, it appear that at this point, to use 2010, you cannot send read-only props. It is up to the app to determine what props are ok. Again, I don't think there is anything Openchange can do. Please let me know if I'm wrong. -----Original Message----- From: Brad Hards [mailto:[email protected]] Sent: Monday, March 01, 2010 10:55 PM To: Development list; Chuck Bohling Subject: Re: [openchange][devel] Problem with OpenChange and exchange 2010 On Tuesday 02 March 2010 01:29:49 pm Chuck Bohling wrote: > It looks like the windows mapi client doesnt send read-only prop like > PR_ACCESS to exchange in the SetProperties RPC call. It removes them from > the array thats sent then constructs the problem array with those removed > props as entries and probably any that are returned by the SetProperties > call. OK. Can you try to explain all of this in one email? I'm still a bit confused about which bits you are OK with, and what you're not OK with. Perhaps try to explain what behaviour you think is incorrect, and what you expect to happen instead. Brad No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.733 / Virus Database: 271.1.1/2718 - Release Date: 03/01/10 23:34:00 _______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
