What Does Invalid Mime Type Mean
7 years ago The issue I am encountering is basically the same as that previously reported as. Basically, once I open a file of type pdf that was sent by a user of the Mail program of OS X 10.7, Thunderbird picks up the mime type of application/applefile for all pdf files.
What Does Invalid Mime Content Mean
Any emails I send with pdf attachments then have the content-type given as application/applefile, but are missing the required metadata for that content type. Result is some receivers of my email (confirmed are those using outlook web access and the OS X Mail program) cannot open the pdf attachment ('file is corrupted' errors). Steps to reproduce: 1) Send an email with a pdf attachment from the OS X mail program, making sure it includes the applefile metadata (default as far as I can tell on OS X 10.7 Mail program) 2) Open email in thunderbird (OS X or Windows; did not check Linux) and save attachment to disk.
Feb 02, 2012 Chat with fellow EECMS users in the 'Invalid MIME type when uploading' ExpressionEngine community discussion forum thread. We use cookies to help make our site work properly and to analyze how our site is used.
Thunderbird picks up the application/applefile mime type for pdf files. 3) Send an email from thunderbird with a pdf attachment. It will have mime type application/applefile. 4) The pdf in this new email is not readable by some clients (one version of OWA and OS X Mail confirmed). Expected result: Thunderbird should always send PDF files as type application/pdf, or at the very least not be using a MIME type without ensuring the appropriate parts are present.
Severity: With the rise of OS X and iOS based clients, this is becoming more prevalent. Further, Thunderbird should not be sending emails with improper MIME types. 5 years ago (In reply to rsx11m from ) > (In reply to Kent James (:rkent) from ) > > 2) not using bad content types that already exist in mimeTypes.rdf in > > outgoing emails. > I'm wondering how one would identify 'bad content types' stored in > mimeTypes.rdf compared to 'valid' ones. What would be the suggested > procedure when a definition contradicting the OS-registered MIME type or > multiple definitions within the mimeTypes.rdf exist, thus causing an ambiguity?
I think there is no need to identify 'bad content types'. I think 'respect setting in OS, already known correct one by Tb(hard coded, or predefined) in generating mail data' is sufficient.
(i) Look content type defined in OS first (ii) if not found, look Tb's pre-defined ones (iii) if still not found, look mimeTypes.rdf defined by user intentionally or accidentally. If broken, for example,?windows-1252?, ignore it. In 'generating mail data', required 'relation' is only 'file extension -> mime-type' on Win and Linux(file meta data of the file is usable if Mac). Why data set by 'do it always or automatically' for 'registration of application name' should be used in mail composition? By this priority change, mimeTypes.rdf can not be used for 'overriding bad OS setting by mimeTypes.rdf of Tb'.