231282 - Opening RFC822 attachment into its window throws exceptions

Status: RESOLVED FIXED

(MailNews Core :: Backend, defect)

Description

[Mike Cowperthwaite]

When opening a message attached to another message into its own standalone 
message window, the following two exceptions are thrown:

Error: [Exception... "Component returned failure code: 0x80004003 
(NS_ERROR_INVALID_POINTER) [nsIMsgMailNewsUrl.mimeHeaders]"  nsresult: 
"0x80004003 (NS_ERROR_INVALID_POINTER)"  location: "JS frame :: chrome:
//messenger/content/mailWindowOverlay.js :: HandleMDNResponse :: line 2115"  
data: no]
Source File: chrome://messenger/content/mailWindowOverlay.js      Line: 2115

Error: [Exception... "Component returned failure code: 0x80004005 
(NS_ERROR_FAILURE) [nsIMsgMessageService.messageURIToMsgHdr]"  nsresult: 
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome:
//messenger/content/mailWindowOverlay.js :: HandleMDNResponse :: line 2114"  
data: no]
Source File: chrome://messenger/content/mailWindowOverlay.js     Line: 2114

Seen in:
  Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7a) Gecko/20040108

xref bug 204350

Comment 1

[Mike Cowperthwaite]

With TB 1.5b2-1006 and TB 1.6a1-1028, only the second of the errors 
originally reported occurs when the attachment is opened:

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMsgMessageService.messageURIToMsgHdr]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://messenger/content/mailWindowOverlay.js :: HandleMDNResponse :: line 2357"  data: no]
Source File: chrome://messenger/content/mailWindowOverlay.js
Line: 2357

Comment 2

[David :Bienvenu]

there's a fix for that in my tree, waiting for review

Comment 3

[Mike Cowperthwaite]

This has been fixed on the trunk in Thunderbird, with the most recent patch at bug 204350 (attachment 201005 [details] [diff] [review]), checked in yesterday.  David, is that patch Core?

Comment 4

[David :Bienvenu]

No, thunderbird only, but the same patch should work if it was ported to Seamonkey.

Comment 5

[Mike Cowperthwaite]

Marking this fixed; the problem described appears in Seamonkey 1.0a-0910, but not in SM 1.5a-1211.