RFC 498 (rfc498) - Page 2 of 3
On mail service to CCN
Alternative Format: Original Text Document
RFC 498 ON MAIL SERVICE TO CCN April 1973 disseminating Network documentation as well as messages. It is based upon extensions of the pathname/user name fields in the MLFL/MAIL commands, respectively. The proposed syntax is as follows: __ __ | | | ;D[DOCUMENT] | | ;M[MESSAGE] || ;C[COPIES]= | | ;BIN= | |__ __| The semantics would be: (1) will normally be a valid TSO userid; this will be used to determine a charge number to account for the printing. If is _not_ recognized, the rest of the parameters will be ignored, but the mail will still be accepted. The result will be to print one copy immediately in upper case and send it to Bin 9906, charging it to an overhead account. (2) MESSAGE means print a copy immediately using the normal upper-case-only train. This is the default. (3) DOCUMENT means enqueue the text for overnight printing with an upper/lower case print train. A message indicating receipt (and perhaps the first block) will also be printed immediately in upper case and distributed. (4) COPIES makes multiple copies. [This facility will not be available immediately]. (5) BIN specifies CCN bin to receive output. Default will be 9906 (ARPA mail bin). Each incoming message will be time-and-date-stamped. The time/date will appear on the first page of the message (on a separate page in the case of upper/lowercase), in the 256 acknowledgment message from FTP, and on our system log file. This time/date stamp may be useful for users to keep tabs on their documents, and to allow us to track down missing messages. The semicolon and equal sign delimiters of this syntax are acceptable in the "user" parameter to SNDMSG. This extended MAIL syntax will be implemented by June 1. RTB/gjm BRADEN
