4 .TH POST %manext8% "%nmhdate%" MH.6.8 [%nmhversion%]
6 post \- deliver a message
16 .RB [ \-format " | " \-noformat ]
17 .RB [ \-mime " | " \-nomime ]
18 .RB [ \-msgid " | " \-nomsgid ]
19 .RB [ \-verbose " | " \-noverbose ]
20 .RB [ \-watch " | " \-nowatch ]
43 is the default program called by
48 to local and remote users. In fact, most of
49 the features attributed to
51 in its manual page are performed by
55 acting as a relatively simple preprocessor.
58 which parses the various header fields, appends a
59 \*(lqDate:\*(rq line, and interacts with the mail transport system.
61 will not normally be called directly by the user.
64 searches the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq,
65 \*(lqFcc:\*(rq, and \*(lqResent\-xxx:\*(rq header lines of the specified
66 message for destination addresses, checks these addresses for validity,
67 and formats them so as to conform to ARPAnet Internet Message Format
70 flag is set. This will normally cause
71 \*(lq@\fIlocal\-site\fR\*(rq to be appended to each local destination
72 address, as well as any local return addresses. The
75 switch can be used to indicate the preferred length of the header
76 components that contain addresses.
78 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
79 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
80 sent to sighted recipients. The blind recipients will receive an entirely
81 new message with a minimal set of headers. Included in the body of the
82 message will be a copy of the message sent to the sighted recipients.
86 is specified, then this copy is filtered
89 prior to being sent to the blind recipients.
95 the MIME rules for encapsulation.
100 switch can be used to specify a file that post
101 should take aliases from. More than one file can be specified, each
104 In any event, the primary alias file is
109 switch indicates that a \*(lqMessage\-ID:\*(rq or
110 \*(lqResent\-Message\-ID:\*(rq field should be added to the header.
114 switch indicates that the user should be informed of
115 each step of the posting/filing process.
119 switch indicates that the user would like to watch the
120 transport system's handling of the message (e.g., local and \*(lqfast\*(rq
123 Under normal circumstances,
125 uses the \*(lqFrom:\*(rq line in the message draft as the identity of
126 the the originating mailbox. A \*(lqFrom:\*(rq line is required in
127 all message draft. By default the message composition utilities such
133 will automatically place a \*(lqFrom:\*(rq line in the message draft.
134 There are two ways to override this behavior, however.
135 Note that they apply equally to \*(lqResent\-From:\*(rq lines in messages sent
139 The first way is to supply a \*(lqSender:\*(rq line. The value of this
140 field will be used as the originating mailbox identity when submitting the
141 message to the mail transport system. If multiple addresses are
142 given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq line is
144 If an \*(lqEnvelope-From:\*(rq line is supplied when multiple addresses
145 are given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq header will
146 be generated using the value of the \*(lqEnvelope-From:\*(rq line,
148 the \*(lqEnvelope-From:\*(rq line is not blank.
150 The second way is to supply a \*(lqEnvelope-From:\*(rq line. The value
151 of this field will be used as the originating mailbox identity when
152 submitting the message to the mail transport system. This will override
153 both the value of the \*(lqFrom:\*(rq line and a \*(lqSender:\*(rq line
154 (if one is supplied). The \*(lqEnvelope-From:\*(rq line is allowed to
155 have a blank value; if the value is blank, then the mail transport system
156 will be instructed to not send any bounces in response to the message.
157 Not all mail transport systems support this feature.
159 If nmh is using the SMTP MTA, the
163 switches can be used to override the default mail server (defined by the
171 has been compiled with SASL support, the
175 switches will enable and disable
176 the use of SASL authentication with the SMTP MTA. Depending on the
177 SASL mechanism used, this may require an additional password prompt from the
179 .RI \*(lq \&.netrc \*(rq
180 file can be used to store this password).
182 switch can be used to select a particular SASL mechanism,
185 switch can be used to select a authorization userid
186 to provide to SASL other than the default.
188 If SASL authentication is successful,
190 will attempt to negotiate a security layer for session encryption.
191 Encrypted data is labelled with `(sasl-encrypted)' and `(sasl-decrypted)' when
192 viewing the SMTP transaction with the
196 switch can be used to select the maximum value of the Security Strength Factor.
197 This is an integer value and the exact meaning of this value depends on the
198 underlying SASL mechanism. A value of 0 disables encryption.
202 has been compiled with TLS support, the
206 switches will require and disable the negotiation of TLS support when
208 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
209 `(tls-decrypted)' when viewing the SMTP transction with the
216 .ta \w'%etcdir%/ExtraBigFileName 'u
217 ^%etcdir%/mts.conf~^nmh mts configuration file
218 ^%etcdir%/MailAliases~^global nmh alias file
219 ^%bindir%/refile~^Program to process Fcc:s
220 ^%libdir%/mhl~^Program to process Bcc:s
223 .SH "PROFILE COMPONENTS"
231 mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
232 .I "Standard for the Format of ARPA Internet Text Messages"
237 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
243 .RB ` "\-width\ 72" '
251 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
252 to the 822 specification, but
254 won't let you use them.
projects / mmh / blob