The example above shows a notation named " type-image-svg " that references the standard public FPI and the system identifier ( the standard URI ) of an SVG 1. 1 document, instead of specifying just a system identifier as in the first example ( which was a relative URI interpreted locally as a MIME type ).

Multipurpose Internet Mail Extensions ( MIME ) is an Internet standard that extends the format of email to support:

According to MIME co-creator Nathaniel Borenstein, the intention was to allow MIME to change, to advance to version 2. 0 and so forth, but this decision led to the opposite outcome, making it nearly impossible to create a new version of the standard.

New versions of PGP applications use both OpenPGP and the S / MIME, allowing communications with any user of a NIST specified standard.

Another important standard supported by most email clients is MIME, which is used to send binary file email attachments.

Thunderbird supports the S / MIME standard, extensions such as Enigmail and support for the OpenPGP standard.

MIME, the modern standard of E-mail format, forbids encoding of headers using byte values above the ASCII range.

Although MIME allows encoding the message body in various character sets ( broader than ASCII ), the underlying transmission infrastructure ( SMTP, the main E-mail transfer standard ) is still not guaranteed to be 8-bit clean.

* Ned Freed, co-author of the MIME email standard ( RFCs 2045-2049 )

This led to the development of the protocol MIME Object Security Services ( MOSS ; never widely implemented, now abandoned ) and S / MIME ( shares de facto standard status with PGP ).

S / MIME ( Secure / Multipurpose Internet Mail Extensions ) is a standard for public key encryption and signing of MIME data.

The original specification used the IETF MIME specification with the de facto industry standard PKCS # 7 secure message format.

* How to secure email using S / MIME standard

Popular electronic signature standards include the OpenPGP standard supported by PGP and GnuPG, and some of the S / MIME IETF standards.

Modern email systems use the MIME standard, making email attachments more utilitarian and seamless.

This was developed by Nathaniel Borenstein and collaborator Ned Freed with the first MIME email attachment being sent by Nathaniel Borenstein on March 11, 1992 and the standard being officially released as RFC2045 in 1996.

Selecting RTF as the format for sending an e-mail implicitly enables TNEF encoding, using it in preference to the more common and widely compatible MIME standard.

For xCBL message transport, Commerce One created an envelope messaging standard called MML ( Marketsite Messaging Layer ) based on the SMTP MIME format to provide both payload ( xCBL ) and attachment support.

The electronic envelope technique involves encrypting the message directly using a secure encryption standard such as OpenPGP ( Public key infrastructure ), S / MIME.

MIME defines mechanisms for sending other kinds of information in email.

MIME defines a collection of email headers for specifying additional attributes of a message including content type, and defines a set of transfer encodings which can be used to represent 8-bit binary data using characters from the 7-bit ASCII character set.

It defines the MIME type " text / csv ", and CSV files that follow its rules should be very widely portable.

IETF RFC 4180 ( summarized above ) defines the format for the " text / csv " MIME type registered with the IANA.

* MIME supplements the e-mail formatting rules to allow non-English text in both e-mail headers and bodies, and defines a mechanism for including non-textual attachments in e-mail bodies

MIME defines mechanisms for sending other kinds of information in e-mail, including text in languages other than English, using character encodings other than ASCII.

* MIME Media Types-comprising a list of directories of content types and subtypes, maintained by Internet Assigned Numbers Authority.

** either by additional attributes ( such as the " type " attribute which indicates the MIME type of the external entity, or the " charset " attribute which indicates its encoding ),

The MIME media type for JPEG is image / jpeg ( defined in RFC 1341 ), except in Internet Explorer, which provides a MIME type of image / pjpeg when uploading JPEG images.

MIME is specified in six linked RFC memoranda: RFC 2045, RFC 2046, RFC 2047, RFC 4288, RFC 4289 and RFC 2049, which together define the specifications.

Parts of MIME are also reused in communication protocols such as HTTP, which requires that data be transmitted in the context of email-like messages even though the data might not ( and usually doesn't ) actually have anything to do with email, and the message body can actually be binary.

A simple MIME text message is therefore likely to be interpreted correctly by a non-MIME client even if it has email headers which the non-MIME client won't know how to interpret.

There's a similar header called Message-ID which assigns a unique identifier to the message as a whole ; this is not actually part of the MIME standards, since it can be used on non-MIME as well as MIME messages.

The widely used Mozilla Thunderbird mail client makes its own decisions about which MIME parts should be automatically displayed, ignoring the content-disposition headers in the messages.

A MIME multipart message contains a boundary in the " Content-Type: " header ; this boundary, which must not occur in any of the parts, is placed between the parts, and at the beginning and end of the body of the message, as follows:

When PNG development started in early 1995, developers decided not to incorporate support for animation, because the majority of the PNG developers felt that overloading a single file type with both still and animation features is a bad design, both for users ( who have no simple way of determining to which class a given image file belongs ) and for web servers ( which should use the image / foo MIME type for stills and video / foo for animations -- GIF notwithstanding ).

In the default configuration, the content of the mail is appended as a MIME attachment, with a brief excerpt in the message body, and a description of the tests which resulted in the mail being classified as spam.

It suffers from many of the same flaws as uuencode does, a number of which had already been solved years before by MIME ( which addressed the same flaws in uuencode ).

) MIME places all such information in the message headers, which is far more reliable.

Some people, including yEnc's creator, have suggested including yEnc as part of MIME, which would solve nearly all of its problems and retain the low encoding overhead.

S / MIME specifies the MIME type ( smime-type " enveloped-data ") for data enveloping ( encrypting ) where the whole ( prepared ) MIME entity to be enveloped is encrypted and packed into an object which subsequently is inserted into an application / pkcs7-mime MIME entity.

" We did not adequately specify how to handle a future MIME version ," Borenstein said.

# MIME types aren't clear ; text / xml usually merely identifies the document as having XML content, while text / x-opml does not specify that the document is XML since it lacks the + xml suffix ( see XML and MIME ).

Email standards such as MIME don't specify any file size limits, but in practice email users will find that they can't send very large files.

As with all encodings apart from US-ASCII, when using Unicode text in email, MIME must be used to specify that a Unicode transformation format is being used for the text.