Closed Bug 1682108 Opened 4 years ago Closed 3 years ago

blind copy setting in account settings does not trigger BCC being set in replies

Categories

(Thunderbird :: Account Manager, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: winfried.meining, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Steps to reproduce:

Configured blind copy to my own address in account settings -> copies and folders
Clicked on reply to a message which was not sent by myself.

Actual results:

Message editor opens.
From/To/Subject fields are automatically filled.
BCC input field is neither shown nor filled

Expected results:

BCC input field should be shown and filled by my own address

Me too (using Thunderbird 78.6.0)
My reproduce:

  1. Select one mail for replying
  2. "reply to all"
  3. (sometimes) Bcc is appeared as expected ... OK
  4. Discard reply message
  5. "reply to all" again on same message
  6. Bcc is NOT appeared ... BAD

I am observing this issue too. It does not seem to be 100% reproducible, but one scenario which always seems to provoke it is to reply twice (or more) in quick succession. The first reply window that pops up usually has the bcc, but I find that the second and subsequent ones never do.

Do you see this issue when using versino 91?

Flags: needinfo?(winfried.meining)
Flags: needinfo?(shunichi.goto)
Flags: needinfo?(m)

This issue doesn't happen with my reproducing pattern using 91.9.
It seems have been fixed.

Flags: needinfo?(shunichi.goto)

Thanks for the update

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(winfried.meining)
Flags: needinfo?(m)
Resolution: --- → WORKSFORME

Works for me too (version 91.9.0)

I haven't noticed the problem recently so it looks like it is fixed for me too.

Note bug 1699159 about shared auto-(b)cc's getting lost when switching sender identity in composition, which is confirmed.

See Also: → 1699159
You need to log in before you can comment on or make changes to this bug.