hefthor
New Member
- OS Version(s)
- Windows
- Outlook version
- Outlook 365 64 bit
- Email Account
- Office 365 Exchange
Operating system:: Windows 11 Latest
Outlook version: Latest
Email type or host: Exchange Online / Microsoft 36
Outlook version: Latest
Email type or host: Exchange Online / Microsoft 36
Hi Dmitry,
is there a supported way in Redemption to export a Microsoft Purview / Sensitivity Label protected mail as an *unprotected* MSG file, byte-faithful (original MAPI properties, internet headers, SentOn, EntryID-equivalent metadata, attachments) — assuming the current user has full rights on the item?
Context:
- Outlook COM add-in, C# / .NET Framework 4.8, AddInExpress, classic Outlook desktop.
- Item is protected via a Sensitivity Label (Purview / MIP), not classic AD RMS templates and not S/MIME. MessageClass is IPM.Note.rpmsg, message.rpmsg attachment present.
- Outlook's "My Permissions" dialog confirms full rights including **Export: Yes** and **Programmatic Access: Yes**. Body and attachments are readable in the UI.
- The item lives in Sent Items, so the original is read-only — we do not need to modify it, only to produce an unprotected copy on disk.
- Outlook's built-in "Remove protection" path refuses with "protection cannot be removed, change the sensitivity label instead" — which is expected for label-based protection, but a downgrade is not desired here (we want an export, not a label change on the live item).
What I've tried with the PIA:
- MailItem.SaveAs(path, olMsgUnicode) writes the rpmsg wrapper, resulting MSG is an empty shell with message.rpmsg attached.
- Building a new MailItem via CreateItem + copying HTMLBody/Attachments works for content, but the result is a draft and loses SentOn, InternetMessageHeaders, original sender/recipient MAPI props, etc. — not acceptable for our use case.
What I'm looking for:
1. A Redemption pattern that yields a fully decrypted, unprotected RDOMail / MSG with original envelope properties preserved.
2. In particular, whether RDOAttachment.EmbeddedMsg on the message.rpmsg attachment is the intended entry point here, or if there is a more direct API.
3. Whether Sensitivity Label protected items behave differently from classic AD RMS items from Redemption's perspective.
If this scenario isn't supported by Redemption either, a short confirmation would also help — saves me chasing the wrong path.
Thanks!
is there a supported way in Redemption to export a Microsoft Purview / Sensitivity Label protected mail as an *unprotected* MSG file, byte-faithful (original MAPI properties, internet headers, SentOn, EntryID-equivalent metadata, attachments) — assuming the current user has full rights on the item?
Context:
- Outlook COM add-in, C# / .NET Framework 4.8, AddInExpress, classic Outlook desktop.
- Item is protected via a Sensitivity Label (Purview / MIP), not classic AD RMS templates and not S/MIME. MessageClass is IPM.Note.rpmsg, message.rpmsg attachment present.
- Outlook's "My Permissions" dialog confirms full rights including **Export: Yes** and **Programmatic Access: Yes**. Body and attachments are readable in the UI.
- The item lives in Sent Items, so the original is read-only — we do not need to modify it, only to produce an unprotected copy on disk.
- Outlook's built-in "Remove protection" path refuses with "protection cannot be removed, change the sensitivity label instead" — which is expected for label-based protection, but a downgrade is not desired here (we want an export, not a label change on the live item).
What I've tried with the PIA:
- MailItem.SaveAs(path, olMsgUnicode) writes the rpmsg wrapper, resulting MSG is an empty shell with message.rpmsg attached.
- Building a new MailItem via CreateItem + copying HTMLBody/Attachments works for content, but the result is a draft and loses SentOn, InternetMessageHeaders, original sender/recipient MAPI props, etc. — not acceptable for our use case.
What I'm looking for:
1. A Redemption pattern that yields a fully decrypted, unprotected RDOMail / MSG with original envelope properties preserved.
2. In particular, whether RDOAttachment.EmbeddedMsg on the message.rpmsg attachment is the intended entry point here, or if there is a more direct API.
3. Whether Sensitivity Label protected items behave differently from classic AD RMS items from Redemption's perspective.
If this scenario isn't supported by Redemption either, a short confirmation would also help — saves me chasing the wrong path.
Thanks!
