Return to askarpa CVS log

Up to [Research Unix] / researchv10no / lbin / Mail / manual

Annotation of researchv10no/lbin/Mail/manual/askarpa, revision 1.1

1.1     ! root        1: .sh 2 "Message headers"
        !             2: .pp
        !             3: In section 2, we saw that the
        !             4: .b reply
        !             5: command uses the
        !             6: .q "To:"
        !             7: and
        !             8: .q "Cc:"
        !             9: fields of the original message to construct the recipient list.
        !            10: In section 3.1, we saw the ~s, ~t, and ~c escapes for modifying
        !            11: the
        !            12: .q "Subject:"
        !            13: .q "To:"
        !            14: and
        !            15: .q "Cc:"
        !            16: fields.  In addition to these headers,
        !            17: .i Mail
        !            18: allows, but does not use, other header fields which may be defined
        !            19: by, say, the ARPANET message standard.  Any header field, whether
        !            20: supported by
        !            21: .i Mail
        !            22: or not, can be modified using the ~e or ~v escape.  The headers
        !            23: are present in the message written to the editor and are recovered
        !            24: after the editor finishes.
        !            25: .pp
        !            26: If you desire to send messages using a fuller complement of the
        !            27: ARPANET standard headers, you can set the binary
        !            28: .q "askarpa"
        !            29: option:
        !            30: .(l
        !            31: set askarpa
        !            32: .)L
        !            33: This will cause
        !            34: .i Mail
        !            35: to supply correct header fields for the
        !            36: .q "Date:"
        !            37: .q "Sender:"
        !            38: and
        !            39: .q "Message-ID:"
        !            40: fields and to prompt you for the
        !            41: .q "Subject:"
        !            42: .q "Reply-To:"
        !            43: .q "To:"
        !            44: .q "Cc:"
        !            45: .q "Comment:"
        !            46: and
        !            47: .q "In-Reply-To:"
        !            48: fields.  For example, we might construct the following headers using
        !            49: .q askarpa"
        !            50: .(l
        !            51: Date: 18 Nov 1979 2320-PDT
        !            52: From: Kurt at Berkeley
        !            53: Subject: An example set of headers
        !            54: Sender: Otherperson at Berkeley
        !            55: Reply-To: vax.kurt at Berkeley
        !            56: To: dave george at bbna
        !            57: Cc: Al Newman at mad-host
        !            58: Comment: This is much too complex
        !            59: In-Reply-To: Your questions about headers
        !            60: Message-ID: 32760.kurt.CSVAX.2320
        !            61: .)L
        !            62: The format and meaning of these fields is dictated by the ARPANET
        !            63: message standard, which is given in the ARPANET Protocol Handbook.
        !            64: .pp
        !            65: When
        !            66: .i Mail
        !            67: prompts for a field, you can type in a longer than line width field
        !            68: by ending each line to be continued with a \e.
        !            69: .i Mail
        !            70: indicates continuations by indenting the following lines 4 spaces.
        !            71: For example:
        !            72: .(l
        !            73: Subject: The solution to a difficult and important \e
        !            74:     problem has finally presented itself
        !            75: .)L
        !            76: The \e does not actually appear in the real message \*-
        !            77: .i Mail
        !            78: will split the header fields so that they will fit on 72 character lines.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.