On Tue, 2010-01-26 at 10:31 +0200, Toni Koski wrote: > As you can see "lpszW_reduced" - field is changed as wanted. > Unfortunately this fields content is neither PR_CONVERSATION_TOPIC nor > PR_NORMALIZED_SUBJECT.
The lpszW_reduced you are referring to is actually dumped from the OpenMessage MAPI call response (exchange.idl:1251 TypedString NormalizedSubject). We actually don't save this value within the message object for further use) - and I think we should, to improve MUA quick mail summary display (e.g. evolution-mapi). In the meantime, if I refer to MS specs, [MS-OXCMSG] section 2.2.3.1.2.3 specifies that OpenMessage NormalizedSubject's string refers to "TypedString structure specifying the normalized subject of the Message object. Contains the value of the PidTagNormalizedSubject property." PidTagNormalizedSubject ([MS-OXPROPS] section 2.914 actually refers to the correct property which GetPropsAll should fetch. The only conclusion I can come up with so far is that if PR_NORMALIZED_SUBJECT is not available within GetPropsAll response (or somehow truncated), there may probably be some GetPropsAll side effect. Looks like something we have encountered long time ago - and which made us move from GetPropsAll to GetProps. One way to work around this and gets sure the problem comes from GetPropsAll would be to replaced the GetPropsAll call in openchangeclient.c:1795 with a GetProps call only including properties mapidump_* functions family are using. This would however have other side effects, but would be worthwhile. I'll update libmapi stack to use these OpenMessage information and introduces a --fetch-summary option in openchangeclient to give a proof of concept. Cheers, Julien. -- 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
