Since upgrading to 3.99.24 I have been getting this error message very intermittently, but sometimes for hours.. I noticed another poster had had the same problem, but he seems to have resolved the problem by fiddling with his Karpasky FireWall.
I have the same problem, but am not using Karpasky but Comodo instead. Shutting down Comodo completely makes no difference.
The strange thing is that I get the error message when accessing web based email accounts while traveling or from within my office network. Accessing my local email server in the office I never have a problem. This little server is very fast and local.
It almost seems that The Bat is timing out prematurely. When using a very slow WiFi internet connection in France last week I could hardly send any emails. I would have to keep trying to send about 50 times before it would suddenly work. Very annoying and many emails that were fairly urgent to send did not get sent. My communication with supplier and customers alike became all confused.
I am not sure if TB is timing out as it sometimes sits and spins for a while before coming back with the error message.
What might be the problem? Has something changed in the 3.99.24 version?
I have the same problem, but am not using Karpasky but Comodo instead. Shutting down Comodo completely makes no difference.
The strange thing is that I get the error message when accessing web based email accounts while traveling or from within my office network. Accessing my local email server in the office I never have a problem. This little server is very fast and local.
It almost seems that The Bat is timing out prematurely. When using a very slow WiFi internet connection in France last week I could hardly send any emails. I would have to keep trying to send about 50 times before it would suddenly work. Very annoying and many emails that were fairly urgent to send did not get sent. My communication with supplier and customers alike became all confused.
I am not sure if TB is timing out as it sometimes sits and spins for a while before coming back with the error message.
What might be the problem? Has something changed in the 3.99.24 version?