Forum Discussion
Unable to open rpmsg
mevaibhav831345 Any resolution on this. I've been in this OME rabbit hole for about 2 years
AsTheCrowFlew - Multiple account at Outlook for AIP world in many case more like unsupported scenario especially with AIP UL client at Outlook or there is temporary authentication failure (which usually happen for exchange mailbox behind the scene).
Because of unsupported scenario, there could be different (some unexpected like you see one at your end) UX when there are multiple account at one profile or multiple account spread across multiple profile.
Make sure to have following in-place (there is no permanent fix for my scenario) to deal with .rpmsg UX for email at Outlook when mailbox is hosted at Exchange Online:
- Close all open browser and office app
- Open IE and Edge and type in https://portal.office.com and make sure you logged in with account which has experienced .rpmsg issue
- Make sure to have same account (account where .rpmsg) at your outlook
- Wait for 5 minutes
- Restart your outlook , let it full load and check encrypted email once again
The recipient is often not us, so we don't have the ability to troubleshoot the other end. It's almost always the case that OWA and Microsoft Mail can decrypt the message, but the full Outlook client can't. For many of our partners OWA and Microsoft Mail is not allowed. I want to embrace OME but the recipient behavior is wildly inconsistent making it difficult for users to adopt.
- I understand your point and its associated challenge where sender dont have control on recipient's infrastructure (especially their OWA is blocked by their org policy) but recipient having Outlook client is not the only answer to auto-decrypt encrypted content because multiple variables to consider like
- if recipient mailbox is on non-exchange/OWA (like social identity) will continue to see that .rpmsg attachment (at outlook client) even though they use Outlook client
- if recipient device has multiple account in-use (like recipient using his personal device where he has his own individual personal account in-use along side recipient company account) then also user get into such problem
To be honest, due to lack of control/choice - only thing that i can suggest is recipient to get in touch with their IT team.Outlook.live com OWA is not blocked on my computer. It just has zero function to open a .RPMSG file.
It also has zero ability to realize that I am the intended recipient. I don't know what else it doesn't know, but it's as far as possible from artificial intelligence and pretty close to natural ignorance.
What is "non-exchange/OWA" ? Explain!
You say: - if recipient mailbox is on non-exchange/OWA (like social identity) (sic: he/she/it is missing) will continue to see that .rpmsg attachment (at outlook client) even though they use Outlook client.
I say: I can see the RPMSG file in both the OWA version and the "Outlook client" version. Neither of them opens it.
You say: "- if recipient device has multiple account in-use (like recipient using his personal device where he has his own individual personal account in-use along side recipient company account) then also user get into such problem."
I say: So, are you saying that if I have two personal e-mail accounts (my wife and my own) then the whole RPMSG file process gets confused? Even though "the e-mail with the .RPMSG file in it" is clearly and positively addressed to my OWN e-mail address, and not to anyone else. To me that sounds like a major programming mistake that should have been caught before releasing this monstrosity on the public. Seems like MSFT no longer tests or fixes anything.
Regarding your statement "To be honest, due to lack of control/choice - only thing that i can suggest is recipient to get in touch with their IT team. "
Well, what in the world makes you think that the person working at home has something as expensive and as unable to help as a so-called "IT team"? I gather from my searches on the internet that problems with opening .RPMSG files have been around for more than five years now. MSFT is not interested in fixing this. They probably have some kind of statistical threshold that says: If a problem is reported by fewer than 2% of the customers, then we won't respond, won't fix it, because eventually people will give up. At this point it seems that MSFT fired the person in charge of this, so nobody is in charge of the whole mess. It is up to MSFT to prove me wrong by fixing the thing.
same here, our clients can't open these new azure encryption mails, it just keep downloading over and over when they click on it, and they never get the 'open message' button in the email. And there not going to become MS email encryption experts to figure it out either. This process use to be so easy with a mail rule Encrypt for the subject line, and the HTML link that always worked via login and one-time passcode. Now the whole process is so convoluted there own techs can't figure out why ours just abruptly stopped working after a decade, unbeknown to us while documents setup in SMTP automation were going out unencrypted to clients. We only discovered it after our SMTP emails also started to fail, then discovered SMTP has to be assigned to the individual user now. We must of missed the memo on that one. the MS tech wrote our new Encrypt by subject line mail rule and it still didn't work. The problem is the have all these different licenses now and they keep changing what they offer and appeared some of our exchange 1 licenses were so old the tech couldn't believe we could encrypt emails ever, I'm still not sure if he believes me, now they can't fix it.
