none
PidTagStoreSupportMask in MSG files RRS feed

  • Question

  • Hi.

    Over in MS-OXMSG it says that 'STORE_UNICODE_OK' is the only flag that is valid to set for this property in MSG files. Can you please confirm that this is up to date and still correct? I've seen a few MSG files that have other additional flags such as:

    STORE_ATTACH_OK
    STORE_CATEGORIZE_OK
    STORE_CREATE_OK
    STORE_ENTRYID_UNIQUE
    STORE_MODIFY_OK
    STORE_MV_PROPS_OK
    STORE_OLE_OK
    STORE_RTF_OK

    Thanks in advance!

    Cheers,

    Luke

    Wednesday, November 20, 2013 12:50 AM

Answers

  • Hi Luke,

    In your msg file PidTagStoreSupportMask has the value 0x00040E79. This does not contradict to the documentation.

    [MS-OXMSG] — v20131118 section 2.1.1.1 PidTagStoreSupportMask says
    “only the STORE_UNICODE_OK flag is valid. All other bits MUST be ignored.”
    and in the table
    STORE_UNICODE_OK is 0x00040000
    The documentation doesn’t say: All other bits MUST be zero.

    How was your sample msg file created?

    Thanks, Vilmos
    • Edited by Vilmos Foltenyi Tuesday, December 10, 2013 7:00 PM corrected Mask value
    • Marked as answer by Vilmos Foltenyi Thursday, December 12, 2013 6:12 AM
    Friday, December 6, 2013 6:28 PM
  • Hi Luke,

    Thanks for pointing out that the Mask value was wrong, I’ve already corrected it. The beginning of your property table can be seen below.

    The PidTagStoreSupportMask has the value 0x00040E79. Your MSG file was created by Outlook 2013, the 0x00000E79 bits were set by it.
    These bits should be considered opaque and are used internally by Outlook. They are not necessary for interoperability.

    Thanks, Vilmos

          Loop through array of 2.4.2.1 Fixed Length Property Entries
          Properties are defined in [MS-OXPROPS] — v20131118

          Property Entry (x10 bytes) from x3360
          0003360 40 00 07 30 02 00 00 00  A0 BC 7F 61 AC E5 CE 01  @..0......a....
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.645 PidTagCreationTime in UTC: 11/20/2013 4:52:57

          Property Entry (x10 bytes) from x3370
          0003370 40 00 08 30 02 00 00 00  A0 BC 7F 61 AC E5 CE 01  @..0......a....
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.753 PidTagLastModificationTime in UTC: 11/20/2013 4:52:57

          Property Entry (x10 bytes) from x3380
          0003380 03 00 F7 0F 02 00 00 00  00 00 00 00 00 00 00 00  ................
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.498 PidTagAccessLevel: 0
          [MS-OXCPRPT] — v20131118 '2.2.1.2 PidTagAccessLevel Property': Read-only

          Property Entry (x10 bytes) from x3390
          0003390 03 00 F4 0F 02 00 00 00  02 00 00 00 FE 07 00 00  ................
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.496 PidTagAccess: x00000002
          [MS-OXCPRPT] — v20131118 '2.2.1.1 PidTagAccess Property': Read

          Property Entry (x10 bytes) from x33A0
          00033A0 03 00 0D 34 02 00 00 00  79 0E 04 00 00 00 00 00  ...4....y.......
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.1018 PidTagStoreSupportMask: x00040E79
          [MS-OXMSG] — v20131118 '2.1.1.1 PidTagStoreSupportMask':
              STORE_UNICODE_OK (x00040000) is set
              The other bits MUST be ignored

    • Proposed as answer by Vilmos Foltenyi Wednesday, December 11, 2013 6:27 PM
    • Marked as answer by Luke Q Wednesday, December 11, 2013 10:14 PM
    Tuesday, December 10, 2013 10:35 PM

All replies

  • Hi Luke,

    I am the engineer who will be working with you on this issue. Please send the .msg file to me. Be sure that the file doesn’t contain any confidential information; the file is probably 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.

    Regards,
    Vilmos Foltenyi - MSFT

    Wednesday, November 20, 2013 4:21 AM
  • Hi Luke,

    Thank you for sending the msg file. I am still analyzing it. I hope soon I’ll have more information for you. Your patience is greatly appreciated.

    Thanks, Vilmos

    Wednesday, December 4, 2013 8:49 PM
  • Hi Luke,

    In your msg file PidTagStoreSupportMask has the value 0x00040E79. This does not contradict to the documentation.

    [MS-OXMSG] — v20131118 section 2.1.1.1 PidTagStoreSupportMask says
    “only the STORE_UNICODE_OK flag is valid. All other bits MUST be ignored.”
    and in the table
    STORE_UNICODE_OK is 0x00040000
    The documentation doesn’t say: All other bits MUST be zero.

    How was your sample msg file created?

    Thanks, Vilmos
    • Edited by Vilmos Foltenyi Tuesday, December 10, 2013 7:00 PM corrected Mask value
    • Marked as answer by Vilmos Foltenyi Thursday, December 12, 2013 6:12 AM
    Friday, December 6, 2013 6:28 PM
  • Hi Vilmos,

    It was just a new draft email created in Outlook 2013, and then dragged onto the desktop to save it.

    Looking in Outlook Spy the value seems to be different:

    Cheers,

    Luke

    Sunday, December 8, 2013 10:48 PM
  • Hi Vilmos,

    But I guess you've answered my question. So it is fine if those other flags are set, the should just be ignored.

    Just to clarify though, if we are creating a MSG file from scratch should any of those other flags get set if Outlook itself is setting them now?

    Cheers,

    Luke

    Sunday, December 8, 2013 10:52 PM
  • Hi Luke,

    Thanks for pointing out that the Mask value was wrong, I’ve already corrected it. The beginning of your property table can be seen below.

    The PidTagStoreSupportMask has the value 0x00040E79. Your MSG file was created by Outlook 2013, the 0x00000E79 bits were set by it.
    These bits should be considered opaque and are used internally by Outlook. They are not necessary for interoperability.

    Thanks, Vilmos

          Loop through array of 2.4.2.1 Fixed Length Property Entries
          Properties are defined in [MS-OXPROPS] — v20131118

          Property Entry (x10 bytes) from x3360
          0003360 40 00 07 30 02 00 00 00  A0 BC 7F 61 AC E5 CE 01  @..0......a....
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.645 PidTagCreationTime in UTC: 11/20/2013 4:52:57

          Property Entry (x10 bytes) from x3370
          0003370 40 00 08 30 02 00 00 00  A0 BC 7F 61 AC E5 CE 01  @..0......a....
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.753 PidTagLastModificationTime in UTC: 11/20/2013 4:52:57

          Property Entry (x10 bytes) from x3380
          0003380 03 00 F7 0F 02 00 00 00  00 00 00 00 00 00 00 00  ................
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.498 PidTagAccessLevel: 0
          [MS-OXCPRPT] — v20131118 '2.2.1.2 PidTagAccessLevel Property': Read-only

          Property Entry (x10 bytes) from x3390
          0003390 03 00 F4 0F 02 00 00 00  02 00 00 00 FE 07 00 00  ................
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.496 PidTagAccess: x00000002
          [MS-OXCPRPT] — v20131118 '2.2.1.1 PidTagAccess Property': Read

          Property Entry (x10 bytes) from x33A0
          00033A0 03 00 0D 34 02 00 00 00  79 0E 04 00 00 00 00 00  ...4....y.......
          [MS-OXMSG] — v20131118 '2.4.2.1 Fixed Length Property Entry' Flags:
              PROPATTR_READABLE
          2.1018 PidTagStoreSupportMask: x00040E79
          [MS-OXMSG] — v20131118 '2.1.1.1 PidTagStoreSupportMask':
              STORE_UNICODE_OK (x00040000) is set
              The other bits MUST be ignored

    • Proposed as answer by Vilmos Foltenyi Wednesday, December 11, 2013 6:27 PM
    • Marked as answer by Luke Q Wednesday, December 11, 2013 10:14 PM
    Tuesday, December 10, 2013 10:35 PM