Forum Discussion
Unable to open rpmsg
- 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.
- ITPigeonApr 05, 2022Copper ContributorWe've since pinpointed our particular problem to the exact version of Outlook being used.
Microsoft is pretty stringent about which version is in support for reading rpmsg messages. Our Citrix environment has a semi-annual release and a vDisk update schedule that jùst missed the release from March, making our current environment 'unsupported'. Sigh. At least OWA works. - ITPigeonMar 31, 2022Copper Contributor
Thanks, but that article seems to focus on setting it up for your organization.
However, in this case it is some external party that just decided to send us an encrypted message this way. We do not use this functionality within our organization, but articles seem to suggest that a receiving party only needs a compatible app to read it. No extra infra settings needed.
User is able to read the email in an Outlook client outside of Citrix. It only refuses to work for the Outlook app within Citrix (OWA opened within the same Citrix sessions opens the e-mail just fine). I still think it's a compatibility issue somewhere but I'll keep looking. - mevaibhav831345Mar 31, 2022Copper Contributoralthough i am not using citrix, you should focus on basic things first about allowing some of required URL : https://docs.microsoft.com/en-us/azure/information-protection/requirements#firewalls-and-network-infrastructure
- ITPigeonMar 31, 2022Copper ContributorI can feel your frustration. Thanks for sharing your overall experience of the troubleshooting process with MS. Sounds like I have to keep looking elsewhere for answers on similar issues before contacting MS about this.
Out of curiosity, is anyone of you also using Citrix? We have issues opening the .rpmsg attachments, but only when using Outlook within Citrix XenApp. Aka: a multi-session environment.
Since some of the issues seem to come from authentication issues, I'm starting to think that might be related. - JoshARIFeb 18, 2022Copper Contributor
AsTheCrowFlew yea it's just gotten frustrating. Our clients are medical facilities so email encryption is a must have for us, kind of puts everything at a stand-still. It can't linger on for a day let alone a week like it has with no solution from MS techs, or seemly any sense of urgency. And it's Friday and no word yet this morning. Since our exchange mail rule stopped working MS can't figure it out and we're sort of stuck ATM, all our emails need to be encrypted (PHI). Prior to a couple weeks ago, all we did was put 'encrypt' in the subject line and that would encrypt the mail and our clients would receive an html link they never had any issues opening, either with the one-time passcode or creating a login. Now MS has setup this new encryption method via the azure portal, spent over 2 hrs on the phone with the tech setting it all up and getting it activate (we think), using all these PowerShell commands, creating a new mail flow rule, disabling the old one, adding licensing, not even sure what PowerShell has to do with email encryption to begin with (it's certainly not user friendly like they claim, and none of it worked). How does MS expect admins to figure it out, if they can't. All our clients have their own mail systems, they don't use 365 or outlook. Best we can do ATM is encrypt the email via the lock icon in outlook but our clients can't open the rpmsg message, neither can we. There's no button to 'view this message'. And one can only spend so much time reading about email encryption and sitting on phone with a tech for hours before your sanity starts to slip :). K I'm just ranting now, thanks for responding!