446345 - phantom draft email in draft folders for POP3 account.

Status: RESOLVED INCOMPLETE

(Thunderbird :: Message Compose Window, defect)

Description

[Bart]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Thunderbird version 2.0.0.14 (20080421)

After saving a draft, 2 drafts show up in drafts folder. after sending the finished draft, draft folder still coming up with notice that there is still 1 draft in drafts folder but when you look inside draft folder there's none.

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1.composed new email, saved as draft
2.2 drafts are left on drafts folder
3.sent out email and one draft is left but no actual email is present in drafts folder.
4.draft and draft.msf files are showing email with status sent
Actual Results:  
phantom draft left in drafts folder

Expected Results:  
after sending draft out expected draft in draft folders to disappear

tried to rebuild index for drafts folder nothing changed
opened drafts and drafts.msf file and deleted contents to resolve
after clearing drafts and drafts.msf files able to save drafts and send out email as normal

Comment 1

[Bart]

Attachment: screenshot of phantom draft

what thunderbird shows after sending out email

Comment 2

[Bart]

Attachment: after creating new email while phantom draft is still present.

what you see is that the drafts folder reporting 2 drafts but the list on the right only having one email draft present

Comment 3

[Lech]

a cannot see anywhere the resolution to the problem of phantom drafts. My drafts folder is now showing 5 drafs while there is actually nothing visible there. Has anyone got any practical solution?

Comment 4

[[:Aureliano Buendía]]

Bart have you tried with compact folder?

Comment 5

[[:Aureliano Buendía]]

Bart, Lech could you answer to comment #4, please?

Comment 6

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to previous comment. If you feel this change was made in error, please respond to this bug with your reasons why.