Releases · TeamMsgExtractor/msg-extractor

v0.52.0

[TeamMsgExtractor #444] Fix typo in string that prevented HTML body from generating from the plain text body properly.
Adjusted the behavior of MSGFile.areStringsUnicode to prioritize the property specified by the parent MSG files for MSG files that are embedded. Additionally, added a fallback to rely on whether or not there is a stream using the 001F type to determine the property value if it is entirely missing.
Adjusted OleWriter.fromMsg() and MSGFile.export() to add the argument allowBadEmbed which helps to correct a few different issues that may appear in embedded MSG files. These corrections allow the embedded file to still be extracted and to open properly in Outlook.
In addition to the above, the errors that some of those corrections will suppress are now significantly more informative about what went wrong.

v0.49.0

[TeamMsgExtractor #427] Adjusted code for converting time stamps to create null dates for any time stamp beyond a certain point. The point was determined to be close to the existing null dates.
[TeamMsgExtractor #425] Added basic support for custom attachments that are Windows Metafiles.
Changed tolerance of bitmap custom attachment handler to allow for attachments with only a CONTENT stream. This change was made after seeing an example of a file that only had a CONTENT stream and no other streams for the custom data. The code now also tries to create default values for things previously determined from those other streams.
Fixed an issue in tryGetMimetype were the code didn't properly check if the data type was bytes (it only checked if it had a type).
Corrected some exports.
Added new ErrorBehavior value CUSTOM_ATTACH_TOLERANT to allow skipping checks for unused data that is normally validated.

Provide feedback