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 ]
24 .IR smtp " | " sendmail/smtp " | " sendmail/pipe ]
45 is the default program called by
50 to local and remote users. In fact, most of
51 the features attributed to
53 in its manual page are performed by
57 acting as a relatively simple preprocessor.
60 which parses the various header fields, appends a
61 \*(lqDate:\*(rq line, and interacts with the mail transport system.
63 will not normally be called directly by the user.
66 searches the \*(lqTo:\*(rq, \*(lqcc:\*(rq, \*(lqBcc:\*(rq,
67 \*(lqFcc:\*(rq, and \*(lqResent\-xxx:\*(rq header lines of the specified
68 message for destination addresses, checks these addresses for validity,
69 and formats them so as to conform to ARPAnet Internet Message Format
72 flag is set. This will normally cause
73 \*(lq@\fIlocal\-site\fR\*(rq to be appended to each local destination
74 address, as well as any local return addresses. The
77 switch can be used to indicate the preferred length of the header
78 components that contain addresses.
80 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
81 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
82 sent to sighted recipients. The blind recipients will receive an entirely
83 new message with a minimal set of headers. Included in the body of the
84 message will be a copy of the message sent to the sighted recipients.
88 is specified, then this copy is filtered
91 prior to being sent to the blind recipients.
97 the MIME rules for encapsulation.
102 switch can be used to specify a file that post
103 should take aliases from. More than one file can be specified, each
106 In any event, the primary alias file is
111 switch indicates that a \*(lqMessage\-ID:\*(rq or
112 \*(lqResent\-Message\-ID:\*(rq field should be added to the header.
116 switch indicates that the user should be informed of
117 each step of the posting/filing process.
121 switch indicates that the user would like to watch the
122 transport system's handling of the message (e.g., local and \*(lqfast\*(rq
125 Under normal circumstances,
127 uses the \*(lqFrom:\*(rq line in the message draft as the identity of
128 the the originating mailbox. A \*(lqFrom:\*(rq line is required in
129 all message draft. By default the message composition utilities such
135 will automatically place a \*(lqFrom:\*(rq line in the message draft.
136 There are two ways to override this behavior, however.
137 Note that they apply equally to \*(lqResent\-From:\*(rq lines in messages sent
141 The first way is to supply a \*(lqSender:\*(rq line. The value of this
142 field will be used as the originating mailbox identity when submitting the
143 message to the mail transport system. If multiple addresses are
144 given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq line is
146 If an \*(lqEnvelope-From:\*(rq line is supplied when multiple addresses
147 are given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq header will
148 be generated using the value of the \*(lqEnvelope-From:\*(rq line,
150 the \*(lqEnvelope-From:\*(rq line is not blank.
152 The second way is to supply a \*(lqEnvelope-From:\*(rq line. The value
153 of this field will be used as the originating mailbox identity when
154 submitting the message to the mail transport system. This will override
155 both the value of the \*(lqFrom:\*(rq line and a \*(lqSender:\*(rq line
156 (if one is supplied). The \*(lqEnvelope-From:\*(rq line is allowed to
157 have a blank value; if the value is blank, then the mail transport system
158 will be instructed to not send any bounces in response to the message.
159 Not all mail transport systems support this feature.
161 The mail transport system default is provided in
163 but can be overriiden here with the
167 If nmh is using the SMTP MTA, the
171 switches can be used to override the default mail server (defined by the
179 has been compiled with SASL support, the
183 switches will enable and disable
184 the use of SASL authentication with the SMTP MTA. Depending on the
185 SASL mechanism used, this may require an additional password prompt from the
187 .RI \*(lq \&.netrc \*(rq
188 file can be used to store this password).
190 switch can be used to select a particular SASL mechanism,
193 switch can be used to select a authorization userid
194 to provide to SASL other than the default.
196 If SASL authentication is successful,
198 will attempt to negotiate a security layer for session encryption.
199 Encrypted data is labelled with `(sasl-encrypted)' and `(sasl-decrypted)' when
200 viewing the SMTP transaction with the
204 switch can be used to select the maximum value of the Security Strength Factor.
205 This is an integer value and the exact meaning of this value depends on the
206 underlying SASL mechanism. A value of 0 disables encryption.
210 has been compiled with TLS support, the
214 switches will require and disable the negotiation of TLS support when
216 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
217 `(tls-decrypted)' when viewing the SMTP transction with the
224 .ta \w'%etcdir%/ExtraBigFileName 'u
225 ^%etcdir%/mts.conf~^nmh mts configuration file
226 ^%etcdir%/MailAliases~^global nmh alias file
227 ^%bindir%/refile~^Program to process Fcc:s
228 ^%libdir%/mhl~^Program to process Bcc:s
231 .SH "PROFILE COMPONENTS"
239 mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
240 .I "Standard for the Format of ARPA Internet Text Messages"
245 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
251 .RB ` "\-width\ 72" '
259 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
260 to the 822 specification, but
262 won't let you use them.