Return to post.me CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / doc / usd / 08.mh

Annotation of 43BSDReno/share/doc/usd/08.mh/post.me, revision 1.1

1.1     ! root        1: .\"    This file is automatically generated.  Do not edit!
        !             2: .SC POST 8
        !             3: .NA
        !             4: post \- deliver a message
        !             5: .SY
        !             6: /usr/new/lib/mh/post 
        !             7: \%[\-alias\ aliasfile]
        !             8: \%[\-filter\ filterfile] \%[\-nofilter]
        !             9: \%[\-format] \%[\-noformat]
        !            10: \%[\-msgid] \%[\-nomsgid]
        !            11: \%[\-verbose] \%[\-noverbose]
        !            12: \%[\-watch] \%[\-nowatch]
        !            13: \%[\-width\ columns]
        !            14: file
        !            15: \%[\-help]
        !            16: .DE
        !            17: \fIPost\fR is the program called by \fIsend\fR\0(1)
        !            18: to deliver the message in \fIfile\fR to local and remote users.
        !            19: In fact, all of the functions attributed to \fIsend\fR
        !            20: on its manual page are performed by \fIpost\fR,
        !            21: with \fIsend\fR acting as a relatively simple preprocessor.
        !            22: Thus, it is \fIpost\fR which parses the various header fields,
        !            23: appends From: and Date: lines,
        !            24: and interacts with the \fISendMail\fR transport system.
        !            25: \fIPost\fR will not normally be called directly by the user.
        !            26: 
        !            27: \fIPost\fR
        !            28: searches the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq, \*(lqFcc:\*(rq, and \*(lqResent\-xxx:\*(rq
        !            29: header lines of
        !            30: the specified message for destination addresses, checks these
        !            31: addresses for validity, and formats them so as to conform to 
        !            32: ARPAnet Internet Message Format protocol,
        !            33: unless the `\-noformat' flag is set.
        !            34: This will normally cause \*(lq@\fIlocal\-site\fR\*(rq to
        !            35: be appended to each local destination address, as well
        !            36: as any local return addresses.  
        !            37: The `\-width\ columns' switch can be used to indicate the preferred length
        !            38: of the header components that contain addresses.
        !            39: 
        !            40: If a \*(lqBcc:\*(rq field is encountered,
        !            41: its addresses will be used for delivery,
        !            42: and the \*(lqBcc:\*(rq field will be removed from the message sent to sighted
        !            43: recipients.
        !            44: The blind recipients will receive an entirely new message with
        !            45: a minimal set of headers.
        !            46: Included in the body of the message will be a copy of the message sent to the
        !            47: sighted recipients.
        !            48: If `\-filter\ filterfile' is specified,
        !            49: then this copy is filtered (re\-formatted)
        !            50: prior to being sent to the blind recipients.
        !            51: 
        !            52: The `\-alias\ aliasfile' switch can be used to specify a file that post should
        !            53: take aliases from.  More than one file can be specified, each being preceded
        !            54: with `\-alias'.
        !            55: In any event,
        !            56: the primary alias file is read first.
        !            57: 
        !            58: The `\-msgid' switch indicates that
        !            59: a \*(lqMessage\-ID:\*(rq or \*(lqResent\-Message\-ID:\*(rq
        !            60: field should be added to the header.
        !            61: 
        !            62: The `\-verbose' switch indicates that the user should be informed of each
        !            63: step of the posting/filing process.
        !            64: 
        !            65: The `\-watch' switch indicates that the user would like to watch the transport
        !            66: system's handling of the message (e.g., local and \*(lqfast\*(rq delivery).
        !            67: 
        !            68: \fIPost\fR consults the environment variable \fB$SIGNATURE\fR to
        !            69: determine the sender's personal name in constructing the \*(lqFrom:\*(rq line
        !            70: of the message.
        !            71: .Fi
        !            72: ^/usr/new/lib/mh/mtstailor~^tailor file
        !            73: ^/usr/new/mh/refile~^Program to process Fcc:s
        !            74: ^/usr/new/lib/mh/mhl~^Program to process Bcc:s
        !            75: ^/usr/new/lib/mh/MailAliases~^Primary alias file
        !            76: .Pr
        !            77: \fIpost\fR does \fBNOT\fR consult the user's \&.mh\(ruprofile
        !            78: .Sa
        !            79: \fIStandard for the Format of ARPA Internet Text Messages\fR (aka RFC\-822),
        !            80: .br
        !            81: mhmail(1), send(1), mh\-mail(5), mh\-alias(5)
        !            82: .De
        !            83: `\-alias /usr/new/lib/mh/MailAliases'
        !            84: .Ds
        !            85: `\-format'
        !            86: .Ds
        !            87: `\-nomsgid'
        !            88: .Ds
        !            89: `\-noverbose'
        !            90: .Ds
        !            91: '\-nowatch'
        !            92: .Ds
        !            93: `\-width\ 72'
        !            94: .Ds
        !            95: `\-nofilter'
        !            96: .Co
        !            97: None
        !            98: .Bu
        !            99: \*(lqReply\-To:\*(rq fields are allowed to have groups in them according to the
        !           100: 822 specification,
        !           101: but \fIpost\fR won't let you use them.
        !           102: .En

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