Red Hat Bugzilla – Bug 201527
It displays "Draft (1)" when there is no message in Draft folder
Last modified: 2008-08-02 19:40:35 EDT
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Launch Mail-Evolution and create a new Mail Message
2. Click "Save Draft" on Toolbar and Close the "Compose Message" Window
3. Click "Drafts" under "On This Computer" and "Junk" this draft message
4. Check "Drafts" and "Junk" folders
The message is saved in "Junk" folder, but "Drafts" folder displays "Drafts (1)"
When there is no messeage saved in Draft, it should be "Draft" instead of "Draft
Created attachment 133714 [details]
Can you plese upgrade to evolution-2.7.91 and try this one again? I'm having a
hard time reproducing the bug on the latest Rawhide release.
The saved draft is immediately marked as read, so I never see the Drafts (1).
I have a similar issue with Evolution-2.8.0-7.fc6 : When i receive two emails,
mark them as read, folder becomes INBOX from INBOX(2). Then i shut down
Evolution, on the next launch the folder is bold INBOX(2) again, but when i
click it, it immediately becomes normal INBOX. This occures even after sync with
Is there a test server we can use which has this problem? We are unable to
Is this problem still present on Fedora 8 Test 2 or later?
Oops... didn't mean to close this.
I can reproduce this with draft folder, so this part I moved upstream. 
The second part, Michal's, I cannot reproduce, even I noticed this occasionally.
From my point of view: evolution stores states of folders somewhere, this state
is not stored every time the change is done, so if one closes evolution before
it is saved, then after new start you see state like before, which is fine
because new resync will fix it. But, when folder is synced before restoring
saved state, then it can remain in previous/wrong state. Just a guess. BTW, I'm
sure, there is other bug for this issue.
Upstream bug is fixed in Rawhide and Michal's issue is no longer reproducible
for me either (possibly fixed). Feel free to reopen if you see either of these
Oops, didn't mean to change the resolution.