Releases: TeamMsgExtractor/msg-extractor
Releases · TeamMsgExtractor/msg-extractor
Version 0.54.1
v0.54.1
- [TeamMsgExtractor #462] Fix potential issue where child MSG might have incompatible encoding to parent MSG when trying to grab a stream from the parent.
- Added code to attempt to significantly improve RTF deencapsulation times. This tries to strip away unneeded data before passing it to
RTFDE
. This shows improvements on all files that take more than one second. Currently, this actually fixes some files previously outputting wrong fromRTFDE
when deencapsulating the HTML body, specifically around non breaking spaces sometimes not transferring over.
Version 0.54.0
v0.54.0
- [TeamMsgExtractor #456] Changed the prepared html output to use plainly encoded HTML instead of prettified, since current prettification options used mangles the output and causes the output to sometimes be very large.
Version 0.53.2
v0.53.2
- [TeamMsgExtractor #452] Adjusted code to allow html encoding to be cached to try to speed up
bs4
operations. - [TeamMsgExtractor #453] Fixed handler for too large filetimes so that some filetimes being too large doesn't break the handler.
- Fixed a bug that would cause an error in task objects due to a lack of
enumerate
. - Fix
TOCEntry
not initializingDVTargetDevice
correctly. - Add temporary properties for
ContentID
toSignedAttachment
. AFAIK these can't ever be set, but this prevents errors in some places.
Version 0.53.1
v0.53.1
- Expanded allowable range for
red-black-tree-mod
. - Fix issue with
MessageBase.asEmailMessage()
that prevented embedded MSG files from being attached. - Expand allowable versions of
BeautifulSoup4
.
Version 0.52.0
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 the001F
type to determine the property value if it is entirely missing. - Adjusted
OleWriter.fromMsg()
andMSGFile.export()
to add the argumentallowBadEmbed
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.
Version 0.51.1
v0.51.1
- Add class type added in last version to known class types.
Version 0.51.0
v0.51.0
- [TeamMsgExtractor #401] Add basic support for MSG class type
IPM.SkypeTeams.Message
.
Version 0.50.1
v0.50.1
- [TeamMsgExtractor #434] Fix bug introduced in previous version.
Version 0.50.0
v0.50.0
- [TeamMsgExtractor #432] Adjust html header code to replace non-ascii characters with escaped versions. Also adujusted plain text to html conversion to ensure non-ascii character from the body are encoded to escpaed values to be safe.
- Made some corrections to
NullDate
.
Version 0.49.0
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
valueCUSTOM_ATTACH_TOLERANT
to allow skipping checks for unused data that is normally validated.