Hello,
One of our customers has been encountering errors while attempting to load metadata from all items in a PST/OST using Aspose.Email for .NET 3.6. Each PST/OST contains a handful of items that are corrupt and can’t be read by Outlook.
The customer is unhappy because another product that they use is able to extract all the emails, apart from the handful that are corrupt. This is the sort of behaviour we would hope to see from Aspose.Email – ie. the ability to enumerate all emails other than those that are corrupt. In general, once Aspose.Email encounters an error, it isn’t able to enumerate subsequent emails in the same folder, or sometimes in the rest of the PST.
We have developed a small test utility to enumerate through all the items in a PST/OST using a variety of different methods, to compare the robustness and performance of each method. When run across the customer’s semi-corrupt PSTs, none of the methods included in the utility were able to enumerate as many items as the other product that the customer is using.
I will attach the source code for the utility, along with some of the exceptions that the customer has received. Unfortunately we don’t have direct access to the customer’s data, as it is of a confidential nature.
We would appreciate your assistance in fixing these specific errors if possible. More generally, we would like your advice regarding the most robust method of enumerating as many items as possible in semi-corrupt PSTs/OSTs.
Thanks,
Reuben