Closed Bug 484369 Opened 16 years ago Closed 16 years ago

PDF attachment get text/plain Content-Type

Categories

(Thunderbird :: General, defect)

x86
macOS
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: moz, Unassigned)

Details

(Whiteboard: dupme)

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.0.7) Gecko/2009021906 Firefox/3.0.7 Build Identifier: version 2.0.0.21 (20090302) When sending an email with a PDF document attached, the Content-Type is set to text/plain, while they should be application/pdf Reproducible: Always Steps to Reproduce: 1. Create new email 2. Attach PDF document (either through dragging, or via the menu) 3. Send. Actual Results: Content-Type: text/plain; name="document.pdf" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="document.pdf" Expected Results: Content-Type: application/pdf; name="document.pdf" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="document.pdf"
Whiteboard: dupme
That's similar or identical to bug 462126 (and likely others), you may have picked up a wrong content-type definition when opening an attachment with such a specification, then making it the default action by checking the box which is in the respective dialog. This associates the extension of that file name with the given content type and will be used for outgoing e-mail from that point on. Find the mimeTypes.rdf file in your profile folder (not the default copy in your installation folders), then rename it while Thunderbird is down. Restarting will create a new file from the default template, and the issue should be gone. You can use the new file if you don't have a significant number of definitions, or replace it with the old one and use the MIME Edit extension to remove the faulty entry. If the issue persists, please attach your mimeTypes.rdf file for inspection.
My apologies, it indeed appears that I inadvertently introduced this into my mimeTypes.rdf file. Removing the file resolved the issue.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.