213051 - Sending a PKCS12 File as Attachment gets wrong Mime-Type

Status: RESOLVED EXPIRED

(MailNews Core :: Attachments, defect)

Description

[Olaf Gellert]

User-Agent:       Mozilla/5.0 (ogPS) Gecko/20100101
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4/mozilla-i686-pc-linux-gnu-1.4-sea.tar.gz

There is a typo at least in the configuration file "mimeTypes.rdf". Instead
of "application/pkcs12" there is "apllication/pkcs12". So if I send a
PKCS12 file as attachment it gets this wrong mime-type. So the attachment
is processed as beeing ASCII, the Transfer-Encoding will be "quoted-printable",
the attachment is broken when it reaches its destination (eg. carriage-returns
replaced and so on).

Reproducible: Always

Steps to Reproduce:
1. Generate PKCS12 File
2. Compose Email, attach PKCS12 file
3. Send it

Actual Results:  
See above

Expected Results:  
The MIME-Type should obviously be "application/pkcs12" without
the typo...

Comment 1

[Boris Zbarsky [:bzbarsky]]

> There is a typo at least in the configuration file "mimeTypes.rdf"

The default mimeTypes.rdf is empty.  If yours has data, it was either entered by
you or entered automatically when you chose how to handle a new, never before
seen, type.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.