I think your post to Microsoft was perfect. Unfortunately, it looks like the
way this is heading is that there are differences between 2010 and non-2010.


Thanks
Chuck

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Friday, March 05, 2010 3:00 AM
To: [email protected]
Subject: devel Digest, Vol 34, Issue 5

Send devel mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://mailman.openchange.org/listinfo/devel
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of devel digest..."


Today's Topics:

   1. Re: Problem with OpenChange and exchange 2010 (Brad Hards)


----------------------------------------------------------------------

Message: 1
Date: Fri, 5 Mar 2010 11:51:25 +1100
From: Brad Hards <[email protected]>
To: Development list <[email protected]>,      Chuck Bohling
        <[email protected]>
Subject: Re: [openchange][devel] Problem with OpenChange and exchange
        2010
Message-ID: <[email protected]>
Content-Type: Text/Plain;  charset="iso-8859-1"

On Wednesday 03 March 2010 04:27:51 am Chuck Bohling wrote:
> 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.
It might not be considered a "regression". It might be considered a fix to
an 
existing bug. You can't really expect to set a property that is read-only
for 
the client.

> 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.
I'm not sure I absolutely understand which calls you're referring to,
because 
SetProps could be the OpenChange function, or the windows function. However 
I've tried to phrase this in terms of questions to Microsoft at
http://social.msdn.microsoft.com/Forums/en-
US/os_exchangeprotocols/thread/0616c747-ee6d-433d-a02b-4b6052789cf8

Please add / update that if you can add anything extra.

Brad


------------------------------

_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel


End of devel Digest, Vol 34, Issue 5
************************************

_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to