chore(deps): bump extract-msg from 0.41.5 to 0.45.0

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Bumps extract-msg from 0.41.5 to 0.45.0.

Release notes

Sourced from extract-msg's releases.

Verison 0.45.0

v0.45.0

• BREAKING: Changed parsing of string multiple properties to remove the trailing null byte. This will cause the output of parsing them to differ.
• Updated typing information for some functions and classes.
• Fixed a bug with MessageSignedBase.attachments that would cause it to return None instead of an empty list if the number of normal attachments was 0 was the error behavior was set to ignore violations of the standard.
• Updated MessageSignedBase.attachments to use functools.cached_property instead of property.
• Fixed spelling errors in some exception strings.
• Made NamedPropertyBase a subclass of abc.ABC.
• Cleaned up some of the code for named properties to remove unused variables and remove inefficient code.
• Changed PropBase to be a subclass of abc.ABC.
• Added detailed versioning info to the README.
• Deprecated many private functions, including methods on many of the classes. Of primary note are _getStream and _getStringStream, which have been moved to the public API as getStream and getStringStream. Any deprecated functions still exist and will forward to a public API function if they are not being removed. Additionally, all internal usage of them has been removed. This change is one of the big preparations that is needed for the 1.0.0 release.
  • As mentioned, a number of these deprecated functions have been moved to the public API. It is recommended that you run tests with your code after enabling deprecation warnings to see what should be changed.
• Removed items deprecated in or before 0.42.0.
• Changed the API for the private method _genRecipient. This is not intended for use outside of the module except for subclasses. The change removed the allowance of ints for the second argument, requiring that it be a valid enum type.
• Convert many enum types to IntEnum.
• Extended functionality of PropertiesStore to allow for integer property names and getting a property based on just the ID. You can also get a list of all properties that use a given ID.
• Added new function PropertiesStore.getProperties which gets a list of all properties matching the property ID. Return type is a list of PropBase instances.
• Added new function PropertiesStore.getValue which looks for the first matching FixedLengthProp and returns the value from it.
• Improved internal code related to getting a property with a potentially unknown type.
• Added a number of entirely new functions to the public API on MSGFile, AttachmentBase, PropertiesStore, and Recipient objects:
  • getMultipleBinary: Gets a multiple binary property as a list of bytes objects.
  • getSingleOrMultipleBinary: A combination of getStream and getMultipleBinary which prefers a single binary stream. Returns a single bytes object or a list of bytes objects.
  • getMultipleString: Gets a multiple string property as a list of str objects.
  • getSingleOrMultipleString: A combination of getStringStream and getMultipleString which prefers a single string stream. Returns a single bytes objecct or a list of bytes objects.
  • getPropertyVal: Shortcut for instance.props.getValue that allows new behavior to be added by overriding it.
  • getNamedProp: Shortcut for instance.namedProperties.get((propertyName, guid), default) that allows new behavior to be added by overriding it.
• Removed Named._getStringStream and Named.sExists. The named properties storage will always use regular streams and not string streams.
• Changed all Named methods to no longer have a prefix argument. The prefix should always be false sense the named property mapping will only exist in the top level directory.
• Adjusted tryGetMimeType to allows any attachments whose data property would return a bytes instance.
• Changed internal code to use public API functions wherever possible. This includes making many private API functions use calls to the public API for getting bits of data.
• Fixed potential issue with AttachmentBase.clsid which had the potential to cause some attachments to fail to generate a CLSID.
• Outright removed or changed a significant portion of the private API. I have rarely, if ever, seen references to these parts, so this should cause you no issues. Some of these have also been moved to the public API, either identically or with changes, and the mapping is as such:
  • _getNamedAs -> getNamedAs: Changed to always require a conversion argument. If you were previously using it to plainly get a named property or to handle the properly being None or a real value, you should use the return value of getNamedProp instead.
  • _getPropertyAs -> getPropertyAs: Same as above, use getPropertyVal instead for None or plain access.
  • _getStreamAs -> getStreamAs, getStringStreamAs: Once again, see above. Use getStream and getStringStream, respectively.

Version 0.44.0

v0.44.0

• Fixed a bug that caused MessageBase.headerInit to always return False after the 0.42.0 update.
• Changed MessageBase.headerInit to a property.
• Fixed extract_msg.utils.__all__.
• Minor regoanization within extract_msg/utils.py.
• Minor changes to docstrings.
• Minor README updates.
• Fix issue with folded header fields decoding incorrectly when given to extract_msg.utils.decodeRfc2047.

Version 0.43.0

v0.43.0

• [[TeamMsgExtractor #56](https://redirect.github.com/interface to stdlib interfaces TeamMsgExtractor/msg-extractor#56)] [[TeamMsgExtractor #248](https://redirect.github.com/Support for returning an EmailMessage object TeamMsgExtractor/msg-extractor#248)] Added new function MessageBase.asEmailMessage which will convert the MessageBase instance, if possible, to an email.message.EmailMessage object. If an embedded MSG file on a MessageBase object is of a class that does not have this function, it will simply be attached to the instance as bytes.

... (truncated)

Changelog

Sourced from extract-msg's changelog.

v0.45.0

• BREAKING: Changed parsing of string multiple properties to remove the trailing null byte. This will cause the output of parsing them to differ.
• Updated typing information for some functions and classes.
• Fixed a bug with MessageSignedBase.attachments that would cause it to return None instead of an empty list if the number of normal attachments was 0 was the error behavior was set to ignore violations of the standard.
• Updated MessageSignedBase.attachments to use functools.cached_property instead of property.
• Fixed spelling errors in some exception strings.
• Made NamedPropertyBase a subclass of abc.ABC.
• Cleaned up some of the code for named properties to remove unused variables and remove inefficient code.
• Changed PropBase to be a subclass of abc.ABC.
• Added detailed versioning info to the README.
• Deprecated many private functions, including methods on many of the classes. Of primary note are _getStream and _getStringStream, which have been moved to the public API as getStream and getStringStream. Any deprecated functions still exist and will forward to a public API function if they are not being removed. Additionally, all internal usage of them has been removed. This change is one of the big preparations that is needed for the 1.0.0 release.
  • As mentioned, a number of these deprecated functions have been moved to the public API. It is recommended that you run tests with your code after enabling deprecation warnings to see what should be changed.
• Removed items deprecated in or before 0.42.0.
• Changed the API for the private method _genRecipient. This is not intended for use outside of the module except for subclasses. The change removed the allowance of ints for the second argument, requiring that it be a valid enum type.
• Convert many enum types to IntEnum.
• Extended functionality of PropertiesStore to allow for integer property names and getting a property based on just the ID. You can also get a list of all properties that use a given ID.
• Added new function PropertiesStore.getProperties which gets a list of all properties matching the property ID. Return type is a list of PropBase instances.
• Added new function PropertiesStore.getValue which looks for the first matching FixedLengthProp and returns the value from it.
• Improved internal code related to getting a property with a potentially unknown type.
• Added a number of entirely new functions to the public API on MSGFile, AttachmentBase, PropertiesStore, and Recipient objects:
  • getMultipleBinary: Gets a multiple binary property as a list of bytes objects.
  • getSingleOrMultipleBinary: A combination of getStream and getMultipleBinary which prefers a single binary stream. Returns a single bytes object or a list of bytes objects.
  • getMultipleString: Gets a multiple string property as a list of str objects.
  • getSingleOrMultipleString: A combination of getStringStream and getMultipleString which prefers a single string stream. Returns a single bytes objecct or a list of bytes objects.
  • getPropertyVal: Shortcut for instance.props.getValue that allows new behavior to be added by overriding it.
  • getNamedProp: Shortcut for instance.namedProperties.get((propertyName, guid), default) that allows new behavior to be added by overriding it.
• Removed Named._getStringStream and Named.sExists. The named properties storage will always use regular streams and not string streams.
• Changed all Named methods to no longer have a prefix argument. The prefix should always be false sense the named property mapping will only exist in the top level directory.
• Adjusted tryGetMimeType to allows any attachments whose data property would return a bytes instance.
• Changed internal code to use public API functions wherever possible. This includes making many private API functions use calls to the public API for getting bits of data.
• Fixed potential issue with AttachmentBase.clsid which had the potential to cause some attachments to fail to generate a CLSID.
• Outright removed or changed a significant portion of the private API. I have rarely, if ever, seen references to these parts, so this should cause you no issues. Some of these have also been moved to the public API, either identically or with changes, and the mapping is as such:
  • _getNamedAs -> getNamedAs: Changed to always require a conversion argument. If you were previously using it to plainly get a named property or to handle the properly being None or a real value, you should use the return value of getNamedProp instead.
  • _getPropertyAs -> getPropertyAs: Same as above, use getPropertyVal instead for None or plain access.
  • _getStreamAs -> getStreamAs, getStringStreamAs: Once again, see above. Use getStream and getStringStream, respectively.

v0.44.0

• Fixed a bug that caused MessageBase.headerInit to always return False after the 0.42.0 update.
• Changed MessageBase.headerInit to a property.
• Fixed extract_msg.utils.__all__.
• Minor regoanization within extract_msg/utils.py.
• Minor changes to docstrings.
• Minor README updates.
• Fix issue with folded header fields decoding incorrectly when given to extract_msg.utils.decodeRfc2047.

v0.43.0

• [[TeamMsgExtractor #56](https://redirect.github.com/interface to stdlib interfaces TeamMsgExtractor/msg-extractor#56)] [[TeamMsgExtractor #248](https://redirect.github.com/Support for returning an EmailMessage object TeamMsgExtractor/msg-extractor#248)] Added new function MessageBase.asEmailMessage which will convert the MessageBase instance, if possible, to an email.message.EmailMessage object. If an embedded MSG file on a MessageBase object is of a class that does not have this function, it will simply be attached to the instance as bytes.
• Changed imports in message_base.py to help with type checkers.
• Changed from using email.parser.EmailParser to email.parser.HeaderParser in MessageBase.header.
• Changed some of the internal code for MessageBase.header. This should improve usage of it, and should not have any noticeable negative changes. You man notice some of the values parse slightly differently, but this effect should be mostly suppressed.

... (truncated)

Commits

• 25db76d Merge pull request #385 from TeamMsgExtractor/next-release
• 442f2cd Fix bug in PropertiesStore.getValue
• 448513c Replace mixed quotes in documentation file
• c149666 Finish reworking significant parts of private api
• 7c14152 Significant progress converting from old api
• b2ce27b Potentially done transferring api usage
• b74282b More adjustments to public and private API
• 2c71551 More progress
• d625ae0 Reduce reliance on private api for many functions
• b1be06d Bump version
• Additional commits viewable in compare view

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)