Talk:MIME

message: Copied below is the original section titled "Content-Disposition".  For some obscure reason, the discussion is all mixed up with filename parameters.  I am copying the original text here before I edit it in the main page. Reddyuday (talk) 16:25, 1 April 2010 (UTC)
thread_title:  Content-Disposition section 

message: ... and needs to be added. When have the specifications been published first? How have they been adopted? How and when have they changed? etc .. --L.Willms (talk) 19:11, 26 May 2010 (UTC)
thread_title:  History of MIME is missing

message: In fact such descriptive form should be provided and be required for a protocol specifications!
The existing "definitive" RFC documents are time consumingly verbose and vague and filled with antequated references and justifications useful to historians.
X21J (talk) 16:59, 19 September 2011 (UTC)
thread_title:  ABNF (Augmented Backus-Naur Form) definition required 

message: The section title is misleading since the text actually does not say what the difference is.  — Preceding unsigned comment added by 92.224.158.223 (talk) 19:14, 24 March 2013 (UTC)
thread_title:  Difference between Q-Encoding and quoted printable 

message: * In the complete list of Internet media types maintained by IANA here:  http://www.iana.org/assignments/media-types/media-types.xhtml it states that MIME and Internet Media Types refer to the same thing:  
* Having the two terms separated as separate articles results in confusion as illustrated by this discussion on StackOverflow..
* Also suggest merge of Mailcap, due to reason 3 of WP:MERGEREASON and since the vast majority of the articles content is in regard to mime types.
David Condrey  log talk  02:07, 12 July 2015 (UTC)
thread_title:  Suggest merging this article together with [[Internet_media_type]] 

message: Since the switch from Geshi to Pygments for syntax highlighting (phab:T85794), support for 'email' was unfortunately dropped, as can be seen with the plain text formatting on this page and other pages such as Internet Message Access Protocol, DomainKeys Identified Mail, Abuse Reporting Format, Email authentication, Mbox and Simple Mail Transfer Protocol and IEFBR14. If we want 'email' syntax highlight support again, it will need to be added to Pygments.
Also, 'lang=http' appears to not activate unless the first line matches the beginning of a http message.  This page has one case where <source lang="http"> is used with MIME-Version: 1.0 appearing first, and the syntax highlighter ignores it.  Adding HTTP/1.0 200 OK as the first line would mean it highlights correctly.  See e.g.)
I havent been able to find any handler in Pygments which is a suitable fallback for 'email', however 'http' might be an alternative that works in some cases, but especially when 'email' was used for non-email source such as here. John Vandenberg (chat) 04:06, 13 July 2015 (UTC)
thread_title:  email syntax highlighting lost 

message: SMTP is OSI layer 7 (the application layer).  SMTP (RFC 5321) in turn delivers .eml (RFC 5322), which may then contain MIME content.  Since MIME is two levels deep within layer 7, it couldn't possibly be part of OSI layer 5 (the presentation layer).  (Compare with CSS, which often lives in HTML, which is usually delivered by HTTP, which is also layer 7.)  I propose removing all references to abstraction layers in the MIME article. Adam KatzΔ☎ 02:17, 10 March 2017 (UTC)
thread_title:  How is MIME on the presentation layer?