Content-Type: message
The message content type allows messages to contain other messages or pointers to other messages.
- message/delivery-status [RFC1894]
The message/delivery-status content type is defined for use in message delivery status notification, allowing automated information transmission.
- message/disposition-notification-to [RFC2298]
- The message/disposition-notification-to content type adds enhanced functionality to messaging. This works within the framework of the multipart/report content type.
- message/external-body [RFC1521]
- The message/external-body content type allows the contents of a message to be external to the message and only referenced in the message. The only required parameter of this content type is access-type, which can have values such as "FTP" and "LOCAL-ACCESS." If values are used that have not been registered with IANA, then they begin with "x-".
Message/external-body parts must include a Content-ID header field with a unique identifier to reference the external data.
- message/http [RFC2068]
The message/http content type is not strictly a MIME content type. Provisions are made in the definition of HTTP to allow it to be used over MIME transport mechanisms, but there must be a conversion between HTTP and MIME for strict MIME adherence.
- message/partial [RFC1521]
- The message/partial content type allows for large messages to be broken up into smaller messages. The full message can then be put back together by the UA. Only 7bit content-transfer-encoding is allowed for this content type. Three parameters are required:
- id: a unique identifier used to match up the pieces.
- number: an integer identifying which piece of the message this is.
- total: an integer indicating the total number of parts the message has. This parameter is required only on the final fragment of the message, but should be used on all parts.
- message/rfc822 [RFC1521]
- The message/rfc822 content type is used to enclose a complete message within a message. It is different from other MIME body parts in that it must be a fully formed RFC822 message, complete with headers.