I’m hoping to get a little more information regarding a new issue we’re seeing related to .msg files in our web app.
We previously had the project configured as a C#/net5.0 SPA that ran our React web app and interfaced with a net5.0 API. Prior to updating to net7.0, we split out that functionality so the front end is just a React app and there’s an API gateway that runs separately that handles the login. I believe it was this change that led to the error we’re seeing now.
We could open message files like the one attached and they’d appear like the first image in the viewer, but now it appears that anything with an image or any sort of complex content, like a picture, item in the signature, etc., comes back like in the second picture, encrypted or mistranslated.
I have a copy of the .msg file from the pictures saved if you have a way to receive it.
I just wanted to know if you’ve seen anything like this and might be able to point me in the right direction. If you need any further information about our implementation, please let me know.