Hi,
in a test project we're exporting some sample messages from PersonalStorage like this:
Code:
Then we load the exported MSG files for further processing via an 3rd party library and it complains that the MSG files violate MSG specification, specifically - Property Stream was empty.
This is odd. We're able to open up the messages via double-clicking them and they do show up via Outlook reading window.
So we investigated a little bit further and after we exported the same messages via Outlook (Save As) and via MFCMapi - the 3rd party library accepted all those MSG files. So it seems like Aspose.Email isn't creating some required property stream.
I'm attaching the samples I've retrieved from the sample PST (which I can also provide if necessary). Please ignore "rendezvoused matador batching.msg" files - those have PR_MESSAGE_CLASS set to empty string to test some other problem - I just kept it there.
PS: I reached out also to the 3rd party library to get more details about which property stream is missing, but I do believe you can figure it out form the samples I included.
Thanks and best regards,
Michal
in a test project we're exporting some sample messages from PersonalStorage like this:
Code:
This works. We're able to observe the MSG files being written to the destination location.using (var src = PersonalStorage.FromFile(@"small_pst.pst", false)) { var folder = src.RootFolder.GetSubFolder("Inbox"); foreach (var messageEntryId in folder.EnumerateMessagesEntryId()) { var message = src.ExtractMessage(messageEntryId); var fileName = message.Subject; message.Save(string.Format(@"output\Aspose\{0}.msg", fileName)); } }
Then we load the exported MSG files for further processing via an 3rd party library and it complains that the MSG files violate MSG specification, specifically - Property Stream was empty.
This is odd. We're able to open up the messages via double-clicking them and they do show up via Outlook reading window.
So we investigated a little bit further and after we exported the same messages via Outlook (Save As) and via MFCMapi - the 3rd party library accepted all those MSG files. So it seems like Aspose.Email isn't creating some required property stream.
I'm attaching the samples I've retrieved from the sample PST (which I can also provide if necessary). Please ignore "rendezvoused matador batching.msg" files - those have PR_MESSAGE_CLASS set to empty string to test some other problem - I just kept it there.
PS: I reached out also to the 3rd party library to get more details about which property stream is missing, but I do believe you can figure it out form the samples I included.
Thanks and best regards,
Michal