From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131
Description of problem:
I am attempting to use evo to connect to my exchange server using POP mail. In
previous versions it seemed ok...but now when you do a send/recieve it takes up
to about 3 minutes to complete when there are no new messages at all(mail is
stored on the server and not deleted). I only experience this when connecting
to exchange, when I connect to sendmail MTA's all seems very responsive..
It is almost like something is timing out?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Add an account that connects to the exchange server using pop
2.do a send/recieve
Actual Results: very slow...I understand the slowness the first time..it has to
download all mail, but every time after that should be speedy shouldn't it?
Expected Results: Resonsive send/recieve when there is no new mail...
If you run
from a terminal and then start evolution once that's ready, is there a lot of
traffic between the local client and the Exchange server?
Closing due to inactivity
I am seeing this too.
Can this bug be reopened ?
Evolution 1.2.2-5 (RH9) is showing big performance problems with fetching mail
from a pop server. I have a cable connection to the internet (~800Kbit/s download)
Receiving new messages from my pop server seems to be exponential.
3 new messages: about 7 seconds
12 new messages: about 3-5 minutes
15 new messages: about 30 mintues
35 new messages: haven't seen this finish....
top shows that evolution is spending 100% cpu. (It isn't spending any noticably)
As I get typically >35 messages a day this really is a problem :)
Accessing the same mail server from a webmail interface is very responsive.
Any more details I can provide ?
Whoops a typo
>top shows that evolution is spending 100% cpu. (It isn't spending any noticably)
This shoud be:
top shows that evolution is _not_ spending 100% cpu. (It isn't spending any cpu
OK, I found the cause of the slowlyness of evolution. Its not caused by
evolution. It was spamassassin.
I am using spamassassin from evolution to check each message. spamassassin uses
osirusoft.com to check wether it comes from a known spamsite. osirusoft.com is
down... -> spamassassin checking takes for ages.
Creating the following file:
with the following content:
score RCVD_IN_OSIRUSOFT_COM 0
score X_OSIRU_DUL 0
score X_OSIRU_DUL_FH 0
score X_OSIRU_OPEN_RELAY 0
score X_OSIRU_SPAM_SRC 0
score X_OSIRU_SPAMWARE_SITE 0
fixed the problem completely for me.