Comment 13 for bug 1012858

Created attachment 614146
Steps to reproduce

To be correct it took 50% on my machine. Now I checked per core and it took more or less equally around 50% from each core. So maybe its natural load. But the load is there since I clicked send [1], then timeout message appeared. Load was still there until I clicked either cancel sending [2] or OK on timeout message [3] which in turn cancels sending. But when cancel sending [2] is clicked then timeout message is still there, but load drops. So it's definitely not caused by timeout message, but the connecting part, and it takes load (quite high) even timeout message is there. See attached image for more explanation on steps.

From user perspective, this SMTP is supposed to be available and should require log in. Don't know why it timeouts for me or if the error is somewhere else. Try at different networks with same result. It might be related to this high load.

Secure connection is none, authentication is set to password.

C:\Users\Marek Nos>telnet smtp.centrum.cz 25
Connecting To smtp.centrum.cz...Could not open connection to the host, on port 25: Connect failed

It does work for you?