1851512 - Replies to emails received via BCC use the wrong identity

Status: RESOLVED FIXED

(Thunderbird :: Message Compose Window, defect)

Description

[Oliver Hiorns [:oshbug]]

Steps to reproduce:

Received an email via BCC to a specific identity, let's say the sender addressed me as BCC: [e-mail]. I have an identity set up with this specific address. I then replied to the email.

Actual results:

The from: field auto-populated with the default account identity ([e-mail]) rather than the identity which received the email ([e-mail]).

Expected results:

The from: field auto-populated with the identity to which the email was sent (in this case [e-mail]).

(Is this desired functionality impossible because there is no standard email header field for the address to which the email was sent, and BCC means the recipient's address is never actually specified? Even if this is the case, GMail seems to have a Delivered-To: header, and other common email providers may have similar, so would it be worth adding a case for these common providers?)

Comment 1

[Hartmut Welpmann [:welpy-cw]]

As a quick workaround it should work when catch-all is enabled for a default identity. The headers to check are defined in the mail.compose.catchAllHeaders preference. Maybe you have to add delivered-to there yourself.

Without catch-all there is code that checks at least the Delivered-To: header, unfortunately it is not functional right now (since bug 1789774).

Maybe the catch-all code could be extended to cover the BCC case also.

Comment 2

[Hartmut Welpmann [:welpy-cw]]

Attachment: Bug 1851512 - Fix currentHeaderData in ComposeMessage. r=mkmelin

Comment 3

[Hartmut Welpmann [:welpy-cw]]

This fix should restore the behavior of TB 102 regarding the Delivered-To: and List-Post: headers. Please note that the message you want to reply to has to be currently displayed. Using the context menu of another message does not process these special headers.

Comment 4

[Magnus Melin [:mkmelin]]

The original premise of this bug seems incorrect. You never have Bcc in your headers, unless it was in your sent folder for something you sent yourself. But replying to self would use the same From as original.

Comment 5

[Cimbali]

As I understand it, the premise is just receiving an email as BCC recipient, which definitely can happen. You don’t receive the BCC header, but may have a Delivered-To, so Thunderbird should attempt to reply with the receiving identity.

The report does not specify that the recipient sees the actual BCC field, just that it’s used to send the email.

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/bf3a3b9be2ff
Fix currentHeaderData in ComposeMessage. r=mkmelin

Comment 7

[Wayne Mery (:wsmwk)]

Comment on attachment 9351873 [details]
Bug 1851512 - Fix currentHeaderData in ComposeMessage. r=mkmelin

[Triage Comment]
Approved for beta
(low risk)

Comment 8

[Daniel Darnell [:dandarnell]]

Thunderbird 118.0b4:
https://hg.mozilla.org/releases/comm-beta/rev/5458a23b7b6c

Comment 9

[Hartmut Welpmann [:welpy-cw]]

Comment on attachment 9351873 [details]
Bug 1851512 - Fix currentHeaderData in ComposeMessage. r=mkmelin

[Approval Request Comment]
Regression caused by (bug #): 1789774
User impact if declined: wrong identity pre-selected for replies to BCC messages
Testing completed (on c-c, etc.): currently on beta
Risk to taking this patch (and alternatives if risky): low

Comment 10

[Wayne Mery (:wsmwk)]

Comment on attachment 9351873 [details]
Bug 1851512 - Fix currentHeaderData in ComposeMessage. r=mkmelin

[Triage Comment]
Approved for esr115

Comment 11

[Daniel Darnell [:dandarnell]]

Thunderbird 115.2.3:
https://hg.mozilla.org/releases/comm-esr115/rev/6db3d73849cd