This was exactly what I needed, and actually what I expected from the default ListMessages(string folder) method. The various ExchangeClient ListMessages methods have no documentation, and required reflection to even figure out what the parameters were. Here is the only documentation on your site and in the compiled help file for these methods:
============================
Lists the mail message in the specified folder.
Overload List
Lists the mail message in the specified folder.
public override ExchangeMessageInfoCollection ListMessages(string);
List the messages in the specified folder
public ExchangeMessageInfoCollection ListMessages(string,bool);
Lists the messages.
public ExchangeMessageInfoCollection ListMessages(string,string);
List the messages in the specified folder
public ExchangeMessageInfoCollection ListMessages(string,string,bool);
============================
If you click any of the links to see the details you get a blank page.
I could see this kind of documentation for an open source project where you could at least look at the source code, to try and figure out what the methods do, but for a product that is purchased, where we don't have access to the source code, and the code has been obfuscated, it is very difficult to figure out how to properly use the API's, especially if they are not intuitive. A method like ListMessages with only a folder as an argument, should by default list ALL messages, not filter it to only a specific type of messages like it does now where all the undeliverables are excluded. I wasted a day or two looking into other API's I could use because until I found this post, I couldn't figure out how to get to all the messages, since the primary purpose of the application I am writing is to process a mailbox where all the undeliverable messages get delivered.
It would really be helpful if Aspose could either provide source code, or at least unobfuscated libraries to paying customers so that we could figure out how to use the various API's that are lacking any meaningful documentation. The examples are helpful when you can find one that does exactly what you want, but otherwise trying to figure out what the parameters are, and what they do takes way more time than it should, and in some cases is almost impossible.
I do appreciate the post that solved my problem, it's great that there is forum support, and I think there is a lot of potential in the library, but in the long term, if people can't figure out how to use the Aspose libraries without posting every question or trying to decipher obfuscated reflected code, they will go somewhere else.
Rick
