GNOME Bugzilla – Bug 484380
Mark as read does not work on folder hierarchy
Last modified: 2010-05-20 11:32:19 UTC
The bug has been opened on https://bugs.launchpad.net/bugs/149314 "Binary package hint: evolution I have a Searchfolder hierarchy to keep things organized. If I select "mark as read" from the context menue, evolution asks if it should be performed on the folder or on the folder and its subfolders. Selecting the subfolders option, nothing really happens, all mails stay unread. using gutsy beta with updates applies as of 04. october ... create two searchfolders , the first one called test/folder1, the second one test/folder2, make sure that some unread mails are listed in these These show up as test | +-- folder1 (2) | +-- folder2 (5) now, select test, right click and select "mark as read" a dialog box pops up asking weather i want to mark all mails in test as read or recursively through all subfolders. select the recursive option the dialog closes, nothing really happens, the mail stays unread :-("
The "Mark all read" plugin does not work recursively on vfolders. I am not sure why -- when I changed the behaviour (see bug 453544) Sri asked me to keep the check ("if it is a vfolder, then do not mark all read", pretty much). But this test is only executed if we are recursively navigating a folder structure, and the current folder is a vfolder (but not the topmost one -- there nothing is tested, and all mails are marked read, even if it is indeed a vfolder). So, the questions are actually: (1) can recursive vfolders be marked as read? (2) why is the test required (i.e., where can I find info on that)?
This is fixed in 2.28. Can we close this now?
Closing per comment #2