Small (one line) fix to the email parse (utilities_email_parse) function to allow email attachments to have the extension '.MSG' as opposed to only '.msg'.
Description
Making the file extension lower case before comparing it to '.msg'.
Motivation and Context
I have encountered some email files that come into resilient as "EMAIL.MSG" which would not match the .msg check causing the email file to not get parsed.
How Has This Been Tested?
I ran email files with '.eml', '.msg' and '.MSG' extensions through the function and all of the files were parsed properly.
[x] Either no new documentation is required by this change, OR I added new documentation
[x] Either no new tests are required by this change, OR I added new tests
[x] I have run pep8 and pylint. I have cleaned up all valid errors and warnings in code I have added or modified. These tools may generate false positives. Don't be worried about ignoring some errors or warnings. The goal is clean, consistent, and readable code.
This issues has been fixed in a recent release of fn_utilities. Thanks for submitting Liam. We are cleaning up the PR's in the public github and will hopefully be more responsive in the future.
Small (one line) fix to the email parse (utilities_email_parse) function to allow email attachments to have the extension '.MSG' as opposed to only '.msg'.
Description
Making the file extension lower case before comparing it to '.msg'.
Motivation and Context
I have encountered some email files that come into resilient as "EMAIL.MSG" which would not match the .msg check causing the email file to not get parsed.
How Has This Been Tested?
I ran email files with '.eml', '.msg' and '.MSG' extensions through the function and all of the files were parsed properly.
Checklist:
Signed-off-by: LiamMahoney liammahoney96@gmail.com