Skip to main content

Delete corrupt rules using MFCMAPI

Delete corrupt rules using MFCMAPI


Following steps to be followed if you need to delete any corrupt/hidden rules using MFCMAPI.

• Export a backup of all Inbox rules from Outlook:

                                1. In Outlook 2007, please click the Tools > Rules & Alerts.
                                    In Outlook 2010 and 2013, please click the Rules > Manage Rules & Alerts in the Move group on the Home tab

                                2. Click the Options on the E-mail Rules tab.

                                3. Now the Options dialog box comes out, click Export rules.

                                4. And then in the Save Exported Rules as dialog box, open a folder to save the exported file firstly; secondly enter a name for the exported file in the File name: box, and at last click the Save button.

                                5. You can also refer to: https://support.office.com/en-au/article/Import-or-export-a-set-of-rules-91e357da-3026-4fb6-8b0e-5e7c8a0fbf5b


• Turn off the cached mode for Outlook.

                                1. Click the File tab.
               
                                2. Click Account Settings, and then click Account Settings.

                                3. On the E-mail tab, click the Exchange account, and then click Change.
               
                                4. Under Microsoft Exchange server, select or clear the Use Cached Exchange Mode check box.

                                5. Exit and then restart Microsoft Outlook.


• Delete all the rules using MFCMAPI.
                                1. Download the 32-bit or 64-bit version of MAPI tool as per the Outlook version.

                                                -> http://mfcmapi.codeplex.com/

                                2. Open the folder to which you extracted MFCMapi, double-click mfcmapi, and then click OK.
               
                                3. On the Session menu, click Logon and Display Store Table.

                                4. If you are prompted to select a profile, click the profile name in the Profile Name list, and then click OK.
               
                                5. Double-click the mailbox that contains the inbox rules that you want to delete.

                                6. Expand Root Container, and then expand Top of information Store.
                                Note: Outlook should be in Online mode to use MFCMAPI. If you see IPM_SUBTREE instead of Top of information Store, Outlook Cache mode is enabled. Disable Outlook Cache mode before you use MFCMapi.

                                7. Right-click Inbox, and then click Open Associated Contents Table.
                                The Open Associated Contents Table contains the hidden messages of the Inbox.

                                8. In the Inbox window, locate and then click the items that have the following message class, and then click Delete.
                                                a. IPM.Rule.Message
                                                b. IPM.Note.Rules.OofTemplate.Microsoft
                                                c. IPM.Note.Rules.ExternalOOFTemplate.Microsoft
                                                d. IPM.ExtendedRule.Message

                                9. Select Permanent delete passing DELETE_HARD_DELETE (unrecoverable) in the drop-down list, and then click OK.

                                10. Close the tool by logging off the session.

                                11. Additionally, this link can be referred: https://support.microsoft.com/en-us/kb/924297

• Launch the Outlook to test.
• Import the backed up rules (if any).


Links which can be referred:
  1. http://blogs.msdn.com/b/hkong/archive/2015/02/27/how-to-delete-corrupted-hidden-inbox-rules-from-a-mailbox-using-mfcmapi.aspx
  2. https://support.microsoft.com/en-us/kb/924297

Comments

Popular posts from this blog

Error - QuarantinedAttributeValueMustBeUnique

Case History. 1. Client already had users created in office 365 2. Client wanted to setup SSO for office 365 users Approach for requirement fullfilment   1. Deployed and configured Azure AD connect      95% users were synced and soft match was successfully done  5% users were getting error - QuarantinedAttributeValueMustBeUnique  (to view the sync issues -  https://aad.portal.azure.com/#blade/Microsoft_Azure_ADHybridHealth/AadHealthMenuBlade/SyncErros )  When we checked 2 users were found under Active users  1. one in Cloud (this was created earlier/ already existed ) with active licenses and Mailbox 2. one unlicensed synced with AD Solution - 1. Delete the unwanted user in Azure or AD as per this document.  https://blogs.msdn.microsoft.com/hkong/2017/03/23/how-to-fix-attributevaluemustbeunique-error-message-when-trying-to-sync-an-object-from-on-premises-active-directory-to-office-365/ ...

Error - AttributeValueMustBeUnique in Azure AD connect sync

My customer had already created accounts in office 365 and managing them in Azure, however due to some changes in business they wanted to sync AD with Azure to sync Password and Manage Identity form AD. Solution - Deploy Azure AD connect on ADDC, and post that it will do a Soft Match. However there were error with some users, their identities did not sync and their status still reflected as Azure AD. Error -  Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [ProxyAddresses SMTP:user@domain.com;].  Correct or remove the duplicate values in your local directory.  Please refer to http://support.microsoft.com/kb/2647098 for more information on identifying objects with duplicate attribute values. Tracking Id: b8367c95-ae67-46e1-xxxx-xxxxxxxxxx ExtraErrorDetails: [{"Key":"ObjectId","Value":["cd088468-bb6a-4...

Block users from saving data on System Drive on Intune Managed Device

Recently i delivered a project for Intune Deployment and came up with a requirement as follows End Users Should not be able to save data locally on C or D Drive, instead they should be allowed to save data only in One Drive for business (synced with System)  Based on the requirement i did my research and found the Following. its possible to control the Local System settings on a Azure AD joined Machine and Managed by Intune. There is no options to define exceptions in policies to allow data saving in certain folders.  Now most of us will think WIP (windows information protection) policy will help us protecting the data on device, however that's not completely true as . User can change the File Ownership to personal if the WIP policy is set to Allow Override. User can save the file locally on the system User will not be able to copy the data from work file to Personal file if policy is set to Allow override. Unenlightened apps cannot differentiate between personal and corporate...