158306 - Re-sending a message from your 'Sent' folder (without using Edit as New, open to compose window)

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[bruno]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a+) Gecko/20020715
BuildID:    2002071504

When you open your local 'Sent' ( or remote IMAP 'Sent' folder ) you are able to
open a message, but you are *not able to edit the message and click 'Send' or
'Send Again.' I often find myself looking for a message in my sent folder,
adding some comment ( ie: " Joe, do you have any status updates for this
request?" ) and clicking send. A work around to this is to click "Reply All" and
taking myself off the "To:" field, but....

Reproducible: Always
Steps to Reproduce:
1.Send a message....
2.Open your 'Sent' folder ( either local, or remote )
3.Open the message that you just sent....
4. Notice you can't edit the message, or click 'Send' or 'Send again'

Actual Results:  Not able to open message ( to edit/add a comment etc... )and
click send again. The work around is to click "Reply AL" and taking yourself off
the list... but that's just weird, and not very straight forward....

Expected Results:  I should be able to look thru my 'Sent' folder ( both the
local, and remote [ie: IMAP sent folder] ) open a message I sent earlier that
week. Make some modifications or add a comment, anc click a 'Send' button...

Most major mail clients support this mail feature:
Eudora 5
Outlook Express 5, 6
Outlook 2000 --> cringe...

Comment 1

[Patrick Xia]

Right-click the message, and click Edit as New.
-> not a bug; INVALID

Reporter: Please reopen if you disagree.

Comment 2

[laurel]

marking verified.

Comment 3

[bruno]

It does leave say something about clarity...

The "Open Message in New Window" should have the same functionality as "Edit as
New" I can see several people getting confused with the "Open Message in New
Window" option.

OR

Maybe a simple re-organization of the menu for the sent folder should be considered.

1. "Open Messag in New Window" should be changed to "Open Message as Read-Only"
( or something similar )and moved down the menu.

2. The "Edit as New" menu function should be named "Open Message in New Window"
and moved to the top of the menu.

The way the menu is organized right now create an unecessary learning curve that
can be fixed relatively easily.

Comment 4

[laurel]

changing to enhancement, added clarification to summary.
I think opening to a composition window for Open in new window is more confusing
than having to use Edit as New, but there's no accounting for everyone's
preferences.

Comment 5

[Mike Fedyk]

There is already this functionality for the Drafts and Templates folders.  Sent
should behave exactly like the Templates folder, where messages when double
clicked it is opened in a compose window instead of a view window, and when the
message is sent, it stays in the folder (sent and templates).

Upon further investigation, I see that neither the Drafts or Templates folder
modify the "Open in New Window" option, only the double click action, if you are
in either Templates or Drafts "Open in New Window" will open the message in a
view window (not a compose window).

I am working at a company where I am transitioning my users over to Mozilla,
this is one of the features from the previous program (QuickMail) that they're
missing.  So, please don't discount this bug.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030326

Comment 6

[Mike Fedyk]

Does anyone have any plans for this bug?  This is hit by my users all of the
time.  And several are complaining.

Comment 7

[Gordon Schumacher]

Yeah - this needs to be clarified.  I had no idea that this was possible to do
in Thunderbird until reading this bug report, and I'm hardly a novice user.  How
about changing it to "Send Again" or "Resend" or something, so that it's not
completely different from all the other MUAs?

Comment 8

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420