Extraneous quote marks added to address, all 'To:' addresses treated as single address

RESOLVED INCOMPLETE

Status

Thunderbird
Message Compose Window
--
major
RESOLVED INCOMPLETE
11 years ago
10 years ago

People

(Reporter: Jonathan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
User-Agent:       Opera/9.24 (Windows NT 5.1; U; en)
Build Identifier: version 3.0a1pre (2007120904)

In both the mail reading pane and the reply-to (compose) window, the mail address in the To: field has had extra " (quote) marks added.

This was for a mail sent to a group of people - the first email address in the 'To:' is the one that is messed up.

In the reading pane, I get just one extra one ".

eg:
someone"@ca.com; nobody@ca.com; thirdperson@ca.com

When I hit 'Reply-all', all the addresses are treated as a single address and I get:

To: originalSender@ca.com
Cc: "someone""@ca.com; nobody@ca.com; thirdperson@ca.com

When I view the message source, the quote mark is not present.  Somehow it seems the parsing of addresses has gone wrong.



Reproducible: Always

Steps to Reproduce:
1. Have someone send you a group email with a bunch of addresses in the 'To:' field.
2. Hit 'Reply-all' to the message.
3. Send the message.  Pretty soon you'll get a bounce for the now very badly malformed address in the Cc: field.
Actual Results:  
Bounce message from server telling you that "someone""@ca.com; nobody@ca.com; thirdperson@ca.com is not a valid username.

Expected Results:  
Addresses are correctly parsed one by one as seaprate address, without extraneous quotes inserted which cause the Reply-all feature to malform the reply addresses.

Comment 1

10 years ago
> someone"@ca.com; nobody@ca.com; thirdperson@ca.com

Is this exactly how they appear in the list? If yes, the semicolon is clearly wrong here, those have to be commas instead to separate individual addresses. What you see may be Thunderbird's attempt to escape that address in order to retain it as a single address, also supported by your statement later

> Bounce message from server telling you that "someone""@ca.com; nobody@ca.com;
> thirdperson@ca.com is not a valid username.

So, this is probably related to (or a duplicate of) bug 210521 and similar.

Comment 2

10 years ago
Jonathan, could you please respond to my comment #1 within two weeks?
Otherwise, this bug will be resolved as incomplete due to lack of information.
Whiteboard: closeme 2008-08-07

Comment 3

10 years ago
No feedback from reporter, closing. Please feel free to reopen this if you have further information to add.

-> INCOMPLETE
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE

Updated

10 years ago
Whiteboard: closeme 2008-08-07
You need to log in before you can comment on or make changes to this bug.