RFC 1524: A User Agent Configuration Mechanism For Multimedia Mail Format Information
In plain English — editorial summary, not part of the RFC
This memo suggests a file format to be used to inform multiple mail reading user agent programs about the locally-installed facilities for handling mail in various formats. This memo provides information for the Internet community. It does not specify an Internet standard.
Document record
- Document ID
- RFC1524
- Published
- September 1993
- Authors
- N. Borenstein
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1806Communicating Presentation Information in Internet Messages: The Content-Disposition HeaderObsoleted
June 1995
- RFC 1864The Content-MD5 Header FieldCurrent
October 1995
- RFC 2183Communicating Presentation Information in Internet Messages: The Content-Disposition Header FieldUpdated
August 1997
- RFC 1544The Content-MD5 Header FieldObsoleted
November 1993
- RFC 5068Email Submission Operations: Access and Accountability RequirementsUpdated
November 2007
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 7681Email Exchange of Secondary School TranscriptsCurrent
October 2015
- RFC 8255Multiple Language Content TypeCurrent
October 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?