build(deps): bump extract-msg from 0.48.7 to 0.49.0

[dependabot[bot]]

Bumps extract-msg from 0.48.7 to 0.49.0.

Release notes

Sourced from extract-msg's releases.

Version 0.49.0

v0.49.0

• [[TeamMsgExtractor #427](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/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](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/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.

Changelog

Sourced from extract-msg's changelog.

v0.49.0

• [[TeamMsgExtractor #427](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/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](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/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.

v0.48.7

• [[TeamMsgExtractor #420](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/420)] Fixed typo introduced in last version.

v0.48.6

• [[TeamMsgExtractor #417](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/417)] Fixed issues with openMsg where some corrupted MSG files could end up throwing an uncaught exception and leaving the file handle open.

v0.48.5

• [[TeamMsgExtractor #414](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/414)] Fixed typo in message_signed_base.py.

v0.48.4

• [[TeamMsgExtractor #411](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/411)] Fix console script throwing error due to changed console args not defaulting.

v0.48.3

• [[TeamMsgExtractor #409](https://redirect.github.com/TeamMsgExtractor/msg-extractor/issues/409)] Added missing private method to SignedAttachment.
• Fixed some missing typing information.

v0.48.2

• Fixed bugs with MessageBase.asEmailMessage(). Numerous improvements to how it handles the data.

v0.48.1

• Added an option (-s, --stdin) to the command line to take an MSG file from stdin. This allows the user to pipe the MSG data from another program directly instead of having to write a middleman that uses the extract-msg library directly or having to write the file to the disk first.
• Changed main function to allow for manual argument list to be passed to it.
• Added attributes to AttachmentBase for creation and modification time. These can be accessed through createdAt or creationTime and lastModificationTime or modifiedAt.
• Changed OleWriter tests to output the name of the test file being done if an error occurs.
• Added tests for some command line stuff.

v0.48.0

• Adjusted error handling for named properties to handle critical streams being missing and to allow suppression of those errors.
• Adjusted error handling for named properties to allow silencing of errors caused by invalid references to the name stream. If ErrorBehavior.NAMED_NAME_STREAM is provided to the MSGFile instance, a warning will be logged and that entry will simply be dropped.
• Adjusted error handling for signed messages to better check for issues with the signed attachment. This should make errors from violating the standard much easier to understand. These errors can be ignored, but the attachment will not be parsed as a signed attachment.
• Minor docstring updates.
• Minor adjustments to OleWriter to prepare the code for being able to write version 4 files. Version 3 files are currently the only one's supported, but much of the code had hard-coded values that could be replaced with variables and small conditionals. This will have very little performance impact, and should not be noticeable.
• Improved comments on OleWriter to make private sections more understandable.
• Changed MessageSignedBase._rawAttachments to MessageSignedBase.rawAttachments to provide non-private access in a reliable way.

v0.47.0

• Changed the public API for PropertiesStore to improve the quality of its code. The properties type is now mandatory, and the intelligence field (and the related enum) has been removed.
  • Additionally, the toBytes and __bytes__ methods will both generate based on the contents of this class, allowing for new properties to be created and for existing properties to be modified or removed if the class is set to writable on creation.
• Added new method Named.getPropNameByStreamID. This method takes the ID of a stream (or property stream entry) and returns the property name (as a tuple of the property name/ID and the property set) that is stored there. Returns None if the stream is not used to store a named property. This name can be directly used (if it is not None) to get the NamedPropertyBase instance associated. This method is most useful for people looking at the raw data of a stream and trying to figure out what named property it refers to.
• Fixed mistake in struct definitions that caused a float to require 8 bytes to unpack.
• Added tests for extract_msg.properties.props.
• Added basic tests for extract_msg.attachments.

... (truncated)

Commits

• aeea79b Merge pull request #428 from TeamMsgExtractor/next-release
• 30a28d8 Merge branch 'next-release' of https://github.com/TeamMsgExtractor/msg-extrac...
• aba140e Remove unused import
• 2889cc5 Fixed extension for metafiles
• a3b353c Fix typo
• f050767 Fix imports
• e6e6172 Fixed issue with null date for large values not having filetime
• aadc8f5 FIxes, new error behavior addition
• 755c5d0 Fix exports
• d7715a5 upload progress
• Additional commits viewable in compare view

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
extract-msg	[>= 0.40.a, < 0.41]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)