Share
Report
2The deceptively challenging problem here is that I can use the "base64tostring" action to get the header information from the .eml file. However, eml files of a certain? size and those with attachments appear to be encoded -- maybe mime? The header information is decoded, however the body of the eml file remains encoded/encrypted. We need to be able to do a substring search of the body of the eml file. This ability is a core need within a larger framework of processing messages involving Purview, SPO, and other business process automation. Because of other mechanisms and volume, we can't go directly to the mailboxes to get the email. We also considered orchestrating content searches after a DLP detection occurred, but it comes at the cost of timing/duration before the content is available to be searched. While not security-related, the logic we must apply to the eml file is beyond what can be done via Purview.
What are some methods to open an EML file in Automate (not PAD) and get the text of the body of the email file where the text appears to be encoded? BTW, we believe this is happening when the Teams to SPO email connector writes the file. Emailing to a teams channel was the way we determined to be able to create the files. Essentially a trigger sends emails to Teams which writes to SPO and we process from there. Open to change this if there is a better way. 🙂
Appreciate your help. Truly is a great community here!
All responses (
Answers (
