rfc724.txt

RFC 相关的技术文档

           of  the  message  who are to remain hidden from the primary
           and secondary  recipients.   Some  systems  may  choose  to
           include   the   text  of  the  "Bcc:"  field  only  in  the
           author(s)'s copy, while others may include it in  the  text
           sent to all those indicated in the "Bcc:" list.

        4) Fcc:

           This field contains the identity of any  message  files  in
           which  copies  of  this  message  are  being  placed by the
           originator.  Note that the presence of this field does  NOT
           guarantee  long-term  availability of the message in any of
           the indicated files.




     II. Standard for the Format of Messages                      / 23
      C. Semantics
      2. Reference Specification Fields



     2. REFERENCE SPECIFICATION FIELDS

     a. Message-Id:

        This field contains a  unique  identifier  (the  <phrase>)  to
        refer  to this version of this message.  The uniqueness of the
        message  identifier  is  guaranteed  by   each   host.    This
        identifier  is  intended  to  be  machine  readable,  and  not
        necessarily meaningful to humans.  A  message-id  pertains  to
        exactly  one instantiation of a particular message; subsequent
        revisions to the message should receive new message-id's.

     b. In-Reply-To:

        The contents of this field  identify  previous  correspondence
        which  this  message answers.  If message identifiers are used
        in this field, they should be enclosed in angle brackets (<>).

     c. References:

        The contents of this field identify other correspondence which
        this  message  references.   If  message identifiers are used,
        they should be enclosed in angle brackets (<>).

     d. Keywords:

        This field contains keywords or phrases, separated by commas.


     3. OTHER FIELDS AND SYNTACTIC ITEMS

     a. Subject:

        The  "subject:"  field  is  intended  to   provide   as   much
        information  as  necessary to adequately summarize or indicate
        the nature of the message.

     b. Comments:

        Permits  adding  text  comments  onto  the   message   without
        disturbing the contents of the message's body.




     II. Standard for the Format of Messages                      / 24
      C. Semantics
      4. Dates



     4. DATES

        It is recommended that,  because  of  differing  international
        interpretations,  the  <string-day>  option be used instead of
        the <slash-day> option in the specification of a <day>.

        If included, <day-of-week> must be  the  day  implied  by  the
        <date> specification.

        <Time-zones> allow reference to Greenwich and to each  of  the
        zones  in  the  United  States.  The zone references beginning
        with "A" are for Atlantic time which are one hour faster  than
        the  corresponding Eastern times.  "Y" indicates Yukon time in
        Alaska, which  is  one  hour  slower  than  the  corresponding
        Pacific times, and "H" indicates Hawaiian times, which are two
        hours slower.



     II. Standard for the Format of Messages                      / 25
      D. Examples






     D. EXAMPLES


     1. ADDRESSES

     a. Alfred E. Newman <Newman at BBN-TENEXA>
        Newman@BBN-TENEXA

        These  two  "Alfred  E.   Newman"  examples   have   identical
        semantics,  as far as the operation of the local host's mailer
        and the remote host's FTP server are concerned.  In the  first
        example,  the "Alfred E.  Newman" is ignored by the mailer, as
        "Newman at BBN-TENEXA"  completely  specifies  the  recipient.
        The  second  example contains no superfluous information, and,
        again, "Newman@BBN-TENEXA" is the intended recipient.

     b. Al Newman at BBN-TENEXA

        This is identical with "Al Newman<Al Newman  at  BBN-TENEXA>."
        That is, the full <phrase>, "Al Newman", is passed to the  FTP
        server.   Note  that  not  all  FTP  servers accept multi-word
        identifiers; and some that do accept them will treat each word
        as  a  different addressee (in this case, attempting to send a
        copy of the message to "Al" and a copy to "Newman").

     c. "George Lovell, Ted Hackle" <Shared-Mailbox at Office-1>

        This form might be used to indicate that a single  mailbox  is
        shared  by several users.  The quoted string is ignored by the
        originating host's mailer,  as  "Shared-Mailbox  at  Office-1"
        completely specifies the destination mailbox.

     d. Wilt (the Stilt) Chamberlain at NBA

        The "(the Stilt)" is a comment, which is NOT included  in  the
        destination mailbox address handed to the originating system's
        mailer.  The address is the string  "Wilt  Chamberlain",  with
        exactly  one  space  between the first and second words.  (The
        quotation marks are not included.)




     II. Standard for the Format of Messages                      / 26
      D. Examples




     2. ADDRESS LISTS

            Gourmets:  Pompous Person <WhoZiWhatZit at Cordon-Bleu>,
                       Cooks:  Childs at WGBH, Galloping Gourmet at
                               ANT (Australian National Television);
                       Wine Lovers:  Drunk at Discount-Liquors,
                                     Port at Portugal;;,
            Jones at SEA

        This group list example points out the use  of  comments,  the
        nesting  of  groups,  and  the mixing of addresses and groups.
        Note that the two consecutive semi-colons  preceding "Jones at
        SEA" mean that Jones is NOT a member of the Gourmets group.


     3. ORIGINATOR ITEMS

     a. George Jones logs into his Host as  "Jones".   He  sends  mail
        himself.

            From:  Jones at Host
        or
            From:  George Jones <Jones at Host>

     b. George Jones logs in as Jones on his Host.  His secretary, who
        logs  in  as  Secy  on  her  Host  (SHost) sends mail for him.
        Replies to the mail should go to George, of course.

            From:    George Jones <Jones at Host>
            Sender:  Secy at SHost

     c. George Jones logs in as Group at Host.  He sends mail himself;
        replies should go to the Group mailbox.

            From:  George Jones <Group at Host>

     d. George Jones' secretary sends mail for George in his  capacity
        as a member of Group while logged in as Secy at Host.  Replies
        should go to Group.

            From:   George Jones<Group at Host>
            Sender: Secy at Host

        Note that there need not be a space between  "Jones"  and  the
        "<",  but  adding a space enhances readability (as is the case
        in other examples).

     e. George Jones asks his secretary  (Secy  at  Host)  to  send  a
        message  for  him  in  his  capacity  as  Group.  He wants his
        secretary to handle all replies.



     II. Standard for the Format of Messages                      / 27
      D. Examples




            From:     George Jones <Group at Host>
            Sender:   Secy at Host
            Reply-to: Secy at Host

     f. A non-ARPANET user friend  of  George's,  Sarah,  is  visting.
        George's  secretary  sends  some  mail to a friend of Sarah in
        computer-land.  Replies should go to George, whose mailbox  is
        Jones at Host.

            From:     Sarah Friendly
            Sender:   Secy at Host
            Reply-to: Jones at Host

     g. George is a member of a committee.   He  wishes  to  have  any
        replies to his message go to all committee members.

            From:     George Jones
            Sender:   Jones at Host
            Reply-To: Big-committee: Jones at Host,
                                     Smith at Other-Host,
                                     Doe at Somewhere-Else;

        Note  that  if  George  had  not  included  himself   in   the
        enumeration  of  Big-committee,  he  would  not  have gotten a
        reply; the presence of the "Reply-to:"  field  SUPERSEDES  the
        sending of a reply to the person named in the "From:" field.

     h. (Example of INCORRECT USE)

        George desires a reply to go to his secretary;  therefore  his
        secretary  leaves  his  mailbox address off the "From:" field,
        leaving only  his  name,  which  is  not,  itself,  a  mailbox
        address.

                 From:   George Jones
                 Sender: Secy at SHost

        THIS IS NOT PERMITTED.  Replies are NEVER implicitly  sent  to
        the   "Sender:";  George's  secretary  should  have  used  the
        "Reply-to:" field, or the mail creating program she was  using
        should have forced her to.

     i. George's secretary sends out  a  message  which  was  authored
        jointly by all the members of the "Big-committee".

            From:   Big-committee: Jones at Host,
                                   Smith at Other-Host,
                                   Doe at Somewhere-Else;
            Sender: Secy at SHost



     II. Standard for the Format of Messages                      / 28
      D. Examples




     4. COMPLETE HEADERS

     a. Minimum required:

            Date:  26 August 1976 1429-EDT
            From:  Jones at Host

     b. Using some of the additional fields:

            Date  26 August 1976 1430-EDT
            From:  George Jones<Group at Host>
            Sender: Secy at SHOST
            To:    Al Newman at Mad-Host,
                   Sam Irving at Other-Host
            Message-id:  some string at SHOST

     c. About as complex as you're going to get:

            Date:       27 Aug 1976 0932-PDT
            From:       Ken Davis <KDavis at Other-Host>
            Sender:     KSecy at Other-Host
            Reply-to:   Sam Irving at Other-Host
            Subject:    Re: The Syntax in the RFC
            To:         George Jones <Group at Host>,
                        Al Newman at Mad-Host
            cc:         Tom Softwood <Balsa at Another-Host>,
                        Sam Irving at Other-Host,
                        Standard Distribution:
                         :File:
                           </main/davis/people/standard at Other Host,
                           "<Jones>standard.dist.3" at Tops-20-Host>
            In-Reply-to: <some string at SHOST>
            Message-ID: 4231.629.XYzi-What at Other-Host
            Comment:    Sam is away on business. He asked me to handle
                        his  mail  for  him  today.   He'll be able to
                        provide a more accurate  explanation  tomorrow
                        when he returns.



     III. References







                            III.  REFERENCES


     --- TELNET Protocol Specification.   Network  Information  Center
        No.  18639;  Augmentation  Research  Center, Stanford Research
        Institute: Menlo Park, August 1973.

     Bhushan, A.K.  The File Transfer Protocol.  ARPANET  Request  for
        Comments,  No.   354,  Networ