1180633 - Reply to all with me on Bcc of original message should warn that my identity will be exposed to the recipients

Status: NEW

(Thunderbird :: Message Compose Window, enhancement)

Description

[Marco A.G.Pinto [:marcoagpinto]]

Hello!

At the university webmail when I hit "reply all" and I was in Bcc, it showed a warning that if I reply to all, everyone will know I also had received that e-mail.

Can you guys add such a feature to TB?

Thanks!

Comment 1

[:aceman]

Cool idea. We have a similar "privacy" request at bug 271405.

Magnus, once we are in a reply in the compose window, do we have a reference to the original message so we can check if we were in the recipients of it?

Comment 2

[Thomas D. (:thomas8)]

(In reply to :aceman from comment #1)
> Cool idea. We have a similar "privacy" request at bug 271405.
> 
> Magnus, once we are in a reply in the compose window, do we have a reference
> to the original message so we can check if we were in the recipients of it?

Even if we had that reference, we must not use it. After replying, the original message can be moved, deleted etc. The feature proposed here should still work, because we know that sender was on bcc when he starts the reply, and can store that information for later use.

Comment 3

[Magnus Melin [:mkmelin]]

I don't think we have that reference, though of course you could extract it.
I don't see why we'd restrict ourselves to replies though. So I'm duping this to bug bug 271405.

Comment 4

[:aceman]

I don't think this is a dupe as the features are different.

Comment 5

[Magnus Melin [:mkmelin]]

Yes but implementing bug 271405 would also fix this bug. And we want bug 271405 fixed. Why would you like to keep them both open?

Comment 6

[:aceman]

Because I do not think fixing bug 271405 will do anything to solve this one. What relation do you see?

Comment 7

[Magnus Melin [:mkmelin]]

Ah, I had read wrong on whose identity would be "revealed".

Comment 8

[Thomas D. (:thomas8)]

(In reply to :aceman from comment #1)

Cool idea. We have a similar "privacy" request at bug 271405.

Cool ideas have more chances of implementation when they are NEW (vs. Unconfirmed)!