Can't compose to Mailing List with commas in display name

NEW
Unassigned

Status

MailNews Core
MIME
2 years ago
4 months ago

People

(Reporter: Will Rutledge, Unassigned)

Tracking

({regression})

regression

Thunderbird Tracking Flags

(thunderbird_esr38+)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36

Steps to reproduce:

Created Mail List with commas in name and/or description


Actual results:

rejects list


Expected results:

List used to work. When you delete the commas, it works again.

Comment 1

2 years ago
Hmm, so should it be allowed?
Keywords: regression
(In reply to Magnus Melin from comment #1)
> Hmm, so should it be allowed?

Sure, why not? We allow commas in display names of single recipients, so per ux-consistency, display names of mailing lists are no different... Also, unless we implement input checking, anything which user is able to enter should work (and comma is not particularly crazy, say you want a list called "Work mates, friends, and family")
Summary: Mail List Name Using Commas Now Invalid → Can't compose to Mailing List with commas in display name
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 3

2 years ago
(In reply to Thomas D. from comment #2)
> Sure, why not? We allow commas in display names of single recipients, so per
> ux-consistency, display names of mailing lists are no different... Also,
> unless we implement input checking, anything which user is able to enter
> should work (and comma is not particularly crazy, say you want a list called
> "Work mates, friends, and family")

The problem seems to be (by reading other bugs) that the quotes are not there in the recipient field.
Like we had problems with user@host <user@host> type addresses.
This one looks similar.
How is Work mates, friends (1 list) different from Work mates, friends (2 lists) ?
I think we keep the recipient as a plain string and then parse it into individual recipients.
And the single line inputs (proposed rewrite of recipient are) will make it even worse.

Outlook shows which characters belong to which recipient and highlights the individual recipients when clicked.

Updated

2 years ago
tracking-thunderbird_esr38: --- → +

Updated

2 years ago
Component: Address Book → MIME
Product: Thunderbird → MailNews Core

Updated

2 years ago
Duplicate of this bug: 1216098

Comment 5

2 years ago
I have this problem.  I upgraded to the latest version of Thunderbird and my lists stopped working.  If I take the description field out, the list works.

I am running Fedora 21 64 bit and Thunderbird 38.1.0.
The description field is a series of names with commas between the names.

Comment 6

a year ago
I have this problem.

If the description of the list contains commas then when you try to send the message you get an error saying that the format of the address is not user@host.

If the description does not contain commas, then the address list is expanded and the message is sent.

This happens when you type the address in the address field.
It also happens when you select it from the contacts list (F9). In this case quotes are included around the description, but the parsing still comes up with an error.

This does not happen if you select to write an email from within the Address Book as the address list is expanded into individual addresses first.

This bug is very difficult to find as the error message ("user@host") does not appear in the error description and searches come up only with bugs which have been resolved.

Comment 7

a year ago
(In reply to :aceman from comment #3)
> (In reply to Thomas D. from comment #2)
> > Sure, why not? We allow commas in display names of single recipients, so per
> > ux-consistency, display names of mailing lists are no different... Also,
> > unless we implement input checking, anything which user is able to enter
> > should work (and comma is not particularly crazy, say you want a list called
> > "Work mates, friends, and family")
> 
> The problem seems to be (by reading other bugs) that the quotes are not
> there in the recipient field.
> Like we had problems with user@host <user@host> type addresses.
> This one looks similar.

This is not the case. If you choose a list from the contacts pane (F9) then the description IS in quotes and the error still occurs.

> How is Work mates, friends (1 list) different from Work mates, friends (2
> lists) ?

The first is...
To: List1 <"Work mates, friends">

The second is...
To: List1 <"Work mates">
To: List2 <"friends">

> I think we keep the recipient as a plain string and then parse it into
> individual recipients.
> And the single line inputs (proposed rewrite of recipient are) will make it
> even worse.

I agree that you oughtn't to remove the ability to be able to type two addresses on the same line and they get split. The problem is that the list description is being parsed as if it is plain text entry when it already sits within chevrons and quotes. If you do type two LISTS on the same line separated by commas, they do get split into two addresses, but neither of them are valid because they aren't recognised as lists or valid addresses.

> 
> Outlook shows which characters belong to which recipient and highlights the
> individual recipients when clicked.

?

Comment 8

a year ago
(Sorry to enter a third comment in a row but...)

It is worth looking at the description and discussion on the duplicate bug (1216098). This clearly notes the problem and describes several test cases which show exactly the issues I am having.
Duplicate of this bug: 1267961

Updated

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