Author |
|
Sneidr Newbie
Joined: 10 April 2008 Location: Czech Republic
Online Status: Offline Posts: 2
|
Posted: 10 April 2008 at 11:46am | IP Logged
|
|
|
Hi all,
I'm using .NET objects 3.0. With POP3 component I check new emails from some POP3 servers. I have problem to connect to one POP3 server with SSL on port 995 (other servers with port 995 and SSL connection works fine).
MailBee log:
[20:06:05.61] [INFO] Assembly version: 3.0.2.79.
[20:06:05.60] [INFO] Will resolve host "eva.fit.vutbr.cz".
[20:06:05.62] [INFO] Host "eva.fit.vutbr.cz" resolved to IP address(es) 147.229.176.14.
[20:06:05.63] [INFO] Will connect to host "eva.fit.vutbr.cz" on port 995.
[20:06:05.66] [INFO] Socket connected to IP address 147.229.176.14 on port 995.
[20:06:05.67] [INFO] Will create TLS/SSL credentials.
[20:06:05.67] [INFO] TLS/SSL credentials created.
[20:06:05.67] [INFO] Will start TLS/SSL negotiation sequence.
And it's all. At this time my server processor is runnig at 100%, any MailBee Exception was thrown, IP connection on this POP3 server is still open.
Here is part of my .NET C# code:
using MailBee;
using MailBee.Mime;
using MailBee.Pop3Mail;
using MailBee.Security;
...
Pop3 pop3mail = new Pop3();
pop3mail.ThrowExceptions = true;
pop3mail.SslMode = SslStartupMode.OnConnect;
pop3mail.Timeout = 10000;
pop3mail.Connect("eva.fit.vutbr.cz", 995);
...
On "Connect" my application use 100% of system processor.
I don't know configuration of POP3 server "eva.fit.vutbr.cz".
In this case "pop3mail.Timeout = 10000;" doesn't work.
Sorry about poor english
|
Back to Top |
|
|
Andrew AfterLogic Support
Joined: 28 April 2006 Location: United States
Online Status: Offline Posts: 1189
|
Posted: 11 April 2008 at 6:15am | IP Logged
|
|
|
Thank you for the log file, the source code and the detailed issue description, they were very helpful for investigation.
We tried to establish SSL connection to the mail server via various e-mail clients (Outlook Express, Thunderbird, The Bat!), but none of them was able to perform TLS handshaking to establish SSL tunnel successfully.
It looks like the server suddenly and not quite correctly closes connection. Perhaps, this is because of security measures of the mail server like white/black lists of IP addresses or something of this kind.
Are you able to connect to the mail server via another e-mail client like Outlook Express?
With regard to 100% CPU load, this is not quite correct error handling in MailBee.NET Objects which happens in some cases when TLS handshaking fails. We'll fix this, but this wouldn't resolve the issue with strange mail server behavior and wouldn't allow you to connect to the mail sever because of the reasons above, it'll be just more correct error handling.
Best regards,
Andrew
|
Back to Top |
|
|
Andrew AfterLogic Support
Joined: 28 April 2006 Location: United States
Online Status: Offline Posts: 1189
|
Posted: 11 April 2008 at 6:48am | IP Logged
|
|
|
The updated version of MailBee.NET.dll is available here. Now, it doesn't load 100% CPU in such case.
Best regards,
Andrew
|
Back to Top |
|
|
Sneidr Newbie
Joined: 10 April 2008 Location: Czech Republic
Online Status: Offline Posts: 2
|
Posted: 12 April 2008 at 5:28am | IP Logged
|
|
|
Thank's for update, now it's work OK.
For me is sufficient when MailBee throw an exception when this error occurs.
|
Back to Top |
|
|