Closed
Bug 360497
Opened 18 years ago
Closed 18 years ago
Cannot reply to forwarded attachment e-mail, JS error
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 204350
People
(Reporter: abl, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061030 MultiZilla/1.8.2.0i SeaMonkey/1.0.6 Mnenhy/0.7.4.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061030 MultiZilla/1.8.2.0i SeaMonkey/1.0.6 Mnenhy/0.7.4.0
Similar to bug 329462, just different JS error :
Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMessenger.msgHdrFromURI]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://messenger/content/mailCommands.js :: ComposeMessage :: line 245" data: no]
Seamonkey 1.0.6, if i rememeber correctly, this happened with all SM versions so far.
Again, the steps to reproduce or expected results are the same as bug 329462, just different JS error message, and product - SeaMonkey instead of TB.
Reproducible: Always
Comment 1•18 years ago
|
||
Fixed for TB 2.0. You can use the 2a1 alpha-release build or a recent nightly, they're pretty stable.
ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/2.0a1
-- or --
ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-1.8
Also, to workaround: save the attached forward as a .EML file, open the .EML file with File|Open Saved Message and then reply/forward from there.
*** This bug has been marked as a duplicate of 204350 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•18 years ago
|
||
I do not use TB!
I use Seamonkey.
And, workaround does not works too.
Probably TB-only workaround.
Comment 3•18 years ago
|
||
(In reply to comment #2)
> I do not use TB!
> I use Seamonkey.
The fix is in both; SM 1.1 works as you want. If you look at the dupe, you'll see it's filed as Core: fixes there appear in both products.
> And, workaround does not works too.
> Probably TB-only workaround.
I don't think that's correct; but I'm not going to install a 1.0.x version of Seamonkey to find out.
You need to log in
before you can comment on or make changes to this bug.
Description
•