Closed Bug 186357 Opened 22 years ago Closed 21 years ago

Mail doesn't open MS Word attachments

Categories

(MailNews Core :: Attachments, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: sai_allavarpu, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20021220
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20021220

When I receive a MS Word doc as an attachment, I click on the attachment.
Instead of opening it Word, I get a 'file save as' dialogue. The MIME types are
right application/msword. I tried attachment filenames with and without spaces
in them. Yet it doesn't work.

Reproducible: Always

Steps to Reproduce:
1.Send yourselves a MS Word doc as an attachment
2 [review].When you receive the sent mail, click on the word attachment
3 [review].

Actual Results:  
opens a 'file save as' dialogue

Expected Results:  
should open the word program to open the doc
More excerpt from the mail window (mail was sent and received using Mozilla 1.3 
(same version as the one used to file the original bug)

--------------060104070802030901020004
Content-Type: application/msword;
 name="Sai Allavarpu.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Sai Allavarpu.doc"
-----------------------------
Noted that there is a pref in pref.js getting set (something like 
helper.applications.neverAsk.saveToFile) that includes application/msword. When 
I manually remove that line, this problem doesn't happen. Don't know how that 
preference got set.
QA Contact: yulian → stephend
using 20031003 I wasn't able to reproduce
please try a more recent build
if the bug is still there please reopen this bug

make sure that you dont have msword documents set to "save to disk"
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Verified.  wfm.
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.