Outgoing attachments have incorrect content types assigned to them

VERIFIED DUPLICATE of bug 43556

Status

defect
P3
normal
VERIFIED DUPLICATE of bug 43556
19 years ago
11 years ago

People

(Reporter: mscott, Assigned: mscott)

Tracking

Trunk
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta3+][nsbeta2-] Est. 7/15)

(Assignee)

Description

19 years ago
This is just a tracking bug for nsbeta2 purposes.

When we send a message with an attachment, we use the nsIMIMEService in the
networking module to give us the content type for the extension of the
attachment. This content type is bundled up in the ougoing message. When you
later receive and try to open the attachment. The client application uses that
content type to figure out how to open it.

Unfortunately the current mime service encapsulates just a list of hard coded
content types and file extensions. Anything not in this list, we end up giving
it an unknown content type when it is sent.

This prevents proper opening of the attachment by the client receiving the mail.

This problem will be fixed by Bug  #43556.  When the mime service is actually
implemented on top of the exthandler code I wrote this past week then it will be
dynamic and contain mime type information we get from both the user, the
operating system and our hard coded strings.
(Assignee)

Updated

19 years ago
Depends on: 43556

Updated

19 years ago
QA Contact: lchiang → pmock
(Assignee)

Comment 1

19 years ago
shame on me....how did I not nominate this for nsbeta2!
the good news is the parent bug is nsbeta2. No real work has to be done for this
bug. It should just work once 43556 is implemented but i want a separate bug to
track this issue. 
Keywords: nsbeta2
Target Milestone: --- → M17

Comment 2

19 years ago
Putting on [nsbeta2+] radar for beta2 fix. 
Whiteboard: [nsbeta2+]
(Assignee)

Comment 3

19 years ago
adding estimated completion date.
Whiteboard: [nsbeta2+] → [nsbeta2+] Est. 7/15
(Assignee)

Comment 4

19 years ago
as important as I think this is, given our new criteria of "would you pull the
beta off the wire for this", I don't think I would. According to the new
criteria established at the leads meeting today and from our mailnews beta2
triage meeting this afternoon, marking nsbeta2-.
Keywords: nsbeta3
Whiteboard: [nsbeta2+] Est. 7/15 → [nsbeta2-] Est. 7/15
Target Milestone: M17 → M18

Updated

19 years ago
Keywords: mail2

Comment 5

19 years ago
+ per mail triage.
Whiteboard: [nsbeta2-] Est. 7/15 → [nsbeta3+][nsbeta2-] Est. 7/15

Comment 6

19 years ago
Scott - I'm going to mark this a duplicate of 43556 because of your comments 
earlier in the bug.  If you disagree and this bug needs work to be done, please 
remove the duplication status.  

*** This bug has been marked as a duplicate of 43556 ***
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → DUPLICATE

Comment 7

19 years ago
verified duplicate
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.