Open Bug 531354 Opened 15 years ago Updated 6 months ago

.eml file opened from HDD, when forwarded a) inline: shows empty body; b) as attachment: "bad" link to attached .eml

Categories

(Thunderbird :: Message Compose Window, defect)

x86_64
Windows Vista
defect
Not set
major

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: kevin, Unassigned)

References

(Blocks 1 open bug, )

Details

(Keywords: testcase, Whiteboard: [related dataloss problem in comment 4])

Attachments

(1 file)

User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30618; InfoPath.2)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091121 Thunderbird/3.0

When forwarding an EML that is not located in Thunderbird, but just on your C drive, Thunderbird doesn't show the body when forwarding should be done inline. When forwarding should be done attached the link of the attached EML is incorrect, but that's probably a different problem because that's always reproducable with an e-mail located on your C drive with images included. Therefor see bug https://bugzilla.mozilla.org/show_bug.cgi?id=531263

Reproducible: Sometimes

Steps to Reproduce:
1. save the EML attached to this bug report to your C drive
2. open the EML with Thunderbird
3. Forward the EML inline
Actual Results:  
When forwarding inline:
Empty body.
When forwarding attached:
The attachment location is incorrect. (see other bug report)

Expected Results:  
When forwarding inline:
The body should be shown
When forwarding attached:
The EML location should be correct
Attached file testcase
Keywords: testcase
User-Agent: Thunderbird/5.0
general.useragent.locale: es-ES
System: Windows XP SP3

I get the same behaviour when fowarding saved emails (*.eml files in hard drive) in several installations with the sames OS version and program version. In error console (Tools->Error console), I get this message:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIMsgComposeService.initCompose]"  nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)"  location: "JS frame :: chrome://messenger/content/messengercompose/MsgComposeCommands.js :: ComposeStartup :: line 1570"  data: no]

I think it could help.
wfm (albeit with one error) on WinXP / TB12.0.1:

- open testcase.eml of attachment 414838 [details] with TB
- Ctrl+L to forward inline
-> full content of testcase.eml displayed inline, including header information

- Message > Forward > As attachment:
-> testcase.eml correctly attached to new mail
-> opening testcase.eml from attachment pane (before draft was saved or closed) correctly opens testcase.eml (not from the original location, because it is already copied to a temporary location - yes, und you can never guess for which type of file or method this will occur or not, that's Bug 378046).

When opening testcase.eml from attachment pane, i.e. from temporary location:
C:\Documents and Settings\USER\Local Settings\Temp\Test_KVA01.eml
I see this error:

Timestamp: 05.06.2012 12:56:59
Error: [Exception... "'<error>' when calling method: [nsIContentHandler::handleContent]"  nsresult: "0x805d0001 (<unknown>)"  location: "<unknown>"  data: no]
OT: 

Something which I find really worrying in terms of dataloss is this: 
- open multiple drafts with "forward [of test.eml on HD] as attachment"
-> they all point to the same temporary file, iow, temporary file is overwritten without notice, and editing that temporary file would edit it for all drafts, which is clearly wrong.

That's another bug, perhaps already recorded, but this will break badly if you start out with two test.eml files with different content which happen to have same file name (test.eml) but different locations on HDD or removable media, whichever of them is attached last will overwrite the previous one (dataloss, privacy) and will get sent for all respective messages. I thought we had fixed this, but apparently we haven't.
Kevin (reporter), Oscar (comment 2), or anyone with 64bit Win Vista, do you still see problems doing the following with testcase.eml of attachment 414838 [details]?
- open testcase.eml
- forward as inline
- foward as attachment
Summary: When forwarding an EML shows an empty body or bad link to the EML attached → .eml file opened from HDD, when forwarded a) inline: shows empty body; b) as attachment: "bad" link to attached .eml
Whiteboard: [related dataloss problem in comment 4]
Sorry, but we only have Windows XP 32 bits in the office. We do not use Vista or Seven, so we cannot test it.
Attachment #414838 - Attachment description: testcase → testcase
Attachment #414838 - Attachment mime type: message/rfc822 → text/plain
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: