Closed
Bug 281078
Opened 20 years ago
Closed 17 years ago
Forwarding a mail with a word attachment puts attachment in message body
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: pturner, Assigned: mscott)
Details
(Whiteboard: closeme 2008-08-28)
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
When forwarding a mail with a word attachment the forwarded mail compose window
did not have the file attachement, but had the attachment in the body text (the
same as viewing the message source of the original email). I can replicate this
everytime with this email. Produced in version 0.9 and then upgraded to 1.0
with the same results.
Reproducible: Always
Steps to Reproduce:
1.Forward the selected mail with word attachment
2 [review].Message Composer has no file attachment, but inline like message source
3.
Actual Results:
Compose window did not have the file attachement, but had the attachment in the
body text (the same as viewing the message source of the original email).
Expected Results:
File attachment should remain as a file attachment when forwarded.
I can supply the original message as a saved eml file if required.
| Reporter | ||
Comment 1•20 years ago
|
||
This .eml fail is the saved original message that caused the problem when
forwarded.
| Reporter | ||
Updated•20 years ago
|
Version: unspecified → 1.0
Comment 2•20 years ago
|
||
I tested creating an email in Thunderbird (1.0.2, OS X 10.3.9) and emailing it
to another account of mine. This attachment is the recieved message.
The attachement is not accessible in this email, though it appears in the
message source with what look to be appropriate boundaries.
Comment 3•20 years ago
|
||
I tested creating an email in Thunderbird (1.0.2, OS X 10.3.9) and emailing it
to another account of mine. This attachment is the version of the email placed
in my "sent items" folder.
The attachement appears as text in the email. Note that neither a boundary
string, "--_NextPart_1_qmZrHLajoetbkwlTZTViemHPfyb", nor a Content-Type
declaration exist before the attachment data.
Similar tests with PNG image attachements work fine.
Comment 4•20 years ago
|
||
Sorry to bury this but it seems related. Tried to forward an email successfully
forwarded from non-Thunderbird client that I received. Thunderbird 1.0.2.0,
WinXP SP2 Home.
Original forwarded text .eml file was already an attachment, as was a .jpg file.
See added note: https://bugzilla.mozilla.org/show_bug.cgi?id=239909
All I got in the new document I tried to create using "forward" was the text
that the forwarder wrote in their message.
I have "show attachments inl-line" enabled.
Work-around: save attachments and attach them to a document created using "Write."
Steve
Comment 5•20 years ago
|
||
I too have been sending MSWord Docs and the recipient has a problem reading
them because the Thunderbird apparently retains the path to the document from
my computer. When the recipient tries to open the document, he gets an error
that it can't find the file at the path location that was on my computer
(which of course is not available on the recipient's computer). If the
recipient clicks on the ok button several times, the document finally opens at
the recipient's computer.
This is a troublesome error. Are there any solutions to this?
Updated•18 years ago
|
QA Contact: general
Comment 6•17 years ago
|
||
Reporter, does the issue still occur with the latest supported 2.0.0.x / Shredder trunk nightlies?
(1.5.0.x is now end-of-life and the latest supported Thunderbird version 2 is 2.0.0.16)
Whiteboard: closeme 2008-08-28
Comment 7•17 years ago
|
||
RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•