On Wed, 2007-08-29 at 00:02 +0200, Julien Kerihuel wrote: > If I create a folder with a slightly buggy dirclass such as IPF.Bug or > IPM.Buggy, then the folder will automatically turn IPM.Post. > > Conclusion: Until particular circonstances we'd need to focus on, we can > create folders browsable and usable/deletable with libmapi but useless > within Outlook [1]. Would you say it is a bug or a feature? ;)
Potential explanation: IPF refers to folders (container class) while IPM is for messages. In our example we create a folder, then set its PR_CONTAINER_CLASS with SetProps and set it to IPM which is *incorrect*. If we use existing OLE element (IPM.Appointment, IPM.Post, IPM.Note, IPM.Task), SetProps succeeds but taking a closer look to "All Public Folders" permissions show it is defined with custom properties and doesn't allow to create items. In the meantime when we specify IPM.Bug or any other non-existing stuff, it is automatically adjusted to default IPM.Post. My opinion, based on the information I've gathered, is that it is an Exchange related bug. It's not openchangepfadmin role to restrict PR_CONTAINER_CLASS. Question: rollback or keep the existing for Administrator convenience? -- Julien Kerihuel [EMAIL PROTECTED] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
