122352 - E-mail address incorrectly modified when replying

Status: RESOLVED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[Boris 'pi' Piwinger]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120

Bug might be OS independend.

Start with a message with a From: line of the form
From: First Last <login @ host>
(Note the white space in the address). Reply, you get something like
To: First Last <""login \"@ host>
The latter address does not work.

My apologies if this bug is already on the list, I had no idea how to find it.

pi

Comment 1

[Stewart Campbell]

Dont see it on WinME, latest nightly.

Comment 2

[Boris 'pi' Piwinger]

This bug is still around in 2002040812. RfC 822 uses space around @ all the
time. Now RfC 2822 says it SHOULD NOT be used, but Mozilla should for reasons of
compatability be able to deal with it.

pi

Comment 3

[Joachim Thewes]

Bug is still there.
Mozilla/5.0 (Windows; U; Win98; de-AT; rv:1.0rc2) Gecko/20020427

Comment 4

[Jean-Francois Ducarroz]

I am doing a lot of work related to encoding/decoding email address in bug
134277. Maybe that would take care of this problem, at least make the address valid.

Comment 5

[Boris 'pi' Piwinger]

Actually this other bug did not help.

pi

Comment 6

[Boris 'pi' Piwinger]

*** Bug 166352 has been marked as a duplicate of this bug. ***

Comment 7

[Boris 'pi' Piwinger]

Marking OS=All by comment 3. We missed the target milestone. Is the a hope for 1.2b?

pi

Comment 8

[Geoff Duddridge]

I am finding that the inclusion of (xxx) in a name eg ian(home) adds "   " in
the address. OS W95. Moz 1.7.3 It also does not like xxx_yyy in the address.
Compiling an address list of:-  To 1 + 20Bcc stalls the operation of the address
transfer to the composed email. Altering the preferred type of mail ie HTML/
Normal text seems sometimes to prevent stray //s being added to the composed
address list. Really messes up email operation.

Geoff Duddridge

Comment 9

[Wayne Mery (:wsmwk)]

still see this problem?

Comment 10

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.

Comment 11

[Boris 'pi' Piwinger]

I don't use SeaMonkey for Mail anymore, but this bug is straigtforward to check. No need to close it without this test.

pi

Comment 12

[Joshua Cranmer [:jcranmer]]

RESO INCO due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.

Comment 13

[Phil Ringnalda (:philor)]

Sigh. He even stood up on his hind legs and said "oh, come on, you can test it yourself, it doesn't require the reporter for that."

Comment 14

[David]

SeaMonkey (1.1.13) mail composition bug.
I think this bug in SeaMonkey is common to bugs 264626, 79455, 122352, 462589, 279846, 394216 that I have found. 
The mail in Netscape 7.2 works as expected. 
In a SeaMonkey mail program with multiple accounts, quite often the wrong account and "From" address is used when a message is replied to or forwarded on. 
For example:
An email is recieved in account1's inbox.
It is moved to account2's inbox
It is selected and replied to (or forwarded).
Netscape correctly uses account2's "compose in html" setting and the reply-to address. 
SeaMonkey incorrectly uses account1's settings and uses account1's reply-to address. The "from address" can be over-ridden with the pull down box, but the incorrect formatting etc is used when the reply (or forwarded) 
message is initially generated. 
Selecting a new composition from each account works correctly.
I think that the account settings, from address and formatting etc used when the reply or forwarded message is created, should be from the account where the initial message is currently stored (inbox, draft, template, sent etc), not some obscure address in the header.

Comment 15

[David]

Surely the idea of multiple accounts is that an account is setup for each 
email identity that the user has, ie Home, work, charity etc. 
Then it make sense to keep the mail relating to that identity in folders 
in the relevant account, ie any work related emails would be kept in the 
work\inbox, or work\sent etc. 
Emails could get there by either downloading from different pop servers, 
or by dragging from another account if all incoming mails are consolidated to one server.

Composing a new message when a certain account is highlighted works correctly, 
ie the correct formatting is selected (text/html) and the correct from address 
is selected. 

When it comes to replying or forwarding a message that is highlighted, 
it should work the same way, BUT IT DOESNT !!

Please correct me if I am wrong, but I believe the solution is blatantly obvious and very simple:
1 Ignore the X-Account-Key, or add an option to ignore the X-Account-Key
2 When replying to a message, or forwarding a message, use the same subroutine that creates a new message. 
   That correctly Opens a new edit window
   Uses the correct formatting 
   Uses the correct signature, CC and Bcc addresses
   Uses the correct From address 

To cater for different setups/users then it would be sensible to have some options 
that the user could select in their preferences.

Comment 16

[Eyal Rozenberg]

I've just tested this with the version of Seamonkey available for download from the website: version 2.49.4, 64-bit, Linux, GTK 3.0 .

I copied a mail message into a new mbox file, and edited it manually to introduce spaces around the @ (being careful the no-spaces address doesn't appear elsewhere). I then opened Seamonkey, viewed the message and replied. The bug does not manifest. The spaces get "disappeared" - both in message display and in the reply you see "First Last <login@host>" even though the mbox file has "First Last <login @ host>".

So, WORKSFORME. Feel free to reopen if it still manifests for you with a recent version.