[KLUG Members] mozilla

[Adam Williams]

>>>I have a problem concerning mail forwarding. When a mail containing a 
>>>attachment is being forwarded to me, the forwarded mail is handled as a 
>>>attachment. A "part 1.2" is displayed in the attachments window. Opening 
>>>this attachment does not encode the attachment:
>>>--------------14EE655159F8498EFEBF02E2
>>>Content-Type: application/msword;
>>>name="BI-keuze.doc"
>>>Content-Transfer-Encoding: base64
>>>Content-Disposition: inline;
>>>filename="BI-keuze.doc"
>>>0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAKAAAAAAA
>>>AAAAEAAAKgAAAAEAAAD+////AAAAACcAAAD/////////////////////////////////////
>>>////////////////////////////////////////////////////////////////////////
>>>////////////////////////////////////////////////////////////////////////
>>>////////////////////////////////////////////////////////////////////////
>>>////////////////////////////////////////////////////////////////////////
>>>The mail is being forwarded by Netscape 4.5 running on windows and I am 
>>>using Mozilla 0.91 running on SuSE 7.1
>>>Worst of all is that outlook (sorry for my French) is reading the mail 
>>>correctly. It shows a attached mail containing a attachment both can be 
>>>opened and read.
>>>Is this a bug or a feature?
>>More or less this is exactly the correct result.  Content disposition is
>>"inline",  but Mozilla can't do much with an "application/msword"
>>document.  In evolution I can
>>view-inline/save-to-disk/open-with-a-helper-app  from a context menu, 
>>I'd assume you can do much the same thing in Mozilla mail.  Basically
>>what you have is a Windows specific mail message.hink 
>but I don't want Mozilla to handle the attachment. Finally I want to 
>detach the "BI-keuze.doc" and open it with startoffice. I don't think 
>Mozilla should care about the attachment type. It just should decode the 
>attached message the right way and offer me a chooise of what I want to 
>do with it.
>Or am I seeing this wrong?

Well, some one said "Content-Disposition: inline;",  probably the
original sender using Outlook.  The mail client is (IMHO) doing the
right thing,  that is, doing what it has been told to do.  It is not up
to the mail client to determine the "correct" outcome of an action. 

A second more remote possibility is that the attachment header has
gotten hosed (I don't see a --begin-- line) and mozilla thus can't
determine enough about the mail message.  I occasionally (once a month)
get one of these.  I simply save the source of the message and use
uudeview to reconstruct the message parts.  I've seen this happen on
every mail client I've ever met, but I've never met a message uudeview
couldn't put back together again. (I bet Mr. Humpty Dumpty had wished
he'd had a copy).  In the case of scrambled messages it seems Lotus
software is the largest offender.