Browse Prior Art Database

Multimedia E-mail (MIME) User Agent Checklist (RFC1820)

IP.com Disclosure Number: IPCOM000004078D
Original Publication Date: 1995-Aug-01
Included in the Prior Art Database: 2019-Feb-12
Document File: 8 page(s) / 10K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Huizer: AUTHOR

Related Documents

10.17487/RFC1820: DOI

Abstract

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 memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 24% of the total text.

Network Working Group E. Huizer Request for Comments: 1820 SURFnet bv Category: Informational 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.

Abstract

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.

Introduction

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 mime-check@relay.surfnet.nl and this information will be made available (at no cost) through WWW (to be announced) for other people to browse through.

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.

Huizer Informational [Page 1]

RFC 1820 MIME User Agent Checklist August 1995

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 <mime- test@relay.surfnet.nl> 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 message/external multipart/mixed multipart/parallel multipart/digest multipart/alternative application/wordperfect5.1 application/msword application/rtf X-local <to test how your UA deals with undefined content-types> nested <returns a message that contains nested multipart contents> iso-8859-1 <returns a message with text/plain; charset=iso-8859-1>

A message containing the requested content-type will be returned to the address contained in the from field.

References

The reader is encouraged to also check out the following references:

The MIME standards:

- Borenstein N. and N. Freed, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for specifying and describing the format of Internet message bodies", RFC 1521, Bellcore, Innosoft, September 1993.

- Moore K., "MI...

Processing...
Loading...