Closed Bug 94816 Opened 25 years ago Closed 24 years ago

RTF attachments show inline as code

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jbn, Assigned: sspitzer)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3) Gecko/20010801 BuildID: 2001080110 RTF (Microsoft Rich Text Format) document received as attachment to plain text message from POP3 server: document appears under message, inline, as code. Document will not open as a separate document using the application registered in the OS. (A test of receiving attachments in other formats registered to use the same application resulted in proper behavior; the external app opened the attachments. Won't work for .rtf.) Result occurred regardless of whether attachment had long or short file name. Reproducible: Always Steps to Reproduce: 1. Create RTF document and save to disk. 2. Using one identity, mail yourself a message and attach the RTF document. I used POP3, but I don't know if that's important. 3. Retrieve the message from your server. Actual Results: Message is received, and whether viewed in preview pane or opened in a new window: underneath a horizontal line the RTF code is displayed. Document cannot be opened with external application using the right-click/Open method that works for other attachment formats. Expected Results: Mozilla should have (1) not displayed the coding of the document, and (2) allowed the attachment to be opened with an associated application (or, if none, then give appropriate error message).
*** This bug has been marked as a duplicate of 94705 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verifying dupe
Status: RESOLVED → VERIFIED
jbn@nierenberg.com, could you do me a favor? view the source of the message with the rtf doc attached. Right before the rtf doc in the source there should be a header like: Content-Type: text/plain; name="mindrover.rtf" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mindrover.rtf" Or something along those lines. The part that I'm interested in is the "Content-Type" header. What does that say? reopening this bug pending answer. The bug it's marked a dup of was a Linux-specific problem.
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
Reporter, could you download a more recent build and try this again? If you're still seeing this problem, please let us know (within 15 days) what happens when you follow the above comment's procedure. Input from community members like yourself is vital to mozilla.org's capability to squish bugs :-) Thanks.
I tried two builds. I downloaded the 10/11 nightly build on October 12. It wouldn't open in my computer. I had to delete the directories. Then I reinstalled 0.9.4, the 2001091303 build. I can't tell you what would have happened with the nightly, but here's what happened with the milestone release: the rtf attachment was not initially downloaded with the message. Instead, Mozilla asked me whether to save it to disk or open it, just as it would when downloading the a zip file or an installer executable. Either way, downloaded or opened as is, the document displayed fine. And in the little attachment box was the correct display of an icon and the file name. So, the previous problem seems to have been fixed in a sense; it is not showing code. However, it seems odd that the attachment would not be downloaded with the message. If one rarely gets attachments, then not that big a deal, but if one gets them often, then it is not a feasible way to go.
Since the reported problem (rtf showed as code) is reported as working properly, closing this WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago24 years ago
Resolution: --- → WORKSFORME
QA Contact: esther → trix
works for me using 2002011403. Attached RTF document is not displayed, correct icon is displayed in attachment box, and able to display the document using proper display app.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.