Red Hat Bugzilla – Bug 597898
SMTP connection establishment to slow
Last modified: 2010-06-17 09:13:36 EDT
Description of problem:
Version-Release number of selected component (if applicable): 22.214.171.124
Hello, I am writing this text, because I noticed a problem that remains after many versions of Evolution. Here is a description.
I have two email accounts, one of them on an ISP provider (www.clix.pt) and the other on gmail. The CLIX one uses no SSL encription, gmail uses SSL. Now the problem is the difference of speed, in sending a message from one and the other, when compared, for example with Outlook Express.
In Outlook Express, both accounts take more or less the same time for sending an email (actually CLIX is faster than GMAIL). With Evolution, gmail is very fast, while Clix takes ages to accept the connection. I sometimes wait perhaps 30 minutes for evolution to be able to connect to the SMTP server and send the email.
The fail is on the connection attempt. Somehow Evolution is unable for much time to connect to the server with no SSL.
I noticed this difference on the same computer and connection with different operating systems (Window$ and Fedora 13).
Thanks for a bug report. Could you run evolution froma console like this, please:
$ CAMEL_DEBUG=all evolution &>evo.log
and try to send message from both accounts, and when it's finally finished, then close volution, strip private information from evo.log (there can be shown passwords, user names, server addresses and email addresses, sometimes message bodies and so on), and attach the file here, please? The may be shown why it takes so long (in case it returns some error and evolution retries again and again).
Thanks in advance.
OK, I seem to have succeeded in fulfilling your request. I'm attaching the evo.log file to this comment. :) It was taken while Evolution was trying to send two emails, using the "slow" account. :)
Created attachment 424607 [details]
Evo.log of Evolution trying to send two emails with "slow" account
Sorry for all this problem. For now it seems just a bad configuration of the server configuration.My mistake, really... I'll just close the bug. :) Problem solved.
No problem, good it's solved.