An RPMSG file, usually named message.rpmsg, is the container Microsoft uses for many rights-protected email messages, including messages protected with Microsoft Purview Message Encryption. It is not an ordinary attachment. Opening it depends on the correct account, a successful sign-in, permission from the sender, and a supported Outlook or browser experience.
This guide explains why an RPMSG file may not open in Outlook, how to tell a file problem from an access problem, and which fixes to try in order. It does not cover bypassing the protection, because the protection is working as designed.
Quick answer: Most RPMSG problems come from the account, the sign-in, or the message permissions, not from a broken file. Open the original message (not a saved copy) in Outlook on the web, signed in with the exact address the message was sent to, and complete the sign-in prompts. If that fails, the sender or your Microsoft 365 administrator usually has to fix access.
Why Is the RPMSG File Not Opening in Outlook?
The items below are possibilities, not diagnoses. Several of them look alike on screen, so work through the fixes in the next section rather than assuming one cause.
- Wrong Microsoft account. The message may have been shared with a specific work or school address, and you are signed in with a different one.
- Authentication is required. The protected message may need you to sign in, or to request a one-time passcode, before it displays.
- You lack permission. Having the file does not mean you have the right to read it.
- Protection settings are causing an access problem. The sender’s rights-management configuration may not match your account.
- Outlook or your browser has a problem. The app may be out of date, or a temporary session issue may be involved. Microsoft has also documented specific client issues with encrypted messages in classic Outlook.
- Your organization restricts access. Microsoft 365 security policies can limit who can open protected content.
- Access has expired or changed. Where the sender set conditions, they may no longer be met.
- The file is incomplete or not the original. A saved, forwarded, or partially downloaded copy may not behave like the original message in your mailbox.
File problem or access problem? A file problem is more likely if the original message in your mailbox opens but a saved copy does not, or if nobody can open it. An access problem is more likely if you see sign-in prompts, permission messages, or an access-denied notice, or if the message opens for another recipient but not for you. Neither pattern proves the cause, but they point you to the right fix.
How to Fix an RPMSG File Not Opening in Outlook
Try these in order. Stop when the message opens.
1. Confirm That You Are Using the Correct Email Account
Check which address received the protected message, then check which account you are signed in with. In Outlook on the web, your account picture or initials in the corner show the active account.
If the message was shared with a work or school account, authenticate with that account rather than a personal one. If several accounts are signed in on the same device, sign out of the extras or use a private browsing window.
2. Open the Protected Message Through a Supported Outlook Experience
Open the original message in your mailbox rather than a downloaded .rpmsg file. Microsoft’s guidance says that if you use a work or school Microsoft 365 account in a desktop or online version of Outlook, you typically should not need to do anything special to read the message.
If the message will not open in the desktop app, try Outlook on the web at outlook.office.com. Browser access depends on your organization’s configuration and the protection method the sender used.
If you use the new Outlook and normally group messages by conversation, open the protected message in its own window. Microsoft notes that conversation view does not support viewing encrypted messages. For other opening methods, see our guide on how to open an RPMSG file.
3. Complete the Authentication Process
Follow the sign-in prompts and any identity checks. If the message arrived in a non-Microsoft mailbox, such as Gmail or Yahoo, it usually contains a link such as “Read the message.” From there, you can typically sign in or request a one-time passcode.
Microsoft states that a one-time passcode expires after 15 minutes. If it expires, request a new one. If the screen says you must request access, contact the sender or your administrator. Do not use tools that claim to skip authentication.
4. Check Whether You Have Permission to Open the Message
Possessing an RPMSG file does not grant permission to view its contents. Ask the sender to confirm three things: the message was shared with the correct address, that address matches the account you are using, and your account has the necessary rights.
Mismatches are common when someone has both a personal and a work address, or when the sender typed an alias.
5. Update Outlook and Try Again
For classic Outlook, check for updates under File > Office Account > Update Options (labels vary by version and by how your organization manages updates). Then close Outlook completely and reopen it.
Microsoft has documented a classic Outlook error with externally encrypted email in certain builds and lists it as fixed, noting you may need to restart Outlook more than once for the fix to apply. Classic Outlook and new Outlook differ in interface and capabilities, so if one fails, try the other or Outlook on the web.
Updating will not fix a permission problem. If you are asked to sign in or are denied access, move on to Steps 3 and 4. If Outlook itself freezes while opening the message, see our guide to fixing Outlook not responding.
6. Try Another Supported Browser or Outlook Session
Open the original message in Outlook on the web using a different supported browser or a private browsing window, where your organization’s policies allow it. This can reveal whether the cause is a stale session, a cached sign-in, or a browser extension.
It will not override access restrictions. If the message still will not open, the cause is more likely permissions or policy.
7. Ask Your Microsoft 365 Administrator to Check Rights Management
If you are on a work or school account, an administrator can look at several areas:
- Microsoft Purview Information Protection and message encryption settings, to confirm the protection applied to the message.
- Microsoft Entra ID sign-in and access policies, which can block or interrupt authentication.
- Recipient permissions and organizational restrictions, including whether your account is allowed to open the content.
- Service or client errors. Microsoft publishes known issues for classic Outlook, and its guidance on Microsoft Entra configuration for Purview-protected content can matter when sender and recipient are in different organizations.
You can pass this list along as is. Administrators who still cannot resolve the problem can open a support case through the Microsoft 365 admin center.
8. Ask the Sender to Resend or Reissue the Protected Message
This is appropriate if the original looks incomplete, access conditions may have changed, or the sender needs to correct the recipient’s permissions. A resent message is often the quickest fix when the saved copy is the problem.
Do not ask the sender to strip the protection or forward confidential content to an account that was not authorized. Doing so defeats the purpose of the protection and may violate the sender’s policy.
How to Fix Common RPMSG Errors in Outlook
Symptoms alone do not prove a cause. Treat the middle column as possibilities.
| Error or symptom | Possible explanation | Recommended action |
| Access denied or permission message | Your account may not be on the recipient list, or the sender’s permissions may have changed | Confirm your account, then ask the sender to check the recipient and rights (Step 4) |
| Sign-in required | The message needs authentication before it displays | Sign in with the address the message was sent to, or use a one-time passcode if offered (Step 3) |
| Protected message will not display | Your client may not show it inline, or it may be open in a view that does not support protected messages, such as conversation view | Open it in its own window or in Outlook on the web (Steps 2 and 6) |
| Attachment cannot be opened | A saved or forwarded copy may be incomplete or detached from the original; the client may lack support | Open the original message in your mailbox, or ask the sender to resend (Steps 2 and 8) |
| Outlook repeatedly asks you to sign in | Wrong account, several signed-in accounts, an expired passcode, or an access policy | Use the correct account, a private window, or a fresh passcode; ask IT if it persists (Steps 1, 3, 6, 7) |
| Opens for another recipient but not you | Suggests an account or permission difference, not necessarily a broken message | Ask the sender to check your address and rights; ask IT to check policies (Steps 4 and 7) |
| Classic Outlook says it cannot read the item, or mentions Information Rights Management setup | Microsoft has documented client issues of this kind | Update Outlook, try new Outlook or Outlook on the web, and check Microsoft’s known-issues page (Steps 5 and 7) |
Can You Open an RPMSG File Without Outlook?
Sometimes, but only through a supported Microsoft route. An RPMSG file holds protected message content. It is not a document you can reliably open in a text editor or a general file viewer.
- Renaming does not convert it. Changing. rpmsg to .eml, .msg, or .pdf does not convert the file. It only makes the file harder to open correctly. For what an actual EML file is, see our guide to opening EML files.
- Generic online file openers are not appropriate. Uploading a protected message to an unknown site is a privacy risk, and it is not a legitimate way to get around message protection.
- Supported routes still need the right account. Microsoft says users on clients other than Outlook can read protected messages through the encrypted message portal, using the link in the notification email, and Outlook on the web is another option. You may still need the correct account or a one-time passcode.
- Prefer the original message. If it is still in your mailbox, opening it there or through its link is usually better than working with a detached file.
When Should You Contact IT Support?
Contact your administrator or IT support if:
- Several employees have the same problem.
- Access fails even though you are using the correct account.
- Your organization uses strict conditional-access or information-protection policies.
- The protected message is business critical.
- You see repeated authentication failures or an access-denied message.
Provide your Outlook version, operating system, the exact error text, whether one person or several are affected, and whether the message opens in Outlook on the web.
Never share passwords, authentication codes, or confidential message contents when asking for help.
Frequently Asked Questions
1. Why is my RPMSG file not opening in Outlook? The most common reasons are the wrong signed-in account, missing permission, an incomplete sign-in, or a client or policy issue. Check the account first, then open the original message in Outlook on the web.
2. How do I open an RPMSG attachment in Outlook? Open the original email in your mailbox and follow any sign-in prompts. With a work or school Microsoft 365 account, protected messages typically open without extra steps. Our RPMSG opening guide covers the general methods.
3. Can I open an RPMSG file without Microsoft Outlook? Possibly. Microsoft says other email clients can use the encrypted message portal link, and Outlook on the web is another supported option. You still need the correct account and permission.
4. Why does Outlook keep asking me to sign in to view an encrypted message? You may be using the wrong account, have several accounts signed in, have an expired one-time passcode (they expire after 15 minutes), or be affected by an organizational access policy. Try a private window and the exact recipient address.
5. Can I convert an RPMSG file to PDF? Not directly. Renaming does not convert it. If you can legitimately open the message, the sender’s protection settings may still restrict printing or copying. If printing is allowed, you can print it to PDF after opening it. Avoid third-party converters.
6. Does an RPMSG file require Microsoft 365? The sender typically uses Microsoft rights-management features. Recipients do not always need their own Microsoft 365 subscription, because Microsoft describes sign-in options and one-time passcodes for other accounts, but support depends on how the message was protected.
7. What should I do if an RPMSG file says access denied? Confirm you are using the address the message was sent to, then ask the sender to check that your account has rights. If it still fails, ask your administrator to review the access and protection policies.
8. Can I open an RPMSG file on a Mac or mobile device? Microsoft lists Outlook for Mac, Outlook for iOS, and Outlook for Android among supported clients for protected messages, and the browser portal is an option when the message arrives in another app. Behaviour can depend on the protection method and your account. Opening a protected message depends on Microsoft permissions, and migration does not change who is allowed to read it. If you have wider questions about moving or managing mailboxes, you can explore SkyMigrate’s Microsoft 365 migration services.
