As per Relevance of the word followed, we have this rfc below:

---

Network Working Group S.
Request for Comments: 785 J.

July 1981

MAIL TRANSFER PROTOCOL
ISI TOPS20 FILE




This document defines the ISI TOPS20s interface between the
Transfer Protocol (MTP) and a mail creation system (e.g., MM, HERMES
etc.) in terms of the files which implement it. The
structure and name of each file is described below

For a complete understanding of the MTP protocol as well as the
used within this document, see RFC 780, "Mail Transfer Protocol".



For each piece of mail, the TOPS20 interface between a mail
system and MTP is comprised of two files. The first file must
named "^V[--UNSENT-MAIL-CONTROL--^V].MTP.-1", where "^V"
the character "control V" (ASCII code 026) and the generation
"-1" indicates the next higher generation number (at the time of
file's creation). It is strongly suggested that the second file
named "^V[--UNSENT-MAIL-FILE--^V].MTP.-1", where "^V" and "-1" are
defined before. (However, the actual file name may be chosen by
mail creation system.) Both these files reside in the directory
the user who created the mail (as is currently the case with
MAILER-based system).

"^V[--UNSENT-MAIL-CONTROL--^V].MTP.-1" is the control file. It is
ASCIZ file and contains all information necessary to relay the
through MTP. It consists of a pointer to the mail text,
source-path, and all destination-paths

First is "FILE:" followed by the FULL mail text file name (which
include directory name and generation number) followed by (ASCII code 15 followed by ASCII code 12). Note that a
name is allowed; if not given "PS:" will be assumed. Also note
for each character that must be quoted in a file name the
character (^V) must be present in the string following "FILE:".
is "FROM:" followed by the followed by . Finally
each destination is given in the form "TO:" followed by the followed by . The FROM- and TO-paths include surrounding
brackets (i.e., <...>) and are identical respectively to the source
and destination-paths described in RFC 780.





Sluizer & Postel Page [1]



July 1981 RFC 785
ISI TOPS20 File Definitions



---------------------------------------------------------------------
+------------------------+
|FILE: |
+------------------------+
|FROM: |
+------------------------+
| TO: |
+------------------------+
| ... |
+------------------------+
| TO: |
+------------------------+

File structure for ^V[--UNSENT-MAIL-CONTROL--^V].MTP.-1
Figure 1
---------------------------------------------------------------------

"^V[--UNSENT-MAIL-FILE--^V].MTP.-1" is the mail text file. (
that this is the file to which in the control
refers.) It is mail which conforms to the standard described in
733, "Standard for the Format of ARPA Network Text Messages".



The older mail creation systems create N copies of a mail text file
one for each of the N addresses in the TO, CC, and BCC fields.
file is named "^V[--UNSENT-MAIL--^V].^V@.-1",
and are as defined in MTP, and "^V" and "-1" are
defined above

The interface between the mail creation system and MTP requires
the creation of two files, regardless of the number of addresses
the TO, CC, and BCC fields. The control file contains
source-path and destination-paths information as well as a pointer
the mail text file. The mail text file contains the the RFC 733
header and body













Page [2] Sluizer &



RFC 785 July 1981
Mail Transfer





In this example, there were no previously existing versions of
the control file or the mail text file in directory where
message was created. Figure 2 shows the mail text file and figure 3
shows the control file

------------------------------------------------------------------
DATE: April 6, 1981
Sender: Linda at
From: Jon Postel To: DCrocker at UDel, Cerf at
Cc: postel@
Bcc: sluizer@
Subject: MTP

Your comments on the MTP document were most helpful. A
version will be forthcoming shortly

Thanks again
--

File contents of ^V[--UNSENT-MAIL-FILE--^V].MTP.1
Figure 2
------------------------------------------------------------------

------------------------------------------------------------------
+--------------------------------------------------+
|FILE:^V[--UNSENT-MAIL-FILE--^V].MTP.1|
+--------------------------------------------------+
|FROM: |
+--------------------------------------------------+
|TO: |
+--------------------------------------------------+
|TO: |
+--------------------------------------------------+
|TO: |
+--------------------------------------------------+
|TO: |
+--------------------------------------------------+

File contents of ^V[--UNSENT-MAIL-CONTROL--^V].MTP.1
Figure 3
------------------------------------------------------------------





Sluizer & Postel Page [3]

---

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.



RFC documents can be found at I.E.T.F.



Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX

---