Closed Bug 325301 Opened 19 years ago Closed 18 years ago

Replied icon in Main window does not appear if you first save the reply as a Draft

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 128996

People

(Reporter: mfong, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060122 Firefox/1.6a1 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1) Gecko/20060122 Firefox/1.6a1 The reply icon is supposed to tell you if an email has been sent. This works if you do a straightforward Reply. However, as I often do, if I fist "Save" my response in Drafts and then send the email, the email in my main window view does not track that sent message. Hence, it is misleading. You may end up replying the the same person becuase you thought the email had not been replied to yet. to already or not. Reproducible: Always Steps to Reproduce: 1. Click Reply to an email in your Inbox 2. Instead of sending out the email, "Save" it. 2. Go to Drafts and double-click on the saved email 3. Send that email Actual Results: The email is sent but there is no bookkeeping that the replyed-to email was sent. Expected Results: Expect to see the original email that was replyed to with a "Replied" icon. sw could be more discerning about scenarios of how repllies are done.
what version of thunderbird are you using? I believe this is fixed in trunk builds, and nightly 1.8.1 builds - ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-mozilla1.8
Can confirm it in Thunderbird 1.5.0.5, WinXP, German
Okay, I guess my reply was misleading. I can confirm the bug EXISTS in 1.5.0.5 - it is NOT fixed.
OK, I still believe it's fixed in 2.0 alpha and nightly trunk builds (if a bug is fixed in the latest code, it's marked fixed). It takes a while for the fix to make it into a released product, and the 1.5.0.x builds contain mainly security fixes - not all the fixes we've made since 1.5 shipped. Those fixes go into 2.0, the next major release.
*** This bug has been marked as a duplicate of 128996 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.