none
MS-OXTNEF: Meeting Request attribute 0x00060002 RRS feed

  • Question

  • While parsing Tnef messages that represents a meeting request, I came upon a message attribute with ID 0x00060002.

    However, according to MS-OXTNEF page 13, these are the only valid attribute IDs for messages:

    idMessageAttr = idMessageClass / idFrom / idSubject / idDateSent /
    idDateRecd / idMessageStatus / idMessageID /
    idBody / idPriority / idDateModified /
    idRecipTable / idOriginalMessageClass / idOwner / idSentFor /
    idDelegate / idDateStart / idDateEnd / idAidOwner / idRequestRes

    Which do not include the attribute I came upon (0x00060002).

    How can I decode this attribute?

    Thanks

    Wednesday, October 1, 2014 12:10 PM

Answers

  • Hi Majdoleen,

    The attribute you are looking for is documented in [MS-OXTNEF] — v20140721 section “2.1.3.3.18 attDelegate Attribute”.
    You couldn't find it because of a typo in [MS-OXTNEF] - v20140721 section "2.1.3.2 ABNF Description". The document states:
    ; PidTagReceivedRepresentingEntryId property ([MS-OXOMSG] section 2.2.1.25)
    idDelegate = %x00.02.06.00
    it should be:
    ; PidTagReceivedRepresentingEntryId property ([MS-OXOMSG] section 2.2.1.25)
    idDelegate = %x02.00.06.00

    I’ve submitted a bug report that this should be corrected.

    Thanks, Vilmos
    Thursday, October 16, 2014 8:29 PM

All replies

  • Hello Majdoleen Odeh,

    Thank you for your question. A member of the protocol documentation will respond to you soon.

    Best regards,
    Matt Weber | Microsoft Open Specifications Team

    Wednesday, October 1, 2014 1:37 PM
  • Hi Majdoleen Odeh,

    Thank you for your question. I am the engineer who will be working with you on this issue. I am currently researching the question and will provide you with an update soon.

    Regards,
    Vilmos Foltenyi - MSFT

    Thursday, October 2, 2014 6:02 PM
  • Hello Mr. Vilmos,

    Thank you for your effort. I came upon this attribute only on messages that represents meeting requests, I'm wondering also if I may face other attributes that are not mentioned in the document while decoding TNEF messages.

    Best regards,
    Majdoleen


    Friday, October 10, 2014 2:41 PM
  • Hi Majdoleen,

    Thank you for your patience. It would help to narrow down the usage of the property 0x00060002 if I could see the context it is used. Please make an unencrypted capture of the session and I’ll check it. Be sure that the capture doesn’t contain any confidential information; the capture will probably be small enough so you can send it as attachment to ‘dochelp (at) microsoft (dot) com’ and in the e-mail indicate that it is for me. If you have a tool for annotating the capture, please send the annotated version, too.

    Thanks, Vilmos

    Tuesday, October 14, 2014 6:04 AM
  • Hi Majdoleen,

    The attribute you are looking for is documented in [MS-OXTNEF] — v20140721 section “2.1.3.3.18 attDelegate Attribute”.
    You couldn't find it because of a typo in [MS-OXTNEF] - v20140721 section "2.1.3.2 ABNF Description". The document states:
    ; PidTagReceivedRepresentingEntryId property ([MS-OXOMSG] section 2.2.1.25)
    idDelegate = %x00.02.06.00
    it should be:
    ; PidTagReceivedRepresentingEntryId property ([MS-OXOMSG] section 2.2.1.25)
    idDelegate = %x02.00.06.00

    I’ve submitted a bug report that this should be corrected.

    Thanks, Vilmos
    Thursday, October 16, 2014 8:29 PM
  • Hi Mr. Vilmos,

    I really appreciate your efforts, thank you so much.

    Best Regards,
    Majdoleen

    Friday, October 17, 2014 3:36 AM