default identity used when replying to mail sent from non-default identity

NEW
Unassigned

Status

Thunderbird
Message Compose Window
8 years ago
2 years ago

People

(Reporter: Kyle Altendorf, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.41 Safari/534.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.11) Gecko/20101006 Lightning/1.0b2 Thunderbird/3.1.5 ThunderBrowse/3.3.2

When replying to a message that has been sent from a non-default identity the default identity is used instead.

Reproducible: Always

Steps to Reproduce:
1. Have multiple identities
2. Send mail from the non-default identity
3. Look in the sent mail folder and reply to the message sent above
Actual Results:  
The from address in the reply is the default identity

Expected Results:  
The from address in the reply is the address that originally sent the message

In general, I have threads carried out under my secondary identity.  If I reply to a message received at that identity it is also used in the reply and I expect the same to happen when replying to a message sent from that identity.

Despite the easy work-around, I feel that the risk of sharing an unintended email address justifies this as a normal severity rather than minor.  Also, given that the functionality is already present in a similar scenario I feel this is a bug and not an enhancement request.
Duplicate of this bug: 485517
Status: UNCONFIRMED → NEW
Ever confirmed: true
(Reporter)

Comment 2

8 years ago
(In reply to comment #1)
> *** Bug 485517 has been marked as a duplicate of this bug. ***

Perhaps this is just semantics but despite bug 485517 having been resolved at some point, this is not a duplicate of it.  The feature requested in bug 485517 (use appropriate identity when replying to a received message) is working fine for me and has been for a long time.  What is not working is replying to a message that I have sent.

Like I said, perhaps just semantics of 'duplicate', but I'd rather clarify sooner than later.

Comment 3

8 years ago
Dito. 
Same here (using Ubuntu 10.04 | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.1).

Had suffered several times from accidentially sending per wrong email address, which really shouldn't have happened. Caused lots of confusion.

Please fix this one soon.
Duplicate of this bug: 612894
(Reporter)

Comment 5

8 years ago
(In reply to comment #4)
> *** Bug 612894 has been marked as a duplicate of this bug. ***

Not really.  That bug refers to the user replying to a message sent to them at one of their identities.  This bug that I reported refers to reply to a message that I sent from one of my identities.  I have not been having the trouble described in bug 612894, quite to the contrary I am very pleased with the feature.

Do I not understand the meaning of 'duplicate' as used for these bugs?

Comment 6

8 years ago
You're right Kyle, 
thanks for pointing that out! 
I happened not to read your bug description close enough...

Comment 7

7 years ago
Confirm this bug, after several months and several major versions it has not been corrected yet. However, I believe the behavior is slightly different.

I think that the FROM: address in the example described above is not taken from the default identity but simply from the first identity in the list. Lucky you who have the first identity as your default - I don't and there is no way how to change order of the identities in the list ...

Updated

6 years ago
Duplicate of this bug: 745841

Comment 9

5 years ago
Possibly related to bug 889410?

Comment 10

3 years ago
Confirmed. This has been bothering me for a long time. Using Reply to All to add something to your previous message gets the identities wrong and has repeatedly caused hassle.

If I remember correctly, Outlook handles this right so that the new reply is sent from the same identity as the message being replied to.
You need to log in before you can comment on or make changes to this bug.