Hey guys,
We're using the latest 5.3 Aspose.Email assemblies and have run into a bit of an issue whenever we create the 2nd IMapClient object within a Mono/Mac (Yosemite 10.10) environment. We have a large number of automated tests written in NUnit and this problem is very easy to reproduce. If you had a single test class in which 2 methods both create and disconnect/dispose the IMapClient object, the first one will succeed and the other will basically hang for 40 seconds until you reach the timeout.
We have a very new cross-platform architecture in which all of our tests pass 100% in Windows but running the same tests via Xamarin in OSX fails. If you run each test individually, they all pass. Unfortunately, our current design potentially creates multiple client objects.
I found the following post that sounded eerily similar...
http://www.aspose.com/community/forums/thread/397715/imapexception-when-connecting-the-second-time.aspx
Is this a known issue? Are there any possible workarounds?