GNOME Bugzilla – Bug 605456
Search folders not updating correctly
Last modified: 2010-03-26 14:09:38 UTC
Forwarding from a Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=538477 Description of problem: Evolution vfolders are not updating properly with 2.28 in F12. The simplest vfolder I have aggregates inboxes from two accounts. The criteria is 'Match All' and is applied to the specific inboxes. When initially created, this correctly showed all emails across both accounts. After quitting the client and starting it the next day, it shows 1/2 (unread/total) emails. The total for the two inboxes is around 42/150. On a different host (F12 and same version of evolution), I set up the same vfolder, quit, and then reopened a few hours later, it shows around 2/100 emails. Selecting Refresh on the folder does not do anything. Neither client is accessing the imap accounts at the same time. Recreating the vfolder results in the correct number of emails. Version-Release number of selected component (if applicable): evolution-2.28.0-2.fc12.i686 How reproducible: Always. Steps to Reproduce: 1. Create vfolder. 2. Quit and let mail build up for awhile. 3. Start evolution and check vfolder to see if it correctly shows all email. Actual results: Incomplete search results. Expected results: The full set of email from both inboxes. Another datapoint .... Started evolution at work this morning. As described above, the vfolder of all inboxes failed to show emails received overnight (unread or otherwise). The last email it shows is from when I closed my client around 18:00 yesterday. However, new email received after I started my client this morning does show up in the vfolder. Basically, there's a gap of email between 18:00 yesterday and 08:00 today. And one more. As I go through the individual inboxes, the read emails show up in the vfolder.
should be a duplicate of bug 565363 ?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 565363 ***