Closed Bug 432638 Opened 17 years ago Closed 17 years ago

replied and forwarded messages do not change their flags (status, icons) if a reply was in the meanwhile saved as a draft (IMAP)

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 128996

People

(Reporter: prugimagi, Unassigned)

Details

User-Agent: Opera/9.26 (Windows NT 5.1; U; en) Build Identifier: 2.0.0.14 (20080421) In the event one replies or forwards an incoming message in IMAP folder with intermeadiately saving the reply or forward message as a draft (no matter in local or remote drafts folder) and then re-opened again and then sent, the original incoming messaage do not change its flag (status, icon) for "replied" or "forwarded" accordingly. Is tested for many servers and many accounts, some other users confirm this bug too. Reproducible: Always Steps to Reproduce: 1. Open a compose window to reply some message in Inbox of IMAP folder (account). (The same problem with forwarding message). 2. Write something in replying. 3. Save the reply message in local or remote folder "Drafts". 4. Close the compose window. 5. Go to the "Drafts" and open the unsent draft of the message. 6. OPTIONALLY: modify the message again (write or delete something etc) 7. Send now your reply or forward. Actual Results: Go back to Inbox: you'll see, that the icon of the replied or forwarded message is as clear as was before, its status (flag) has not changed. Expected Results: Replied or forwarded message status (flag) should change after I replied or forwaded it. The problem was previosly discussed in MozillaZine forum and tested by other users with different servers. Confirmed.
I have the same problem but I don't use IMAP, just conventional POP3/SMTP. The problem is exactly as described above.
Try 3.0alpha1, this was fixed by bug 128996.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.