RFC 1648: Postmaster Convention for X.400 Operations
In plain English — editorial summary, not part of the RFC
This paper extends this concept to X.400 mail domains which have registered RFC 1327 mapping rules, and which therefore appear to have normal RFC822-style addresses. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1648
- Published
- July 1994
- Authors
- A. Cargille
- Status
- HISTORIC
- Stream
- IETF
- Area
- app
- Pages
- 4
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1649Operational Requirements for X.400 Management Domains in the GO-MHS CommunityCurrent
July 1994
- RFC 1653SMTP Service Extension for Message Size DeclarationObsoleted
July 1994
- RFC 1767MIME Encapsulation of EDI ObjectsCurrent
March 1995
- RFC 1523The text/enriched MIME Content-typeObsoleted
September 1993
- RFC 1502X.400 Use of Extended Character SetsCurrent
August 1993
- RFC 1496Rules for downgrading messages from X.400/88 to X.400/84 when MIME content-types are present in the messagesCurrent
August 1993
- RFC 1495Mapping between X.400 and RFC-822 Message BodiesObsoleted
August 1993
- RFC 1801MHS use of the X.500 Directory to support MHS RoutingCurrent
June 1995
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?