Closed Bug 1704390 Opened 3 years ago Closed 2 years ago

Adding or removing an address from a mailing list does not update the list pill in the recipient area of the compose window

Categories

(Thunderbird :: Address Book, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: lucjoqc, Unassigned)

Details

(Keywords: dataloss, privacy)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0

Steps to reproduce:

if I add (or delete) an email address in an address book mailing list and go back to the main email editing module

Actual results:

by entering the name of the mailing list (via Write- For (or CC or Bcc)), the new email address does not appear (or, if I deleted it in the mailing list, it still appears).

Expected results:

Changes to the mailing list made in the address book (additions or deletions) should be reflected when using this list in the main email writing module

Worksforme on TB 107.0a1 (2022-09-22) (64-bit), and 102.3.0 (64-bit), Win10.

This should have a dedicated testcase.

STR

  • create a mailing list called thelist with a@a.com, b@b.com, c@c.com
  • Write, type thelist in To field, confirm - list pill created.
  • In address book, add or remove addresses from the list, e.g. add d@d.com, or remove c@c.com
  • Go back to write window, right-click on list and Expand list.
  • Alternatively, File > Send later (Ctrl+Shift+Enter)

Actual == Expected Result

  • After expanding or sending later, recipients expanded from the list should match the last list update, i.e. removed members should be excluded, and added members should be included in the expanded set of recipients.
Severity: -- → S2
Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Keywords: dataloss, privacy
Resolution: --- → WORKSFORME
Summary: adding or removing an address from a mailing list does not work in the email editor → Adding or removing an address from a mailing list does not update the list pill in the recipient area of the compose window
You need to log in before you can comment on or make changes to this bug.