422642 - Wrong content-type chosen for unknown extension

Status: RESOLVED DUPLICATE of bug 236212

(Thunderbird :: General, defect)

Description

[Dmitry Monakhov]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: version 2.0.0.12 (20080226)

I attach binary file with unknown file extension (.esw) expecting to get application/octet-stream content type.
However the actual content type is  text/plain. The situation is reproduced on Linux and Windows XP platforms with the same file attached. I can provide the file for testing.

Reproducible: Always

Steps to Reproduce:
1. compose new message
2. attach the file (let say 1.esw)
3. send the message
4. see the source of message you sent in the "Sent" folder

Actual Results:  
Content-Type: text/plain;
 name="1.esw"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
 filename="1.esw"

Expected Results:  
Content-Type: application/octet-stream;
 name="1.esw"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="1.esw"

The problem can be fixed by hacking  mimeTypes.rdf file.
I had to add the entry for *.esw file  like the following
------------------------------------------------------------------
 <RDF:Description RDF:about="urn:mimetype:application/eswtype"
                   NC:value="application/eswtype"
                   NC:editable="true"
                   NC:fileExtensions="esw"
                   NC:description="">
  </RDF:Description>

Comment 1

[Dmitry Monakhov]

Attachment: attach it and get the plain-text attachment

If you send the message with the file attached you will get wrong content type.

Comment 2

[Steve Simms]

Same issue as bug 236212?

There are a number of semi-overlapping MIME/content-type bugs, based on a couple of searches.

Comment 3

[Ludovic Hirlimann [:Usul]]

(In reply to comment #2)
> Same issue as bug 236212?
> 
> There are a number of semi-overlapping MIME/content-type bugs, based on a
> couple of searches.

Thanks steve.