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 653936 - Cannot set time limit for "Marked messages as Read"
Cannot set time limit for "Marked messages as Read"
Status: RESOLVED DUPLICATE of bug 602378
Product: evolution
Classification: Applications
Component: general
3.0.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2011-07-04 10:57 UTC by ed
Modified: 2011-08-31 09:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ed 2011-07-04 10:57:24 UTC 
In the previous version of Evo, there was an option to "<ark message as read" after n seconds. 

Since my upgrade to 3.0.2 my unread messages appear in my search box labelled "Unread". However, if I try to read a message in this folder it almost immediately gets marked as read, disappears from the folder and keeps marking each unread message as read and disappearing.

In the previous release, I could read each message and they would remain in the UNREAD folder until I either looked in another folder or new mail arrived.
Comment 1 Akhil Laddha 2011-07-04 11:49:10 UTC 
looks similar to bug 602378
Comment 2 Milan Crha 2011-08-31 09:23:57 UTC 
Thanks for a bug report. There are two things you are mixing together:
a) the option for "Mark messages as read after X seconds" is gone in the UI
b) unread folder 'reads messages for you'

the a) was done for a purpose I do not understand, same as many other options were dropped from preferences. This one is very standard option, thus its removal doesn't make any sense to me, except of bothering users with options which they cannot change.

the b) is Akhil's bug and it causes trouble for you. I'm marking this one as a duplicate of it.

*** This bug has been marked as a duplicate of bug 602378 ***