18.9 SecurityOptions no longer working

Aspose.Email Product Family
1

was reading and sending via imap / smtp just fine with my test outlook.com account up until I upgraded to 18.9 over the weekend.
now I get The specified value is not valid in the ‘SslProtocolType’ enumeration.
Parameter name: sslProtocolType

am using
client.SecurityOptions = Aspose.Email.Clients.SecurityOptions.SSLExplicit
has something changed that I need to add?

2

@gavinduffy

We were able to reproduce this issue and have logged it under ID “EMAILNET-39125” for further investigation. You will automatically be informed here once we have more information to share.

3

@gavinduffy

You may set up encryption protocols for specified instance like as given below:

client.SupportedEncryption = EncryptionProtocols.Tls12;

4

tried adding this where i specify the ssl SecurityOptions, no luck.
the next call client.ListFolders() hangs.
i get the timeout message:
Connection failure. Timeout ‘200000’ has been reached.
in my code i have: client.Timeout = 30000

5

@gavinduffy,

We were unable to reproduce the issue that you reported. We used the code snippet given below for testing.

ImapClient imapClient = new ImapClient();
imapClient.Host = "imap-mail.outlook.com";
imapClient.Port = 993;
imapClient.Username = "Email";
imapClient.Password = "Password";
imapClient.SupportedEncryption = EncryptionProtocols.Tls12;
imapClient.SecurityOptions = SecurityOptions.SSLImplicit;

ImapMessageInfoCollection msgsColl = imapClient.ListMessages();
Console.WriteLine("Total Messages: " + msgsColl.Count);
ImapFolderInfoCollection folderColl = imapClient.ListFolders();
Console.WriteLine("Total Folders: " + folderColl.Count);

We hope that this fixed the issue that you were facing. Please feel free to reach us if further assistance is required.

6

changing from explicit to implicit fixed it.
i was under the impression tls required explicit.
for your test, specify a timeout and explicit, the timeout will not trigger.

thanks for the fix.

7

@gavinduffy,

It is good to know that your issue has been resolved. If additional information is required, please free to contact us. We will be more than happy to assist you further.

8

The issues you have found earlier (filed as EMAILNET-39125) have been fixed in this update. This message was posted using BugNotificationTool from Downloads module by MuzammilKhan