276228 - Replying to msg w/ illegal Reply-To breaks addressing fields

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[Mike Cowperthwaite]

TB 1.0, Win2K

Certain illegal strings in a message's Reply-To field will cause the message to 
display with an empty Reply-To: in the envelope.  Replying to such a message 
breaks the compose window.

Steps to reproduce:
1) Get a message in a mail folder that has a header like:
  Reply-to:  <[e-mail]
2) View the message
3) Reply to the message
4) Close the compose window
5) Reply to the message *again*

Actual results:
2) envelope shows empty    Reply-to:
3) compose window has an empty To: field, which can be edited -- but no further 
address/header fields can be entered.  No additional fields are even drawn.
5) the (reopened, cached) compose window has an empty, disabled To: field *and* 
a disabled Subject: field.

After steps (3) and (5) JavaScript console shows:

Error: [Exception... "Component returned failure code: 0x80004003 
(NS_ERROR_INVALID_POINTER) [nsIMsgCompFields.SplitRecipients]"  nsresult: 
"0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome://
messenger/content/messengercompose/addressingWidgetOverlay.js :: 
CompFields2Recipients :: line 216"  data: no]
Source File: chrome://messenger/content/messengercompose/
addressingWidgetOverlay.js
Line: 216


This same problem was reported for Mozilla (xref bug 208577) but no longer 
manifests there.

Comment 1

[Mike Cowperthwaite]

See also bug 229880, bug 280782.

Comment 2

[Mike Cowperthwaite]

This is working quite acceptably for me with TB 1.5b1-0904.  The To header field 
is shown, and is not disabled or otherwise broken, but is left empty, which is 
sufficient.  Note that the Reply-to is also shown, blank, in the message 
envelope panel.