[permalink] [id link]
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:
from
Wikipedia
Some Related Sentences
MIME and multipart
Usually all Internet e-mail is transmitted in MIME format, allowing messages to have a tree structure where the leaf nodes are any of a variety of single part content types and the non-leaf nodes are any of a variety of multipart types.
Through the use of the multipart type, MIME allows messages to have parts arranged in a tree structure where the leaf nodes are any non-multipart content type and the non-leaf nodes are any of a variety of multipart types.
For example, a multipart MIME message using the digest subtype would have its Content-Type set as " multipart / digest ".
xYzZY is used as the default boundary marker by the Perl HTTP :: Message module for multipart MIME messages, and was used in Apple's AtEase for workgroups as the default administrator password in the 1990s.
As some of these encoding formats are not capable of incorporating all metadata making up a coverage, GMLCOV foresees a multipart MIME encoding ( see Figure ) where the first component encodes the coverage description ( domain extent, range type, metadata, etc.
The MIME type for this is multipart / signed with the second part having a MIME subtype of application /( x -) pkcs7-signature.
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.
A DSN may be a MIME multipart / report message composed of three parts:
When more than control is carried in a message, the format of the message is a MIME multipart / related compound object.
The control entity MUST be the first entity in the MIME multipart / related message.
The content entity MUST be the second entity in the MIME multipart / related message.
The capabilities entity, if present, MUST be the third entity in the Push Submission MIME multipart / related message and MUST be the second entity in a Client Capabilities Query response.
MIME and message
With the advent of MIME, IMAP2 was extended to support MIME body structures and add mailbox management functionality ( create, delete, rename, message upload ) that was absent in IMAP2.
The IMAP4 protocol allows clients to separately retrieve any of the individual MIME parts and also to retrieve portions of either individual parts or the entire message.
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.
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.
These goals were achieved by using additional RFC 822-style headers for all MIME message attributes and by making the MIME headers optional with default values ensuring a non-MIME message is interpreted correctly by a MIME-capable client.
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.
A MIME message including an attached file generally indicates the file's original name with the " Content-disposition :" header, so the type of file is indicated both by the MIME content-type and the ( usually OS-specific ) filename extension
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.
This is a message with multiple parts in MIME format.
The MIME standard defines various multipart-message subtypes, which specify the nature of the message parts and their relationship to one another.
Rfc822 is a misnomer, since the message may be a full MIME message.
When a document is transmitted via a MIME message or a transport that uses MIME content types such as an HTTP response, the message may signal the encoding via a Content-Type header, such as.
MIME and contains
If this " plain text " convention is not followed, then the CSV file no longer contains sufficient information to interpret it correctly, the CSV file will not likely survive transmission across differing computer architectures, and will not conform to the text / csv MIME type.
MIME and Content-Type
The MIME Content-Type for this encoding is therefore " text / plain ; charset = macintosh ".
The web server is configured to deliver Alluvium playlists with MIME type Content-Type: application / x-alluvium for files with the extension. rss
MIME and header
The content-transfer-encoding: MIME header has 2-sided significance:
MIME and ;
; RFC 1847: Security Multiparts for MIME: Multipart / Signed and Multipart / Encrypted
; RFC 3156: MIME Security with OpenPGP
; 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 4288: MIME Part Four: Media Type Specifications and Registration Procedures.
; RFC 4289: MIME Part Four: Registration Procedures.
; RFC 2049: MIME Part Five: Conformance Criteria and Examples.
; RFC 2231: MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations.
; RFC 2387: The MIME Multipart / Related Content-type
By default, iCalendar uses the UTF-8 character set ; a different character set can be specified using the " charset " MIME parameter ( if the transport method used supports MIME, such as Email or HTTP ).
A slightly modified version of quoted-printable is used in message headers ; see MIME # Encoded-Word.
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 ).
; MIME types: Instruct the server how to treat different varying file types.
The kinemage information is stored in a human-as well as machine-readable text file that describes the hierarchy of display objects and their properties, and that also includes optional explanatory text ; the kinemage format is a defined chemical MIME type of ' chemical / x-kinemage ' with the file extension '. kin '.
# 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 ).
* Standards-compliant support for SMTP, LMTP, STARTTLS encryption, SASL authentication, MIME, DSN delivery status notifications, IPv4, and IPv6 ;
0.279 seconds.