Open Bug 1795118 Opened 2 years ago Updated 1 year ago

mail.compose.warn_public_recipients fails for nested mailing lists

Categories

(Thunderbird :: Message Compose Window, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

People

(Reporter: marcausl, Unassigned)

References

Details

(Keywords: privacy, ux-implementation-level)

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

Steps to reproduce:

Created an address list which contains address lists. The fully expanded set of addresses is longer the the public recipients limit. Create an email with the list name in the to field.

Actual results:

No warning of too many recipients in the To: field is created, and the mail can be sent without warning even if aggressive is on.

Expected results:

The check for too many recipients should completely expand the list of lists to get a correct count and create the warning and if aggressive require confirmation.

I concur, the implementation should be improved to consider the correct count of contacts in a nested mailing list.
This constitutes a substantial and unexpected violation of privacy, including potential legal repercussions when privacy legislation is violated.
Imagine enterprise having Customers America, Customers Europe etc. mailing lists, and a global mailing list containing these sub-lists. Perfectly legitimate and plausible scenario which will fail to alert.

Severity: -- → S2
Component: Untriaged → Message Compose Window
Summary: mail.compose.warn_public_recipients fails for lists of lists → mail.compose.warn_public_recipients fails for mailing lists containing mailing lists
Summary: mail.compose.warn_public_recipients fails for mailing lists containing mailing lists → mail.compose.warn_public_recipients fails for nested mailing lists

Confirming for 102.3.3 (64-bit), Win10.
Thunderbird also won't display nested lists well, i. e. it displays and pseudo-allows editing of a sub mailing list item as if it was a single contact.

Status: UNCONFIRMED → NEW
Ever confirmed: true
See Also: → 1795807
You need to log in before you can comment on or make changes to this bug.