On Sun, 26 May 2002 10:25:33, [EMAIL PROTECTED] (Ben 
Bucksch) wrote:
> Jan Eri wrote:
> 
> >I have a problem when sending non-binary attachments like *.RTF and 
> >*.TXT from Mozilla Mail (currently RC3 for OS/2).
> 
> >2. Some recipients complain that the attachments shows up ONLY inline in the 
>message, not detachable as attachments. This happens when the message is received by 
>someone using  Eudora and some Lotus Notes versions. Eudora support claims this is 
>because something in Mozilla is defective.
> >
> Can you attach the MIME header of those attachment, both when sending f 
> rom OS/2 and Win32? I guess, the problem is that Mozilla sends them as 
> attachment type=inline.
> 
> I agree that Mozilla is too aggressive in attaching stuff as inline, and 
> that it maybe even should give the option to attach either as inline or 
> as attachment. I don't know why Mozilla likes to attach as inline - jwz 
> or rhp would know, but they're both gone :-(.
> 
> But I also think that Eudora is broken, if it doesn't allow its users to 
> save inline attachments to disk. I had this problem with Eudora 
> recipients myself, IIRC.
> 
> Ben

Thanks a lot for reminding me to compare the headers, I believe the 
problem is partly solved.

Here is the extract from the header from OS/2 Mozilla:

>Content-Type: text/plain;
> name="testfile.rtf"
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline;

and this is the corresponding header from Windows Mozilla:

>Content-Type: application/msword;
> name="testfile.rtf"
>Content-Transfer-Encoding: base64
>Content-Disposition: inline;

Even if I had already checked that the OS/2 version had 
Navigator->Helper app->application/rtf defined, I discovered that the 
application entry was blank, so I changed to "Save to disk". After 
that change the OS/2 header changed to

>Content-Type: application/rtf;
> name="testfile.rtf"
>Content-Transfer-Encoding: base64
>Content-Disposition: inline;

Is it a bug or a feature when Mozilla ignores the type due to 
non-defined application?

The "user_pref("mail.content_disposition_type", 1);" that Parish 
mentions is not in my prefs.js file. Have I missed an option 
somewhere, or can it only be inserted manually?

regards,
Jan
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jan Eri ~~ Protector AS ~~ Norway
Work: http://www.protector-group.no/
Priv: http://janeri.com/

Reply via email to