-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to receive .msg files as an attachments #10
Comments
If you open the file the content should still be of the .msg file, the problem is |
I understand, but when encountering an attachment with an unknown extension, it is difficult to determine its specific format and, therefore, an application that can open it. |
You could check the magic bytes via https://github.com/gabriel-vasile/mimetype |
I attempted to write out an .msg attachment as a file and only got a small amount of garbage data. I created a test PST file with a single message containing a single attachment - an .msg file. I followed the example code. I believe it's not parsing .msg attachments. |
@McFlip Would it be possible to send me the test PST file (my email is info@mooijtech.com) so I can reproduce and possibly fix this issue? |
On the way! |
Thanks for the test PST files, makes it much easier to solve. |
I can now read the embedded attachment, this should be the OLE format. Should be solved in a few days. |
ETA may be extended a week since support for writing PST files came up |
@mooijtech Hi friend. Any updates? I've been using readpst as a workaround but I would love to use your lib instead. |
Is your feature request related to a problem? Please describe.
During the parsing procedures we are unable to receive attachments that represent .msg files. Instead we have files with "UNKNOWN..." names.
Describe the solution you'd like
Would like to get attachments in their native format. In this particular case -> .msg files. It would be great for further analysis using proprietary applications.
The text was updated successfully, but these errors were encountered: