locked
PidTagPriority backwards in MS-OXCMSG? RRS feed

  • Question

  • The values for PidTagPriority in section 2.2.1.12 of MS-OXCMSG seem to be mixed up. Outlook Spy reports 0x1 as urgent, and 0xffffffff as non-urgent. Is the documentation correct?
    Monday, December 7, 2009 3:23 AM

Answers

  • Luke,

    You are correct as the table should be:

    Value

    Description

    0x00000001

    Urgent

    0x00000000

    Normal

    0xFFFFFFFF

    Non-Urgent

    I will file a Technical Document Issue (TDI) to have this fixed. 

    Thank you for your feedback.


    Developer Consultant
    Monday, December 7, 2009 5:49 PM

All replies

  • Hi Luke, thanks for your post regarding the [MS-OXCMSG] protocol specification. One of the Open Specification Documentation team will be in touch with you shortly. Thanks!

    Regards,
    Bill Wesse
    Monday, December 7, 2009 5:21 PM
  • Luke,

    You are correct as the table should be:

    Value

    Description

    0x00000001

    Urgent

    0x00000000

    Normal

    0xFFFFFFFF

    Non-Urgent

    I will file a Technical Document Issue (TDI) to have this fixed. 

    Thank you for your feedback.


    Developer Consultant
    Monday, December 7, 2009 5:49 PM