RFC629 Scenario for using the Network Journal

0629 Scenario for using the Network Journal. J.B. North. March 1974. (Format: TXT=4504 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                       Jeanne North
Request for Comment: 629                                         SRI-ARC
NIC 22383                                                 March 27, 1974

                 SCENARIO FOR USING THE NETWORK JOURNAL

Network users may send mail to individuals and to groups, input as
messages or entire files, through the Network Journal, using SNDMSG or
their site's mail system.  The mail is converted at NIC into NLS files,
Journalized, and sent to specified recipients.  Short messages may be
received as messages, longer ones as citations to files which may be
retrieved immediately, and also later, by using FTP.  Mail sent to NIC
with a "/" in the user-name field invokes the Net Journal.

SENDING THE MESSAGE OR FILE BY TELEX SNDMSG

   Construct user field with slash and NIC idents:

      [Users:] sender ident/addressee ident(s)@NIC

   e.g. "JEW/DHC MAP@NIC". To send to a group, use group ident, e.g.
   "JEW/NLG@NIC". To combine Journal SNDMSG with SNDMSG to others, add
   others' Network addresses after commas, e.g. "JEW/DHC@NIC,PRATT@ISI".
   See ARPANET Directory for NIC idents and Network addresses.

   [@] SNDMSG 
   [Type ? for help]
   [Users:] JEW/NGG  DHC@NIC, PRATT@ISI 
   [Subject:] Title of Message 
   [Message (? for help):] Text of message ...
      Note: ^B allows insertion of a sequential file as the message or
      at any point in the test of the message:

      ^B [(Insert file:)] file  [ext ...EOF)]
   <^Z>
   [jew/ngg dhc@nic -- ok]   (or [ -- queued -- timed-out])
   [pratt@isi -- ok]

   When using SNDMSG through TELNET, change TELNET escape character, to
   ^Q for example, allowing ^Z to be used for end-of-message.

RETRIEVING THE FILE FROM NETWORK JOURNAL

   Substitute the citation received, for example "21695", for
   "number" and supply a filename in the following:

   [@] FTP 
   [HOST FTP User process x.xx.x]



North                                                           [Page 1]

RFC 629                Using the Network Journal              March 1974


   [*] CONN  NIC 
   [   Connection opened]
   [*< OFFICE-1 FTP Server x.xx.x - at DAY DATE TIME]
   [*] LOG  ANONYMOUS  NIC 
   [*] GET  number.NLS;xnls 
   [   to local file] filename  [New file] 
   [<  IMAGE retrieve of number.NLS; started]
   [<  transfer completed]
   [*] DISC 
   [*] QUIT 

   [@] COP  [] file  [] LPT:  [OK] 

SENDING A MESSAGE BY TELNET, FTP, OR OTHER MAIL SYSTEM

   TELNET by TENEX Users:

      [@] TELNET 
      [User Telnet x.x DATE ...]
      [#] NIC  FTP  [is complete.#]
      [300 OFFICE-1 FTP Server x.xx.x - at DAY DATE TIME]
      MAIL  JEW/RWW  DHC    (pause)
      [350 Type mail, ended by a line with only a "."]
      Re: Title of Message 
      First line of message 
      second line of message    ...etc.
       .    (pause)
      [256 Mail completed successfully]
      <^Z>
      [#] DISC 
      [#] QUIT 

   FTP by TENEX Users:

      [@] FTP 
      [HOST FTP User process x.xx.x]
      [*] CONN  NIC 
      [   Connection opened]
      [*< OFFICE-1 FTP Server x.xx.x - at DAY DATE TIME]
      [*] QUO  MAIL  JEW/DHC RWW 
      [*] (pause) [Type mail, ended by a line with only a "."]
      [*] QUO  Re: Title of Message 
      [*] QUO  First line of message 
      [*] QUO  second line of message    ...etc.
      [*] QUO  .    (pause)
      [*< Mail completed successfully]
      [*] DISC 
      [*] QUIT 



North                                                           [Page 2]

RFC 629                Using the Network Journal              March 1974


   Using Other Mail Systems:

      It is not possible to give a generalized scenario for use with all
      local mail systems.

      The general procedure, to be applied to the local mail system, is
      to supply:

         "NIC" as the host name, and

         Sender's NIC ident / Addressee's NIC ident as user name

   See RFC543, NIC 17777, for more detail on Network Journal.

            [ This RFC was put into machine readable form for entry ]
              [ into the online RFC archives by Alan Ford 12/99  ]



































North                                                           [Page 3]

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

COT関数 コタンジェント

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る