MIME also specifies rules for encoding non-ASCII characters in email message headers, such as " Subject :", allowing these header fields to contain non-English characters.

Since RFC 2822, conforming message header names and values should be ASCII characters ; values that contain non-ASCII data should use the MIME encoded-word syntax ( RFC 2047 ) instead of a literal string.

The server SMTP at the receiver's side receives the NVT ASCII data and delivers it to MIME to be transformed back to the original non-ASCII data.

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.

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.

In June 1992, MIME ( RFC 1341, since made obsolete by RFC 2045 ) defined a set of methods for representing binary data in ASCII text format.

Base64 is commonly used in a number of applications including email via MIME, and storing complex data in XML.

iCalendar data has the MIME content type text / calendar.

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

S / MIME provides the following cryptographic security services for electronic messaging applications: authentication, message integrity, non-repudiation of origin ( using digital signatures ), privacy and data security ( using encryption ).

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.

* Proper use of HTTP and MIME to deliver the page, return data from it and to request other resources referenced in it, based on < nowiki > RFC 2616 </ nowiki >, from IETF.

S / MIME provides a consistent means to securely send and receive MIME data.

S / MIME is not only limited to email but can be used with any transport mechanism that carries MIME data, such Hypertext Transfer Protocol ( HTTP ).

This includes pasteboard data and data streaming over a protocol such as HTTP where a MIME type has been given.

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:

Erroneous labels " image / ico ", " image / icon ", " text / ico " and " application / ico ", along with the unofficial name " image / x-icon " were in use at the time of official registration and assignment of the MIME type.

May have a " title " attribute to indicate additional information, a " type " attribute to indicate the MIME type of the resource at the destination of the href, a " rel " attribute to indicate the relationship of the resource at the href to this outline ( e. g. using XFN ), and / or a " rev " attribute to indicate the relationship of this outline to the resource at the href ( e. g. using VoteLinks ).

This may be achieved by standardising on a single byte order, by specifying the endianness as part of external metadata ( for example the MIME charset registry has distinct UTF-16BE and UTF-16LE registrations ) or by using a byte-order mark at the start of the text.

Because the MIME format uses a carriage return to delimit the information in a message, and only the raw message determines its eventual destination, adding carriage returns to submitted form data can allow a simple guestbook to be used to send thousands of messages at once.

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.

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.

Shift JIS ( also SJIS, MIME name Shift_JIS ) is a character encoding for the Japanese language, originally developed by a Japanese company called ASCII Corporation in conjunction with Microsoft and standardized as JIS X 0208 Appendix 1.

While the ASCII range is encoded as one octet, as in UTF-8, the ASCII octets 0x21-0x7E ( decimal 33-126 ) are also used in UTF-1 multi-byte encodings ; therefore UTF-1 is unsuited for many Internet protocols, including MIME.

STD 71 ( RFC 6152, < abbr title =" SMTP Service Extension for 8-bit MIME Transport "> 8BITMIME </ abbr >), and STD 72 ( RFC 6409, Mail Submission ) published in 2011.

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

* Multipurpose Internet Mail Extensions ( MIME )

* MIME ( S-MIME ), Multipurpose Internet Mail Extensions and Secure MIME

* RFC 3851: Secure / Multipurpose Internet Mail Extensions ( S / MIME ) Version 3. 1 Message Specification

* RFC 5751: Secure / Multipurpose Internet Mail Extensions ( S / MIME ) Version 3. 2 Message Specification ( Draft Tracker )

* Secure / Multipurpose Internet Mail Extensions ( S / MIME )

PDN Mail was years ahead of its time and was also used by Microsoft Corporation until MIME was introduced.

Before MIME existed, PDN Mail was able to perform the same functions and was used to send software updates as well as all sorts of attachments between systems.

Other useful standards in this space include the Multipurpose Internet Mail Extensions ( MIME ) for registering the format of the IMPS protocol messages.

* RFC 2652 MIME Object Definitions for the Common Indexing Protocol ( CIP )

Virtually all human-written Internet email and a fairly large proportion of automated email is transmitted via SMTP in MIME format.

Internet email is so closely associated with the SMTP and MIME standards that it is sometimes called SMTP / MIME email.

Mapping messages into and out of MIME format is typically done automatically by an email client or by mail servers when sending or receiving Internet ( SMTP / MIME ) email.

In North America X. 400 is still used in some applications, such as the military, intelligence services and aviation, mainly because the X. 400 functions for integrity and security were developed and deployed much earlier than their SMTP counterparts ( S / MIME, PGP and SMTP-TLS ).

With MIME, a message and all its attachments are encapsulated in a single multipart message, with base64 encoding to convert binary into 7-bit ASCII-or on modern mail servers running Extended SMTP, optionally full 8-bit support via the 8BITMIME extension.

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.

* Standards-compliant support for SMTP, LMTP, STARTTLS encryption, SASL authentication, MIME, DSN delivery status notifications, IPv4, and IPv6 ;