Multimedia E-mail (MIME) User Agent Checklist (RFC1844)
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
This document presents a checklist to facilitate evaluation of MIME capable User Agents. Access to a MIME test-responder, that generates test-messages is described.
Network Working Group E. Huizer
Request for Comments: 1844 SURFnet bv
Obsoletes: 1820 August 1995
Multimedia E-mail (MIME) User Agent checklist
Status of this Memo
This memo provides information for the Internet community. This memo
does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This document presents a checklist to facilitate evaluation of MIME
capable User Agents. Access to a MIME test-responder, that generates
test-messages is described.
This document presents a checklist that facilitates evaluation of
MIME capable E-mail User Agents. It is by no means a conformance or
interoperability (both strictly defined and measurable quantities)
checklist, but rather an interworking (practical perspective)
checklist that is aimed at the users and system managers.
Usage and submission
If you use this checklist against a specific product (regardless of
whether you're a vendor, implementor or user) you can submit the
result to email@example.com, make sure that the subject
reflects the name and version of the product. This is an automated
mailhandler, so PLEASE only submit filled-in checklists (in content-
type text/plain or text/html) to this address. This information will
be made available (at no cost) for other people to browse through at
Although SURFnet will attempt to verify the correctness of each
submission, all submitted information is made available as is, with
no guarantees (SURFnet does not take any responsibility for errors in
the data that is made available, or for any damages resulting from
usage of that data). Users who want to procure a UA are advised to
use the data as an orientation, and to perform their own procurement
tests (possibly using the checklist below as a guideline). Also it is
noted that vendors and implementors are encouraged to use the results
from the checklist to improve their products.
Getting test messages
For several tests in the checklist a test message is required. Test
messages can be requested in the following way: Send mail to firstname.lastname@example.org> with a subject field containing ONE of the following: text/plain text/enriched image/gif image/jpeg audio/basic video/mpeg application/octet-stream application/postscript message/rfc822 message/partial ...
email@example.com> with a subject field containing ONE of the