LN,FN separated by comma in e-mail address results in splitting the name when Reply

VERIFIED FIXED in M12

Status

MailNews Core
Composition
P2
major
VERIFIED FIXED
19 years ago
10 years ago

People

(Reporter: esther, Assigned: Jean-Francois Ducarroz)

Tracking

Trunk
x86
Windows 98

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
Using 1999110109m11 build on win98, when I Reply to a message that has a
recipient with an e-mail address using LN,FN separated by a comma
(example:"Last, First" <First.Last@kla-tencor.com>) the name splits after the
comma when doing a Reply.  I have (2) people who e-mail me with this format and
they both use Outlook Express.  4.7 can handle the comma.  I still need to check
Mac and linux.

0. Have someone with an e-mail address that fits the example above send you a
message.
1. Launch Messenger
2. Select the account this message would be in
3. Select the message and Click Reply

Result: the name before the comma is on the first line, the rest of the name and
e-mail address are on the second line.

Expected: the full name of the recipient on the first line.
(Reporter)

Updated

19 years ago
QA Contact: lchiang → esther
Summary: LN,FN separated by comma in e-mail address results in splitting the name when Reply → LN,FN separated by comma in e-mail address results in splitting the name when Reply
(Reporter)

Updated

19 years ago
Priority: P3 → P2
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M12
(Assignee)

Comment 1

19 years ago
Right, we use comma as recipient separator. We should probably use someting else? or put the full email address
between double quotes in this particular case.

Comment 2

18 years ago
You should use the utility functions we already have to parse a buffer of
recipients into the properly separated email addresses. Whatever the modern-day
equivalent of MSG_ParseRFC822Addresses is (I bet rhp knows) That code knows
about double quotes and RFC822 special characters.
(Assignee)

Comment 4

18 years ago
Looks like it will be more complex than expected. The addresses are broken in
unique entity at the Front end level therefore from JS. As from JS we deal only
with unicode data, I cannot use directly the msgHeaderParser function. I will
need to add a new scriptable class to wrap a nsString array which will
be constructed by msgCompose using the parser
function.

I have also discovered that we have some problem during the send when we use
comma into any recipient's address.
(Assignee)

Comment 5

18 years ago
OK, I have a fix for that in my tree. Now we are supporting correctly any RFC822
recipients in a reply/reply all message. But we have now problem sending the
message with those specific formated (LN,FN) recipients. I am working on the
send issue now...

Updated

18 years ago
Blocks: 20203
(Assignee)

Updated

18 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
(Assignee)

Comment 6

18 years ago
Fixed and checked in. Review by jefft

Updated

18 years ago
Blocks: 20870
(Reporter)

Updated

18 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Comment 7

18 years ago
Using build 1999120808 on mac and linux and build 1999120716m12 on win98 this is
fixed.  Verified

Comment 8

18 years ago
This bug still appears to exist in the linux build 2000040315.  I sent a
message with the following headers:

From: "Stock, Steve (from)" <steve@technolope.org>
To: "Stock, Steve (to)" <sstock@iconnect-inc.com>
CC: "Lastname, Firstname" <someoneelse@iconnect-inc.com>
Subject: test message

When I hit "reply all" the compose window had the following addresses:
To: "Stock, Steve (from)" <steve@technolope.org>
Cc: Stock
Cc: Lastname
Cc: Firstname <someoneelse@iconnect-inc.com>

It appears that the From address is parsed correctly for the To field, but the
CC list is just wrong.  Other (real life :-) emails are also showing this behavior.

Let me know if you need more information.

Comment 9

18 years ago
sstock@iconnect-inc.com - pls open a new bug up for your case.  This bug report 
is pretty old so we don't want your comments to get lost.  Thanks!

Updated

18 years ago
No longer blocks: 20203

Updated

18 years ago
No longer blocks: 20870
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.