Closed Bug 172760 Opened 22 years ago Closed 21 years ago

Interpretation of "*.bck" files incorrect.

Categories

(MailNews Core :: Attachments, defect)

Other
Other
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: nrt, Assigned: mscott)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 5.14; Mac_PowerPC) Build Identifier: I'm running Mozilla on a Compaq XP1000 workstation running Tru64 Unix 5.1a. In the mail program, I received an e-mail attachment that was a *.bck file (a VMS backup save set). Unfortunately, Mozilla interprets ".bck" as a text file and attempts to display it. When I try to save the attachment, so I can FTP it to a VMS system, the only save option is as a .TXT file, which has the effect of destroying the save set. When I transfer it to a VMS machine and reset its attributes, it is no longer readable. Need a way to override the deefault interpretation of of file extensions. Reproducible: Always Steps to Reproduce: 1. Create a VMS backup save set. 2.e-mail it to Mozilla 3.save it 4. transfer to VMS system and attempt to open. Actual Results: Unreadable save set. VMS recognized it, but found no content. Expected Results: Correct contents of save set. At the Mozilla level, what is needed is option to save mail attachments as straight binary, rather than being forced to text.
Reporter: Can you give us a example of such an E-Mail? You can save the e-mail (File|Save As|File) and attach it here. I think the failure is not at Mozillas side, because you can set the MIME-Type of the attachment and MIME-Type goes before the file-types the OS knows.
Component: File Handling → Attachments
Product: Browser → MailNews
-->MailNews Attachments
Assignee: law → mscott
QA Contact: sairuh → trix
When you mail it, what do you mail it with? What file type is it marked as in the mail message?
QA Contact: trix → yulian
Reporter: Whats with Comment 1 and Comment 3?
Addtional comment from original submitter: I am unable to provide an example, as I have no VMS system on the open internet. I think what happened is that the e-mail attachment came to me through a long series of relays, and the MIME type information was lost or overwritten somewhere along the way. What I'm suggesting is not to try to make Mozilla any smarter, but rather to give the user a chance to override the default file type in case Mozilla is fooled by unforseen circumstances.
QA Contact: yulian → stephend
Can we resolve this bug invalid then?
-->invalid
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Verified.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.