Index Journeys
RFC 786 UNKNOWN EMAIL · SYSTEM INTERFACE

Mail Transfer Protocol: ISI TOPS20 MTP-NIMAIL interface

The file interface between MTP and NIMAIL on ISI TOPS-20.

On rfc-editor.org ↗
PUBLISHED
July 1981
AUTHORS
S. Sluizer, J. Postel
STREAM
Legacy
MTP-TO-NIMAIL FILE EXTENSION
.NIMAIL.-1
DATE-TIME FORMAT
dd-mmm-yy hh:mm:ss, 24-hour
DOI
10.17487/RFC0786

RFC text

Contents
Original text · RFC Editor View on rfc-editor.org ↗ 
Network Working Group                                         S. Sluizer
Request for Comments: 786                                      J. Postel
                                                                     ISI
                                                               July 1981

                        MAIL TRANSFER PROTOCOL:
                    ISI TOPS20 MTP-NIMAIL INTERFACE


INTRODUCTION

   This document defines the ISI TOPS20s interface between the Mail
   Transfer Protocol (MTP) and the Network Independent Mail Protocol
   (NIMAIL) in terms of the files which implement it.  The internal
   structure and name of each file is described below.

   For a complete understanding of the MTP protocol as well as the terms
   used within this document, see RFC 780 "Mail Transfer Protocol", RFC
   784 "ISI TOPS20 Implementation", and RFC 785 "ISI TOPS20 File
   Defintitions".  The NIMAIL is documented in IEN 169, "A Simple
   NIFTP-Based Mail System".

DESCRIPTION

   1. NIMAIL to MTP

      NIMAIL will present mail for processing by MTP using the files
      specified in RFC 785.

   2. MTP to NIMAIL

      MTP will present mail for processing by NIMAIL in files of the
      following form:

         address <CR><LF>
         address <CR><LF>
         address <CR><LF>
         <CR><LF>
         Via: USC-ISIE; date-time <CR><LF>
         header
          .
          .
          .
         <CR><LF>
         body
          .
          .
          .

         Where each address is of the form:




Sluizer & Postel                                                Page [1]

ISI TOPS20 MTP-NIMAIL Interface



            user%host%host%host@host

         And each address in the same file has the same "@host" part.

         The date-time will be in the default TOPS20 ODTIM format
         "dd-mmm-yy hh:mm:ss" (24 hour time).

      The files will named "arbitrary.NIMAIL.-1", where "arbitrary" will
      be somesort of date-time encoding for human uses.  The NIMAIL will
      not care in the least what the "arbitrary" part is.  These files
      will be placed into the NIMAIL directory on ISIE.

DISCUSSION

   The NIMAIL and MTP will each perform a transformation of the address
   information to create the appropriate input for the other system.

   NIMAIL to MTP

      The mail that arrives at NIMAIL with the information

         joe%hostx%hosty%hostz@isie

      will be presented to MTP with the information

         FROM: <NIMAIL@ISIE>
         TO: <@hostz,@hosty,joe@hostx>

   MTP to NIMAIL

      The mail that arrives at MTP with the information

         FROM: <sam@SRI-NIC>
         TO: <@ISIE,@hostz,@hosty,joe@hostx>

      will be presented to NIMAIL with the information

         joe%hostx%hosty@hostz

         Via: ISIE









Page [2]                                                Sluizer & Postel

ISO Plain Language

On this page
PROBLEMThe MTP and NIMAIL mail systems on ISI TOPS-20 need defined files and address transformations to exchange messages.
MECHANISMNIMAIL presents files in the RFC 785 format; MTP presents a recipient list, Via line, headers, and body in files placed in the NIMAIL directory.
THE INTERFACEThe memo specifies the bidirectional file interface and shows how each system transforms the other's address format.

§1A File-Based Mail Interface

The memo defines the interface between the Mail Transfer Protocol and Network Independent Mail on ISI TOPS-20 in terms of the files each system uses. NIMAIL gives MTP files in the format defined by RFC 785.

MTP gives NIMAIL files with destination addresses, a Via line, headers, and a body.

The two mail systems pass messages by placing files in the format expected by the other system. This memo defines those file forms for ISI TOPS-20.

§2Mail from MTP to NIMAIL

An MTP-to-NIMAIL file starts with one or more recipient addresses, followed by a blank line and a Via line containing the sending host and date-time. The message headers and body follow.

Addresses in one file must share the same final @host part. The file name ends in .NIMAIL.-1 and the file is placed in the NIMAIL directory.

The file begins with its recipients and routing information, then contains the message. Recipients in one file share the same final host part.

§3Converting Address Formats

When NIMAIL sends joe%hostx%hosty%hostz@isie to MTP, the interface represents the sender as NIMAIL at ISIE and converts the destination into an MTP route.

In the reverse direction, the MTP address <@ISIE,@hostz,@hosty,joe@hostx> is converted to a NIMAIL percent-routed address and a Via line identifying ISIE.

NIMAIL and MTP write routed addresses differently. Each side converts the address when it prepares the file for the other system.