HSMF enhancements #167
Closed
HSMF enhancements #167
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- introduce NameIdChunks.GetPropertyTag which enables evaluating property ids from properties identified by name/id in property sets
(simple version of IMAPIProp::GetIDsFromNames)
- AttachmentChunks.getAttachData: use new ByteStreamChunk instead of ByteChunk which enables delayed reading of attachments
to avoid all attachments are completely read into memory when parsing which may cause OutOfMemoryErrors on e-mails with big attachments.
- POIFSChunkParser: support reading multi valued chunks (e.g. required when reading the Keywords ("categories") property)
- add MAPIProperty.RECEIVED_BY_SMTP_ADDRESS
- add unit tests
Author
|
Thank you for applying this! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(simple version of IMAPIProp::GetIDsFromNames)
to avoid all attachments are completely read into memory when parsing which may cause OutOfMemoryErrors on e-mails with big attachments.