169493 - incorrect parsing of (non-RFCx822) list of mail addresses

Status: RESOLVED WONTFIX

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Kuno Meyer]

(Moz 1.1final)

Today I received a message with the following recipent list (2 Contacts):
"To: Kuno Meyer <[e-mail]>;[e-mail]"

Here is, what Mozilla recognizes and displays in the message pane of the
mailnews window (1 Contact):
"Kuno Meyer ;[e-mail] <[e-mail]>"

Comment 1

[Mike Cowperthwaite]

Reporter, copying your symptom to the duplicate.

*** This bug has been marked as a duplicate of 110605 ***

Comment 2

[Kari Hurtta]

Grammar is:

address         =       mailbox / group

mailbox         =       name-addr / addr-spec

name-addr       =       [display-name] angle-addr

angle-addr      =       [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr

group           =       display-name ":" [mailbox-list / CFWS] ";"
                        [CFWS]

display-name    =       phrase

mailbox-list    =       (mailbox *("," mailbox)) / obs-mbox-list

address-list    =       (address *("," address)) / obs-addr-list


So to make 
     To: Kuno Meyer <[e-mail]>;[e-mail]

correct also ',' need to be added. That is:

To: Something: Kuno Meyer <[e-mail]>;,[e-mail]


';' is not address list separator. It is group terminator.
Space are not significant on syntax.


In other words there is ';' tried  to use as address separator
when ',' is address separator.

Alternatively to make     
   To: Kuno Meyer <[e-mail]>;[e-mail]
legal is change it
   To: Kuno Meyer <[e-mail]>,[e-mail]

bug 110605 is about rfc 2822 group syntax. There is not really
group syntax used, so I do not think that this is duplicate
(actually I think that this should be invalid -- if header 
 is garbage, it is reasonable that result of parsing is garbage.)


Microsoft uses on it's user interfaxe ';' as address separator, but 
it (;) does not used for that on internat mail sytntax (rfc 2822).

Comment 3

[Mike Cowperthwaite]

Kari Hurtta: you are quite right, this is a different problem.  Reopening.

However, I disagree on the last point; I think Mozilla should be able to parse 
this out a little more cleanly, even tho it's non-spec.

Comment 4

[Mike Cowperthwaite]

And confirming: reproduced with
  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a2) Gecko/20040610

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 6

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420