Closed Bug 1677093 Opened 4 years ago Closed 4 years ago

Reply to bcc message replicates original from account and to addressee

Categories

(Thunderbird :: Message Compose Window, defect)

x86_64
Windows 7
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mozilla, Unassigned)

Details

I'm new, couldn't find a recent bug like this within 5 years.
This has happened while I'm logged into several mail accounts on one single domain. If a@mydomain sends a message to b@wherever with bcc to me@mydomain, then I reply, the compose window sets from a@mydomain and addresses to b@wherever, which can lead to embarrassing passing on of comments that b shouldn't see.

Replies to your own identities are treated as follow-ups (reply to self). Is that what you're referring to?

I think in terms of accounts. In my example, I have my own account, me@mydomain, and my wife's, a@mydomain, both open (logged in via passwords). She sends to the external address, b@wherever, with bcc to me@mydomain. Opening the bcc in the me@mydomain inbox, I click reply, and the compose window fills in from a@mydomain to b@wherever, instead of from me@mydomain to a@mydomain. If I write something critical to my wife but it goes to b@wherever apparently from her, it's bad.

And both accounts me@mydomain and a@mydomain set up in the same Thunderbird?
You can set the mailnews.reply_to_self_check_all_ident preference to false in the Config editor to avoid this if they are on different accounts. If you set them to identities of the same account, you can't avoid it.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID

Yes, both accounts logged into on my one and only Thunderbird installation. I've looked into Identities - each account obviously has a default identity whilst, as it happens, me@mydomain has a second identity, which won't be accessed when I merely click reply (invoking default). The potential to solve this on my first adventure into the Config editor suggests to me that this unwanted behaviour would be a bug for the majority of users in this unusual situation, but I'm content to try your solution, thanks.

You need to log in before you can comment on or make changes to this bug.