| Author |
|
mackolo22
Groupie
Joined: 09 October 2018
Location: Poland
Online Status: Offline
Posts: 41
|
| Posted: 21 January 2019 at 8:27am | IP Logged
|
|
|
Hello,
our user reported an error during logging to his mail account. I checked that Connect() method from Imap object throws an exception:
"IOException occurred during SSL negotiation. InnerException message follows: Authentication failed because the remote party has closed the transport stream."
Imap client is configured as follows:
Imap client = new Imap() { ThrowExceptions = true, Timeout = 5000 };
client.SslMode = SslStartupMode.OnConnect;
client.SslProtocol = SecurityProtocol.Auto;
client.Proxy.Protocol = ProxyProtocol.NoProxy;
client.Connect(serverName, port);
Server name and port are valid. The same account in Thunderbird with the same configuration works fine. What can cause this problem? Should I set some property of Imap client? Version of our MailBee.NET dll is 10.0.4.507.
Thanks for help and regards.
|
| Back to Top |
|
| |
mackolo22
Groupie
Joined: 09 October 2018
Location: Poland
Online Status: Offline
Posts: 41
|
| Posted: 21 January 2019 at 8:51am | IP Logged
|
|
|
And the type of exception is MailBeeSslNegotiationException.
|
| Back to Top |
|
| |
mackolo22
Groupie
Joined: 09 October 2018
Location: Poland
Online Status: Offline
Posts: 41
|
| Posted: 21 January 2019 at 9:54am | IP Logged
|
|
|
I found out that my version of MailBee.NET dll has got an old version of SecurityProtocol enum. Its fields are: Auto, Ssl2, Ssl3 and Tls1.
According to your documentation (https://afterlogic.com/mailbee-net/docs/MailBee.Security.SecurityProtocol.html), I see that there have been added 3 new values (Tls11, Tls12, TlsAuto).
I downloaded the newest version of MailBee.NET via nugget, used trial key and then it works!
|
| Back to Top |
|
| |
Alex
AfterLogic Support
Joined: 19 November 2003
Online Status: Offline
Posts: 2206
|
| Posted: 21 January 2019 at 10:07am | IP Logged
|
|
|
Yes, the current version does support TLS 1.2 (Tls12) and also provides the ability to automatically downgrade to TLS 1.0 if TLS 1.2 is not supported (TlsAuto).
Regards,
Alex
|
| Back to Top |
|
| |
mackolo22
Groupie
Joined: 09 October 2018
Location: Poland
Online Status: Offline
Posts: 41
|
| Posted: 22 January 2019 at 12:08am | IP Logged
|
|
|
It means that the mail server rejects requests via SSL and TLS 1.0 and only allows TLS 1.1 and 1.2, right?
I've got another question. Previous developer was responsible for MailBee library in our project so now I'm not sure if we can upgrade it to newer version without cost. Using new dll and old license key throws an exception 'LicenseKey is for an older version of MailBee.NET components.'. Does it mean that we have to buy new license?
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6038
|
| Posted: 22 January 2019 at 12:44am | IP Logged
|
|
|
Code:
| It means that the mail server rejects requests via SSL and TLS 1.0 and only allows TLS 1.1 and 1.2, right? |
|
|
Yes, it looks that way.
Code:
| Does it mean that we have to buy new license? |
|
|
It depends on whether your maintenance contract is still valid. You can check that at Maintenance Renewal page, and renew if needed. If maintenance contract is valid, you can request the license key update at our HelpDesk.
--
Regards,
Igor, Afterlogic Support
|
| Back to Top |
|
| |
mackolo22
Groupie
Joined: 09 October 2018
Location: Poland
Online Status: Offline
Posts: 41
|
| Posted: 22 January 2019 at 12:51am | IP Logged
|
|
|
Hi Igor!
Thank you very much for your help :) Maintance Renewal page says that the license key wasn't found in records. I will contact your support and hopefully I'll be able to update MailBee.
Regards.
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: Problem during SSL negotiation.
Privacy policy |
Refund policy