Steps to reproduce: 1. Make sure "Preferences|Mail & Newsgroups|Composition|Forward Message: As Attachment" is selected. 2. Forward an email to your account. 3. Receive the mail. This mail includes the forwarded email as an attachment. 4. Open the attachment by double-click or via the context-menu. Result: A Mail/News window without any content and headers appears. Expected Result: A Mail/News window with the forwarded message is displayed. I tested this with build 2003042412 on Windows XP and with a CVS build from today on Debian Linux. Clean install, fresh profile.

Confirming with Moz 20030424

It's a regression between April 21th-24th. It looks that guilty is bug 159995 or bug 186081.

note, this does not occur with IMAP Accounts.

Please ignore comment #3. This was the result of a misunderstanding on IRC. This is broken since the new behaviour for opening attached mails was checked in on april 14th (see Bug 143565). Before the checkin the attached message was shown in a browser window, now it results in the empty Mail/News-window. The fix for Bug 143565 seems to work fine for IMAP accounts only. :-( I´m CCing Neil and Antonio to this bug because of their involvement in Bug 143565. Maybe this should block Mozilla 1.4b because the fix for Bug 143565 is one of the major new features for this next release and should work for all kinds of accounts.

yeah, I don't like the sound of this regression. mark it as blocking.

working on it, from the console: ###!!! ASSERTION: unknown error, but don't alert user.: 'errorID != UNKNOWN_ERRO R', file c:/trees/trunk/mozilla/mailnews/base/util/nsMsgProtocol.cpp, line 401 JavaScript error: chrome://messenger/content/commandglue.js line 1: redeclaration of const MSG_FOL DER_FLAG_TRASH WEBSHELL+ = 8 JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x8 0004003 (NS_ERROR_INVALID_POINTER) [nsIMsgFolder.getMsgDatabase]" nsresult: "0x 80004003 (NS_ERROR_INVALID_POINTER)" location: "JS frame :: chrome://messenger/ content/messageWindow.js :: CreateView :: line 354" data: no]

wowsa, in messageWindow.js, OnLoadMessageWindow() we think the folder uri is: XXX gCurrentFolderUri = mailbox:/C|/Documents and Settings/Administrator/Applica tion Data/Mozilla/Profiles/default/eou9vmeh.slt/Mail/mail.meer.net/Inbox (that isn't a folder URI!) for imap, we do it right: XXX gCurrentFolderUri = imap://sspitzer@nsmail-1/INBOX

oh, I bet the problem is get are doing folder.URL, instead of folder.URI for imap, the are the same (I think?), but for local folder, they aren't.

bingo. here comes a patch.

fixed. r/sr=bienvenu, a=sspitzer

still some work here. now it opens, but the opened message ends up having the same attachments as the original message.

Quick note: In comment 7, the JS error on <commandglue.js> is bug 195733. It happens in the current bug, but is not "caused" by it.

I'm going to spin this issue to a new bug. > now it opens, but the opened message ends up having the same attachments as the > original message.

spun new issue to bug #203570

v