After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554468 - imap folders not getting updated correctly with evolution 2.24
imap folders not getting updated correctly with evolution 2.24
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-09-30 17:42 UTC by tjb
Modified: 2011-02-08 15:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description tjb 2008-09-30 17:42:06 UTC
Please describe the problem:
I'm having problems on multiple systems running the Fedora 10 beta and evolution 2.24.0 where imap folders are not being represented accurately. They are not always updated correctly, sometimes showing mail that is no longer present on the server, sometimes not showing mail that I know is on the server. It seems to be happening on mailboxes that often get cleaned out completely like my procmail possible spam folder. The imap server is running dovecot-1.0.15-10.fc9.x86_64. This does not happen with evolution-2.22.3.1-1.fc9.x86_64.

No amount of restarting, refreshing, etc. will make evolution update it's view of the misrepresented imap folder. 

Steps to reproduce:
1. I haven't found a way to consistently reproduce it.
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Srinivasa Ragavan 2008-10-01 04:30:45 UTC
Just do one this. 

sqlite3 ~/.evolution/mail/imap/<account>/folders.db
drop table 'folder_name'
delete from folders where folder_name = 'folder_name'

Where folder_name is the actual folder. This cleans up the summary once.
It delete the summaries of the foler, which will be fetched from the server again.

Now, start up fresh and try to see if it happens. Try and see a pattern if you can.
Comment 2 tjb 2008-10-01 15:35:36 UTC
OK, as requested I removed the table, etc, restarted Evolution and it updated the problematic folder correctly. I then quit, went over to my laptop which is also running F10b and used evolution to delete everything in that folder. Quit from laptop, went over to desktop, restarted evolution, and it didn't update the folder view. (So now it essentially has a list of emails that no longer exist on the server.) I then deleted all in the folder and it showed no messages. Quit and restart evolution and it updated the folder view correctly. I'm not sure what can be drawn from this. 
Comment 3 tjb 2008-10-02 14:25:49 UTC
I've got a folder right now that is showing no messages in it even though I just dragged 5 new messages into it. I moved some spam from my inbox to this folder. Quitting and restarting evolution did not update the folder. What info from the sqlite database would you want in a case like this?
Comment 4 tjb 2008-10-30 12:24:45 UTC
The 2.24.1 release fixed most problems I've been having. The one problem I see still is the folder list saying there's a new unread message in a folder when there aren't any. What exactly does the right-click on a folder context menu->refresh do? Couldn't it be made to actually completely refresh a view of an imap folder? It doesn't seem to do anything now.
Comment 5 Srinivasa Ragavan 2008-11-03 05:29:06 UTC
Cool. On the last bug you have, any steps you do to get it actually?
Comment 6 tjb 2008-11-03 15:27:20 UTC
It seems to happen when other mail agents update a mailbox. For instance, right before I start evolution, I ssh to my two mail servers and run spamc on ham and spam folders and then remove any mail in those folders. Or if I read mail from my laptop and delete all mail in a folder, when I go back to my desktop, if the mailbox is still empty (no mail has since been put in that folder by procmail) evolution will show it having the mail counts it thought is used to have. If new mail has since arrived, evolution shows the message counts correctly.

Another somewhat related problem I'm now having is speed or lack of it. I am on a number of mailing lists and use them more as references when I need to look something up quickly. As such, many are filled with lots of unread messages. It seems to take evolution forever to get through checking for new mail now but only on my workstation. (I have check for new mail in all folders because I use procmail to filter my maildir imap mailboxes.) On my workstation, I have an NFS mounted home directory talking to an imap server. On my laptop, I have local storage talking to the imap server. The laptop doesn't have any speed problems but the workstation does. I don't know if sqlite over nfs is inherently slow or what but my workstation and the nfs server are on the same gigabit switch so network speed should not be an issue. This was never a problem with the older version of evolution. I'm in the process right now of marking a bunch of mail in those large folders are read and it's been going now for over 10 minutes. We're talking less than 100,000 messages though camel_verbose_debug is on, slowing things down somewhat.
Comment 7 tjb 2008-11-06 14:55:02 UTC
Some good news. After a kernel update to my server and subsequent reboot, the nfs mounted home directory situation is much better. There may have been some nfs kernel problems between the F9 server and the F10 client. Things are much more usable, though probably not quite as peppy as the Evolution 2.2.

One area I'm still experiencing unexplained slowness is composing a reply or new message. It takes over 30 seconds for a compose window to appear. Any clues as to how to debug this?
Comment 8 Matthew Barnes 2008-11-06 16:02:13 UTC
How many dictionaries do you have enabled?

That was the cause of some slowness prior to the 2.24.0 release, but I thought I had fixed that.
Comment 9 tjb 2008-11-06 16:49:44 UTC
Just one, American English.
Comment 10 tjb 2008-11-25 13:42:42 UTC
I've updated to 2.24.2 and things generally seem much quicker. Unfortunately, I'm still having the same problem described in comment #6.
Comment 11 Akhil Laddha 2010-03-31 05:49:25 UTC
If possible please try out improved IMAP support IMAPX (IMAP+) which is a part of  evolution 2.30.0 and let us know if it improves performance.
Comment 12 Akhil Laddha 2010-12-24 06:49:18 UTC
Could you please confirm if this bug is still happening at your end ? Please try in 2.30.3 or 2.32.1 and report back, thanks.
Comment 13 Tobias Mueller 2011-02-08 15:02:30 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!