Doing nothing more than attempting to construct the client object in separate test methods will result in the 1st test passing and the 2nd test to fail. I experimented with different constructors, removing using statement/Dispose, explicitly calling Disconnect, etc. all to no avail. As mentioned, we have no issues whatsoever constructing multiple client objects in Windows.
Please spare us a little time as we are further investigating this issue at our end. We’ll soon write back here to share our feedback with you.
Thank you for being patient.
We have further investigated this issue at our end and were able to reproduce the same problem at our end. It has been logged in our issue tracking system as EMAILNET-34802 for further investigation and rectification by our Product team. We’ll notify you here once there is some information or a fix version available in this regard.
Could you please check this issue with the latest version of Aspose.Email for .NET 5.5.0 and share your feedback with us? Please let us know if the issue still occurs at your end or not. We have tested it at our end with the following test environment and were not able to reproduce it with this latest version of the API.
Test Environment Details
Xamarin Studio Version 5.7 (build 660)
Runtime: Mono 3.12.1 ((detached/b7764aa); GTK+ 2.24.23 (Raleigh theme); Package version: 312010000;
Operating System Mac OS X 10.10.0