EMail reply uses global default account instead of the account of the replied-to message

UNCONFIRMED
Unassigned

Status

UNCONFIRMED
4 years ago
3 years ago

People

(Reporter: mitch, Unassigned, NeedInfo)

Tracking

31 Branch
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141127111021

Steps to reproduce:

When replying to an email that was sent to an account that is not the default email account (SMTP + POP3), the reply is set by default to be the Thunderbird-wide default account rather than the account to which the original email was directed.

1. Verify that default account is "A"
2. Click Reply button for an email sent to account "B"


Actual results:

The default "from" account for the reply is set to "A".  The signature block for "A" is also inserted.


Expected results:

The draft reply should be set to be from account "B", including the proper signature block.

This was working until a few versions ago (sorry, don't remember exactly when it broke).
I'v tested in safe mode with all add-ons disabled and behavior is the same.

Comment 1

4 years ago
I confirm this bug on Win7+Th31.4 (also with all addons disabled)

This bug repeat continuously in almost every new instance of Thunderbird I have tested since ver 24. I still need to stand on version 24.8.1 which is not affected. A lot of new versions of TB were released since 24.8.1 and this bug which is really HUGE (if you do not care you answer from DIFFERENT ACCOUNT/EMAIL) is still present.

Comment 2

3 years ago
Do you see this problem when using version 45?
If you do, then I think this is a duplicate of another bug
Flags: needinfo?(orwel01)
Flags: needinfo?(mitch)
(Reporter)

Comment 3

3 years ago
I'm stuck on 38.6 from the Ubuntu 14.04 repository.  
Is there a good/safe way to use later versions with Ubuntu?

Comment 4

3 years ago
I can confirm this bug is present on TB45. I am on Win7.
Flags: needinfo?(orwel01)
You need to log in before you can comment on or make changes to this bug.