Cannot use MFCMAPI to copy and paste personal retention policy tags from one folder to another
@stephenegriffin is already working on this.
Since Jul 31, 2023.
- Dominant language
- C++
- Stars
- 978
- Forks
- 170
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
A while back I wrote this guide on how to use MFCMAPI to prevent auto archiving for Calendar, Notes and Tasks in Exchange Online - https://answers.microsoft.com/en-us/msoffice/forum/all/prevent-archiving-for-calendar-notes-and-tasks-in/477d93b9-143e-4ace-8c7b-de1bfafc913d.
This is no longer working and I have tested with the following MFCMAPI versions: x64.19.2.19207.938, x64..21.0.21127.03, x64.23.0.23086.06.
The steps to reproduce the issue are:
- Create a new folder with Outlook desktop client or OWA in the mailbox
- Assign to this new folder a personal archive tag
- Run Start-ManagedFolderAssistant to confirm the changes
- Start MFCMAPI x64.23.0.23086.06, select Tools, Options and make sure you check "use MDB_ONLINE" and "MAPI_NO_CACHE", then click OK
- Click on Session tab and then logon to select the Outlook profile of the affected mailbox
- Double click on the name of the Exchange mailbox and expand the Root Container in the new window
- Expand Top of Information Store and look for the new folder that you created
- There will be a property stamped on it called PR_ARCHIVE_TAG, right click on it and select Copy
- Now select the Calendar folder for example, right click on it and select Paste - nothing happens, the PR_ARCHIVE_TAG property is not copied over on the Calendar folder
It's the same behavior as above with version x64..21.0.21127.03. With version x64.19.2.19207.938 however, there are additional things going on:
- When I right click on the Calendar folder and I select Paste, I get a new window prompt that asks me how do I want to paste the property with the Copy Style field automatically set to IMAPIProp::CopyProps
- I click OK on the Copy Style prompt and a second windows pops up on which I also click OK
- The end result is that the PR_ARCHIVE_TAG property is created on the Calendar folder but with a null binary value, which makes it useless, as the expected result is to have the ID of the tag in that binary value
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.