MIME - Revision history

Jsummers: PRONOM, added category

2017-03-03T19:01:22Z

PRONOM, added category

Dan Tobias at 00:58, 21 February 2017

2017-02-21T00:58:35Z

Dan Tobias: /* See also */

2017-02-21T00:56:44Z

‎See also

Jsummers at 21:31, 16 August 2015

2015-08-16T21:31:04Z

Jsummers: /* Format */

2014-08-24T23:13:39Z

‎Format

Dan Tobias at 05:12, 8 March 2014

2014-03-08T05:12:39Z

Dan Tobias at 05:11, 8 March 2014

2014-03-08T05:11:34Z

Dan Tobias at 16:07, 2 November 2013

2013-11-02T16:07:44Z

Jsummers at 15:38, 2 November 2013

2013-11-02T15:38:08Z

Jsummers: Created page with "{{FormatInfo |formattype=electronic |subcat=E-Mail, newsgroups, and forums }} == Overview == '''Multipurpose Internet Mail Extensions''' ('''MIME''') is an extension of [[Inte..."

2013-03-02T04:19:35Z

Created page with "{{FormatInfo |formattype=electronic |subcat=E-Mail, newsgroups, and forums }} == Overview == '''Multipurpose Internet Mail Extensions''' ('''MIME''') is an extension of [[Inte..."

New page

{{FormatInfo
|formattype=electronic
|subcat=E-Mail, newsgroups, and forums
}}
== Overview ==
'''Multipurpose Internet Mail Extensions''' ('''MIME''') is an extension of [[Internet e-mail message format]]. Among other things, it defines a standard way to attach files to an email message.

== Format ==
A MIME-compliant message is identified by the presence of a "MIME-Version" message header. The other headers used by MIME begin with "Content-".

== See also ==
* [[Mime-type]]

== Specifications ==
* RFC 2045: MIME Part One: Format of Internet Message Bodies
* RFC 2046: MIME Part Two: Media types
* RFC 2047: MIME Part Three: Message Header Extensions for Non-ASCII Text
* RFC 2049: MIME Part Five: Conformance Criteria and Examples
* RFC 2183: The Content-Disposition Header Field
* RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
* RFC 2387: The MIME Multipart/Related Content-type
* RFC 3676: The Text/Plain Format and DelSp Parameters
* RFC 3798: Message Disposition Notification
* RFC 4289: MIME Part Four: Registration Procedures
* RFC 5147: URI Fragment Identifiers for the text/plain Media Type
* RFC 6532: Internationalized Email Headers
* RFC 6533: Internationalized Delivery Status and Disposition Notifications
* RFC 6838: Media Type Specifications and Registration Procedures

@@ Line 3: / Line 3: @@
 |subcat=E-Mail, newsgroups, and forums
 |extensions={{ext|mime}}
 }}
 '''MIME''' (Multipurpose Internet Mail Extensions) is an extension of [[Internet e-mail message format]]. Among other things, it defines a standard way to attach files to an email message.
@@ Line 36: / Line 37: @@
 * http://libxad.cvs.sourceforge.net/viewvc/libxad/testfiles/ASCII/mime/ → *.mime
 [[Category:Web]]

@@ Line 6: / Line 6: @@
 '''MIME''' (Multipurpose Internet Mail Extensions) is an extension of [[Internet e-mail message format]]. Among other things, it defines a standard way to attach files to an email message.
-The file type identification system used by MIME, [[Mime-type]], is also used by a number of other formats and protocols, such as [[HTTP]].
+The file type identification system used by MIME, [[MIME types]], is also used by a number of other formats and protocols, such as [[HTTP]].
 == Format ==

@@ Line 14: / Line 14: @@
 == See also ==
-* [[Mime-type]]
+* [[MIME types]]
 * [[Multipart/Form-Data]]

@@ Line 4: / Line 4: @@
 |extensions={{ext|mime}}
 }}
-'''MIME''' (Multipurpose Internet Mail Extensions) is an extension of [[Internet e-mail message format]]. Among other things, it defines a standard way to attach files to an email message. It is also used in the [[HTTP]] protocol to identify media types on the Web.
+'''MIME''' (Multipurpose Internet Mail Extensions) is an extension of [[Internet e-mail message format]]. Among other things, it defines a standard way to attach files to an email message.
 == Format ==
@@ Line 13: / Line 15: @@
 == See also ==
 * [[Mime-type]]
 == Specifications ==

@@ Line 7: / Line 7: @@
 == Format ==
-A MIME-compliant message is identified by the presence of a "MIME-Version" message header. The other headers used by MIME begin with "Content-".
+A MIME-compliant message is identified by the presence of a "MIME-Version" message header. The other headers used by MIME begin with "Content-". (This applies to the top level of an e-mail message. If MIME content is embedded in another format such as [[S/MIME]], it may not require a MIME-Version header.)
 Since MIME data is usually found as part of a message (as stored or transmitted by various means) rather than as a standalone file, it usually doesn't have a file extension. MIME headers or MIME-encoded messages saved for archiving or as example files might sometimes have a .mime extension.

← Older revision		Revision as of 05:12, 8 March 2014
Line 32:		Line 32:
	== Sample files ==		== Sample files ==
	* http://libxad.cvs.sourceforge.net/viewvc/libxad/testfiles/ASCII/mime/ → *.mime		* http://libxad.cvs.sourceforge.net/viewvc/libxad/testfiles/ASCII/mime/ → *.mime
		+
		+	[[Category:Web]]

@@ Line 3: / Line 3: @@
 |subcat=E-Mail, newsgroups, and forums
 }}
 '''Multipurpose Internet Mail Extensions''' ('''MIME''') is an extension of [[Internet e-mail message format]]. Among other things, it defines a standard way to attach files to an email message.
@@ Line 27: / Line 26: @@
 * RFC 6533: Internationalized Delivery Status and Disposition Notifications
 * RFC 6838: Media Type Specifications and Registration Procedures