[RFE] Allow followups to mail messages

RESOLVED WORKSFORME

Status

--
enhancement
RESOLVED WORKSFORME
11 years ago
8 years ago

People

(Reporter: bugzilla, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; it; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11
Build Identifier: 2.0.0.9 (20071031)

I'd love the ability to send a follow-up to an already sent message.
Right now what I do is click Forward and type in the address of the original recipient. It's not that cumbersome, but it's very annoying if you have to do it multiple times every day.
Actually, the coolest thing I can think of is that when a followup is sent, a special header is inserted in the new message that may allow the recipient's UA to stick the followup to the original message (or maybe even replace the old message with the new one).

Reproducible: Always
Actually, all you have to do is hit reply to your own message...
(Reporter)

Comment 2

11 years ago
I don't know what version you're using, but in TB2 if I select "reply" after selecting a message in the "Sent" folder, the recipient is myself and not the original recipient(s).
Did yoy mean "edit as new" instead of "reply"? In that case, yes, the original recipient(s) is/are still there. But I don't think that the recipient's UA is able to understand that this second message is meant to replace the first one.
That was bug 377998, only goes that way if you were sending the mail between identities. Even with tb2, if no identities are involved and you send a mail to A, B and C, hitting reply to that message in the sent folder will make make this new message too addressed to A, B and C.

Comment 4

8 years ago
This should be WFM in current version
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 5

8 years ago
WFM in 3.1. Maybe some better choice of wording instead of "reply" would help less experienced users (for me as long as it works it's ok).
You need to log in before you can comment on or make changes to this bug.