A MIME message consists of both data and metadata. MIME metadata consists of HTTP-style headers and MIME boundary delimiters. Each header is a colon-separated name-value pair on a line. The ASCII sequence <CR><LF> terminates the line. A sequence of these headers, called a header block, is terminated by a blank line: <CR><LF><CR><LF>. Any headers following this HTTP-style can appear in a MIME document. A number of standard MIME headers are described in MIME standard header fields.
The only header that the MIME parser insists on being present is the Content-Type header. This header specifies the type of the data in the message. If the Content-Type value starts with "multipart" then the message is a multipart MIME message. For multipart messages the Content-Type must also include a boundary attribute giving the text used to delimit the message parts. Each separate MIME Part has its own Content-Type field that specifies the type of the data in the Part. This may also be multipart, allowing multipart messages to be nested. MIME parts with any other Content-Type values are handled as BLOB data.
SET OutputRoot.Properties.ContentType = 'text/plain';
S/MIME is a standard for sending secure e-mail. S/MIME has an outer level Content-Type of multipart/signed with parameters protocol and micalg that define the algorithms used to encrypt the message. One or more MIME parts can have encoded content. These parts have Content-Type values such as application/pkcs7-signature and a Content-Transfer-Encoding of base64. The MIME domain does not attempt to interpret or verify whether the message is actually signed.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac30080_ |