Unable to open rpmsg

mevaibhav831345 

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.