esa.crawler.mapi.skipMsgTypes properties clears on itself

Hello Sarah,

I wanted to respond to let you know that I had a case with one of my customers recently where myself and our Backline Support have confirmed that the System Property esa.crawler.mapi.skipMsgTypes isn’t preventing email stubs from being processed as expected.

At present this issue has been reported in a bug (Etrack) and is with Engineering, but there have been no new updates.

However, there is another System Property esa.icp.collection.exchange.excludeIPMMessageClasses that is preventing the collection of email stubs during Exchange Collections. This setting can be applied by System or Case. This setting accepts all of the appropriate message classes separated by a comma as follows:

• IPM.Note.EnterpriseVault.Shortcut
• IPM.Note.EnterpriseVault.PendingArchive
• IPM.Note.EnterpriseVault.Shortcut.DeleteMe
• IPM.Note.EnterpriseVault.Shortcut.RestoreMe
• IPM.Note.EnterpriseVault.PendingArchive.ArchiveMe

Note: Again, this setting only applies to Exchange Collections.

Note: While the System Property can be used please keep in mind, as my customer has, that there may be some matters that require the collection of email stubs.

If you have a matter that already has email stubs processed and/or will be required, there is a method that you can use in Analysis & Review from the Advanced Search to differentiate between email stubs and relevant email as follows:

1. Go to the Advanced Search.
2. Select Free Form search.
3. Under the Queries field, type the following:

• +nGrams:(enterprisevault) Note: Includes email stubs
• -nGrams:(enterprisevault) Note: Exclude email stubs

4. Click Run Search.

From here, you could perform some of the following:

• Tagging emails as either Relevant or Non-Relevant
• Exporting Relevant emails
• Review Relevant emails

Also, if you click on Report, you can see the number of Matching and Non-Matching Documents.

I hope that this has helped. If so, kindly mark the post as Solved :)