PS_INTERNET_HEADERS x-ms-journal-report named property missing for PST entry

Aspose.Email Product Family
1

Hi, we are using Aspose Email 24.10 for Java for processing PSTs. Extract the msgs, body, attachments, …

I’ve a PST that contains a so-called journal email. Basically, the outer email is an envelope with some journaling information. The actual (“journaled”) email is the attachment. Such a journal email can be detected by checking for the named property “x-ms-journal-report” with the PS_INTERNET_HEADERS GUID.

MFCMAPI displays the property like this:

Tag: 0x80A7001E
Type: PT_STRING8
DASL: http://schemas.microsoft.com/mapi/string/{00020386-0000-0000-C000-000000000046}/x-ms-journal-report
Named Prop Name: x-ms-journal-report
Named Prop Guid: {00020386-0000-0000-C000-000000000046} = PS_INTERNET_HEADERS

Problem: This property is missing in MapiMessage.getNamedProperties() when accessing the PST entry via PersonalStorage.extractMessage(byte[]).
I’ve also tried PersonalStorage.saveMessageToFile(String,String). Same result, property is missing.

The original entry in the PST contains 11 PSETID_Common named properties. One PS_INTERNET_HEADERS and one PSETID_Appointment property.
Aspose seems to extract only the PSETID_Common properties.

Is there some limitation around named properties?

I can provide the PST if needed.

2

@spfaff

It seems you are encountering an issue with missing named properties, specifically the “x-ms-journal-report” property, when processing PST files using Aspose Email for Java. This property is crucial for identifying journal emails, and its absence can hinder your ability to extract the necessary information.

Currently, it appears that Aspose Email may only be extracting certain named properties, specifically those associated with the PSETID_Common. If you are not seeing the “x-ms-journal-report” property in the results from MapiMessage.getNamedProperties() or when using PersonalStorage.extractMessage(byte[]), it could indicate a limitation in the library regarding the extraction of named properties.

To address this issue, you might want to consider the following steps:

  1. Check for Updates: Ensure that you are using the latest version of Aspose Email for Java, as updates may include fixes or enhancements related to named property extraction.

  2. Error Handling: Implement error handling in your code to capture any exceptions that may occur during the extraction process. This can help identify if there are issues with specific messages in the PST.

  3. Contact Support: If the problem persists, consider reaching out to Aspose support with your specific PST file. They may be able to provide insights or workarounds based on the internal workings of the library.

  4. Review Documentation: Check the Aspose Email documentation for any notes on limitations regarding named properties. This may provide additional context on what is supported.

If you have further questions or need assistance with specific code examples, feel free to ask!

Sources:
No specific sources were referenced in this response.

3

Hello @spfaff,

Thank you for reporting the issue and providing detailed information.
In order to investigate this further, we would kindly ask you to share the PST file.
This will allow us to analyze the issue.

4

JournalReports.zip (24.3 KB)

There should be only one item in it (Drafts folder). It’s entry id is 00000000AF83F5C6AAEFC04BB69EFA4218F8D90C24002000

5

@spfaff,

Thank you for providing the sample file.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): EMAILJAVA-35339