** Observed with 2/2/2001 trunk build ** 1. Send yourself a msg with a MS Word document attached -- a file with .doc extension. 2. Receive it in Mail. Click on the attachment/paper clip icon and choose 'open it' option. (This assumes that you have MS Word.) 3. It tries to open the file but I get an error msg saying that: MS Word cannot open the specified file format -- this feature is not currently installed. Do you want to install it? But when I do essentially the same thing with Communicator 4.x, MS Word opens the document without any complaint.

Are you sending the message from WinNT and get it back on WinNT?

The message seemed to have been sent from WinNT4-en using Communicator 4.76. I viewed it under WinNT4-J with today's Mozilla build.

I see this too. marking nsbeta1+ and moving to mozilla0.8 This needs to be fixed for mozilla0.8

Ignore my comment about seeing this bug. I saw a different bug than this where the attachment icon brings up an empty popup. I'm removing all of the nominations and nsbeta1+. Let's reproduce this first.

I cannot open the attachment because the attachment popop menu doesn't show up (see bug 67435). How do you do that if you are using a build from today?

You're right. I had some difficulty but one way I got around it was by choosing an item from the Character Coding menu. This reloads a msg display and somewhow after that, when I click on the icon, I am able to bring up the attached file.

If instead of opening it, you save it on the disk and then open it with MSWord. Will it works?

accepting

It works fine for me. Can you send a test message with the word document that cause problem. Thanks

J-F, it does work when saving a file first and then open it with MS Word directly. I just discovered something interesting. I was using WinNT4-Japanese when I discoverd this problem with Office 2000 (Word). I have the same Office 2000 installed on WinNT4-US and on that platform, the file opens without a complaint. I should look into this a bit more before you spend any more time on it. I'll update the bug.

It looks like when I removed all of the nsbeta1 stuff that it got put back. If we can reproduce this and it looks like a common case, then let's renominate.

The same bug seems to apear on todays linux build. Pressing the attachment icon will not work.. the bar that shows activity at the bottum does not stop either... not sure if this is related.

I can confirm this bug on Mac/2001071903. Specifically, when the message is sent from Mozilla Mail, the Word file is typed as application/octet-stream. Subsequent attempts to retrieve the attachment (either by opening it directly to Word or saving it to disk first) resulted in one of two things happening to me: (1) the resulting file was not recognized by Word and an "Open as..."-type dialog presented, or (2) an error dialog was shown stating that, "The current command did not succeed. The mail server responded, Invalid body part." I sent a test message with the same Word file attached from Outlook Express. OE correctly typed the attachment as application/msword. MozMail was correctly able to decode and save the file, and Word was able to open it. Curiously, OE is able to open the first message sent from MozMail, and can produce a file Word is able to open.

*** Bug 85205 has been marked as a duplicate of this bug. ***

looks like a problem with the external helper! We seems to lost the content type...

This behaviour is not specific to Word. I have seen the behaviour under 0.9.5 with Excel files also. Curiously, it doesn't happen all the time. For instance, I have had the following scenario: 1. I received a Word attachment to an email 2. I double click on the attachment and it opens fine in Word 3. I keep working in Mozilla for a while 4. I try to open another attachment and get the infamous 27 byte unopenable file error 5. Perplexed I go back to my original attachment and try to open it again and get the same error. Hope this helps someone...

marking nsbeta1+ for investigation, but I'm wondering if this could be related to 110067

I am still not able to reproduce this problem on My WinNT4. Can somebody attach to this bug report or send me by email a word document with which you have the problem.

I am not able to reproduce this problem. WFM

verified wfm. unable to duplicate the problem