MHTML test messages

By Rickard Hentze and Aiko Muto at the Department of Computer and Systems Sciences, Stockholm University and KTH. Revised by Jacob Palme.

We have prepared a set of test messages which demonstrate different variations of sending e-mail in HTML format according to RFC 2557. These test messages are partly a revision of a set of test messages developed by Jacob Palme for the 1997 version of the MHTML proposed standard.

The URL-s for retrieval of these test message files is <http://dsv.su.se/jpalme/ietf/mhtml-test/<file name>> where <file name> is the file name in the table below.

More information about MTHML, sending HTML in aggregate multipart MIME messages.

Results of testing mail programs with these test programs.

Addition by Jacob Palme: I have added two test messages mhtml-16.txt and mhtml-17.txt in order to test the combination of multipart/alternative with Content-ID relations between body parts.

Last revision: 12 June 2000.

File name

Description

mhtml-1.txt

Three body parts: one text/html, two inline GIFs, the inline GIFs have Content-Disposition. Uses Content-ID URLs to the inline GIFs.
This message checks whether the e-mail clients can handle Content-ID URIs and Content-Type: multipart/related.

mhtml-2.txt

Three body parts: one text/html, two inline GIFs. The inline GIFs have no Content-Disposition headers. The MHTML standard says that Content-Disposition should be ignored within multipart/related, so this should not have any effect on rendering. Uses Content-ID URLs to the inline GIFs.
This message checks whether the e-mail clients can handle messages without Content-Disposition headers.

mhtml-3.txt

One text/html body part. Both images have to be retrieved using HTTP. Uses absolute URIs to the non embedded GIF pictures.
This message checks whether the e-mail clients can retrieve objects using a URI specified protocol, such as HTTP.

mhtml-4.txt

Three body parts: one text/html, one inline GIF. Uses Content-ID URL to the embedded inline GIF. One image is not included and has to be retrieved using HTTP.
This message checks whether the e-mail clients can handle messages with different link types (Content-ID, Content-Location URIs).

mhtml-5.txt

Three body parts: one text/html, two inline GIFs. Uses absolute URIs to the embedded GIFs. One image has an absolute Content-Location, one has a relative Content-Location.
This message checks whether the e-mail clients support Content-Location with absolute URIs for links between body parts.

mhtml-6.txt

Two body parts: one text/html, one inline GIF. The relative URI is resolved without an explicit base available.
This message checks whether the e-mail clients support Content-Location with relative URIs with no explicit base available.

mhtml-7.txt

Three body parts: one text/html, two inline GIFs. Uses relative URIs to the inline GIF pictures. Uses a Content-Location header in the multipart/related heading as a base. One image must be retrieved using HTTP. One image has a relative Content-Location that must be resolved by BASE specified in the multipart/related Content-Location header. One image has an absolute Content-Location.
This message checks whether the e-mail clients support Content-Location with relative URIs, which are resolved to absolute URIs through base indicated in a Content-Location in a surrounding multipart content heading.

mhtml-8.txt

Three body parts: one text/html, two inline GIFs. Uses relative URIs to embedded GIF pictures. A Content-Location header in the text/html heading will be a BASE to all relative URIs. The embedded GIF pictures have absolute Content-Location headers.
This message checks whether the e-mail clients support Content-Location header to indicate a base to be used for other URIs in the same content body.

mhtml-9.txt

A multipart/mixed, which contains two body parts. One of type multipart/related with one text/html part and two inline GIF pictures. The other of type text/html where the images are not included and have to be retrieved using HTTP. Uses relative URIs to the inline GIF pictures. In the first multipart/related the two inline GIF pictures are embedded. One image has an absolute Content-Location. One has a relative Content-Location which must be recursively resolved using the BASE specified in the multipart/mixed heading.
This message checks whether the e-mail clients support Content-Location header on a multipart body to apply recursively to included body parts.

mhtml-10.txt

Three body parts: one text/html, two inline GIFs. Uses relative URIs to the inline GIF pictures. One image has a relative Content-Location, one has an absolute Content-Location. One image must be retrieved using HTTP. The relative Content-Location is resolved by <BASE> in the HTML markup.
This message checks whether the e-mail clients support use of the HTML <BASE> element for resolution of relative URIs.

mhtml-11.txt

A multipart/mixed, which contains two body parts: each of type multipart/related. In the first multipart/related part the reference is of the absolute URI kind with absolute Content-Location. The other multipart/related part has a reference of the Content-ID type.
This message checks if the e-mail clients support more than one multipart/related in the same e-mail message.

mhtml-12.txt

Four body parts: one text/plain, one text/html, two inline GIFs. Uses relative URIs to the embedded GIF pictures. Uses multipart/alternative inside multipart/related to provide a choice between a plain text and HTML rendition.
This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative outside the multipart/related.

mhtml-13.txt

Four body parts: one text/plain, one text/html, two inline GIFs. Uses relative URIs to the embedded GIF pictures. Uses multipart/alternative outside multipart/related to provide a choice between plain text and multipart/related.
This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative inside the multipart/related as the start body part of the multipart/related.

mhtml-14.txt

Three body parts: one text/html, two inline GIFs. Uses relative URIs to the embedded GIF pictures. The URI in Content-Location is folded. One image must be retrieved using HTTP, one image has an absolute Content-Location, one image has a relative Content-Location that must be resolved by base specified in the multipart/related Content-Location heading.
This message checks if the e-mail clients support unfolding of received URIs in MIME header fields.

mhtml-15.txt

Three body parts: one text/html, two inline GIFs. Uses relative URIs to the inline GIF pictures. The Content-Location contains illegal characters (å, ä and ö). One image must be retrieved using HTTP, one image has an absolute Content-Location and one image has a relative Content-Location that must be resolved by the BASE specified in the multipart/related Content-Location heading.
This message checks if the e-mail clients support decoding of received URIs in MIME header fields.

mhtml-16.txt

Four body parts: one text/plain, one text/html, two inline GIFs. Differs from mhtml-12.txt in that it uses cid-type URIs to the embedded GIF pictures. Uses multipart/alternative inside multipart/related to provide a choice between a plain text and HTML rendition.
This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative outside the multipart/related.

mhtml-17.txt

Four body parts: one text/plain, one text/html, two inline GIFs. Differs from mhtml-13.txt in that it uses cid-type URIs to the embedded GIF pictures. Uses multipart/alternative outside multipart/related to provide a choice between plain text and multipart/related.
This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative inside the multipart/related as the start body part of the multipart/related.

mhtml-18.txt Same as mhtml-17, but with multipart/alternative inside multipart/related.

File name	Description
mhtml-1.txt	Three body parts: one text/html, two inline GIFs, the inline GIFs have Content-Disposition. Uses Content-ID URLs to the inline GIFs. This message checks whether the e-mail clients can handle Content-ID URIs and Content-Type: multipart/related.
mhtml-2.txt	Three body parts: one text/html, two inline GIFs. The inline GIFs have no Content-Disposition headers. The MHTML standard says that Content-Disposition should be ignored within multipart/related, so this should not have any effect on rendering. Uses Content-ID URLs to the inline GIFs. This message checks whether the e-mail clients can handle messages without Content-Disposition headers.
mhtml-3.txt	One text/html body part. Both images have to be retrieved using HTTP. Uses absolute URIs to the non embedded GIF pictures. This message checks whether the e-mail clients can retrieve objects using a URI specified protocol, such as HTTP.
mhtml-4.txt	Three body parts: one text/html, one inline GIF. Uses Content-ID URL to the embedded inline GIF. One image is not included and has to be retrieved using HTTP. This message checks whether the e-mail clients can handle messages with different link types (Content-ID, Content-Location URIs).
mhtml-5.txt	Three body parts: one text/html, two inline GIFs. Uses absolute URIs to the embedded GIFs. One image has an absolute Content-Location, one has a relative Content-Location. This message checks whether the e-mail clients support Content-Location with absolute URIs for links between body parts.
mhtml-6.txt	Two body parts: one text/html, one inline GIF. The relative URI is resolved without an explicit base available. This message checks whether the e-mail clients support Content-Location with relative URIs with no explicit base available.
mhtml-7.txt	Three body parts: one text/html, two inline GIFs. Uses relative URIs to the inline GIF pictures. Uses a Content-Location header in the multipart/related heading as a base. One image must be retrieved using HTTP. One image has a relative Content-Location that must be resolved by BASE specified in the multipart/related Content-Location header. One image has an absolute Content-Location. This message checks whether the e-mail clients support Content-Location with relative URIs, which are resolved to absolute URIs through base indicated in a Content-Location in a surrounding multipart content heading.
mhtml-8.txt	Three body parts: one text/html, two inline GIFs. Uses relative URIs to embedded GIF pictures. A Content-Location header in the text/html heading will be a BASE to all relative URIs. The embedded GIF pictures have absolute Content-Location headers. This message checks whether the e-mail clients support Content-Location header to indicate a base to be used for other URIs in the same content body.
mhtml-9.txt	A multipart/mixed, which contains two body parts. One of type multipart/related with one text/html part and two inline GIF pictures. The other of type text/html where the images are not included and have to be retrieved using HTTP. Uses relative URIs to the inline GIF pictures. In the first multipart/related the two inline GIF pictures are embedded. One image has an absolute Content-Location. One has a relative Content-Location which must be recursively resolved using the BASE specified in the multipart/mixed heading. This message checks whether the e-mail clients support Content-Location header on a multipart body to apply recursively to included body parts.
mhtml-10.txt	Three body parts: one text/html, two inline GIFs. Uses relative URIs to the inline GIF pictures. One image has a relative Content-Location, one has an absolute Content-Location. One image must be retrieved using HTTP. The relative Content-Location is resolved by <BASE> in the HTML markup. This message checks whether the e-mail clients support use of the HTML <BASE> element for resolution of relative URIs.
mhtml-11.txt	A multipart/mixed, which contains two body parts: each of type multipart/related. In the first multipart/related part the reference is of the absolute URI kind with absolute Content-Location. The other multipart/related part has a reference of the Content-ID type. This message checks if the e-mail clients support more than one multipart/related in the same e-mail message.
mhtml-12.txt	Four body parts: one text/plain, one text/html, two inline GIFs. Uses relative URIs to the embedded GIF pictures. Uses multipart/alternative inside multipart/related to provide a choice between a plain text and HTML rendition. This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative outside the multipart/related.
mhtml-13.txt	Four body parts: one text/plain, one text/html, two inline GIFs. Uses relative URIs to the embedded GIF pictures. Uses multipart/alternative outside multipart/related to provide a choice between plain text and multipart/related. This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative inside the multipart/related as the start body part of the multipart/related.
mhtml-14.txt	Three body parts: one text/html, two inline GIFs. Uses relative URIs to the embedded GIF pictures. The URI in Content-Location is folded. One image must be retrieved using HTTP, one image has an absolute Content-Location, one image has a relative Content-Location that must be resolved by base specified in the multipart/related Content-Location heading. This message checks if the e-mail clients support unfolding of received URIs in MIME header fields.
mhtml-15.txt	Three body parts: one text/html, two inline GIFs. Uses relative URIs to the inline GIF pictures. The Content-Location contains illegal characters (å, ä and ö). One image must be retrieved using HTTP, one image has an absolute Content-Location and one image has a relative Content-Location that must be resolved by the BASE specified in the multipart/related Content-Location heading. This message checks if the e-mail clients support decoding of received URIs in MIME header fields.
mhtml-16.txt	Four body parts: one text/plain, one text/html, two inline GIFs. Differs from mhtml-12.txt in that it uses cid-type URIs to the embedded GIF pictures. Uses multipart/alternative inside multipart/related to provide a choice between a plain text and HTML rendition. This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative outside the multipart/related.
mhtml-17.txt	Four body parts: one text/plain, one text/html, two inline GIFs. Differs from mhtml-13.txt in that it uses cid-type URIs to the embedded GIF pictures. Uses multipart/alternative outside multipart/related to provide a choice between plain text and multipart/related. This message checks if the e-mail clients support combination of multipart/related with multipart/alternative, with multipart/alternative inside the multipart/related as the start body part of the multipart/related.
mhtml-18.txt	Same as mhtml-17, but with multipart/alternative inside multipart/related.

Back to MHTML main page