189928 - Quotes in address not displayed in message header

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Boris 'pi' Piwinger]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030117

Look at a mail with some from line like this:
From: "Real Name <foo@bar>" <foo@bar>

This will be displayed as:
From: Real Name <foo@bar> <foo@bar>

This, of course, would not be correct. Looking at the source of the mail I found
it was a correct header and Mozilla fooled me.

Sorry, if this is the wrong component.

Bug 134277 might be related to this here.

pi

Comment 1

[Pascal Chevrel:pascalc]

related to bug 134277  ?

Comment 2

[Mike Cowperthwaite]

(Updating summary so search on "address quote" will find this one.)
xref bug 273884

Generally speaking, I'd prefer unescaped quotes were not displayed (and escaped 
quotes displayed without the escapes).  

Of course, they should be maintained when the string is actually being used as 
an address; and, at least in current builds, Reply or Compose Email To on this 
address actually creates the correct, quoted header, altho the compose window 
also does not show the quotes in the address fields.

Even if you type in an unquoted, unescaped string, the quotes are properly added 
in the header -- at least, for strings that are "well-formed" as far as matching 
opening- and closing-parentheses or angle-brackets

Comment 3

[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 4

[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 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

[Boris 'pi' Piwinger]

Still there with Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.21)
Gecko/20090403 SeaMonkey/1.1.16

Even worse, if you hit reply, then the bogus address shows up in the To field. When sent, the quotes are in the right place, though!

pi