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