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
132 will automatically place a \*(lqFrom:\*(rq line in the message draft.
133 There are two ways to override this behavior, however.
134 Note that they apply equally to \*(lqResent\-From:\*(rq lines in messages sent
138 The first way is to supply a \*(lqSender:\*(rq line. The value of this
139 field will be used as the originating mailbox identity when submitting the
140 message to the mail transport system. If multiple addresses are
141 given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq line is
143 If an \*(lqEnvelope-From:\*(rq line is supplied when multiple addresses
144 are given in the \*(lqFrom:\*(rq line, a \*(lqSender:\*(rq header will
145 be generated using the value of the \*(lqEnvelope-From:\*(rq line,
147 the \*(lqEnvelope-From:\*(rq line is not blank.
149 The second way is to supply a \*(lqEnvelope-From:\*(rq line. The value
150 of this field will be used as the originating mailbox identity when
151 submitting the message to the mail transport system. This will override
152 both the value of the \*(lqFrom:\*(rq line and a \*(lqSender:\*(rq line
153 (if one is supplied). The \*(lqEnvelope-From:\*(rq line is allowed to
154 have a blank value; if the value is blank, then the mail transport system
155 will be instructed to not send any bounces in response to the message.
156 Not all mail transport systems support this feature.
158 If nmh is using the SMTP MTA, the
162 switches can be used to override the default mail server (defined by the
170 has been compiled with SASL support, the
174 switches will enable and disable
175 the use of SASL authentication with the SMTP MTA. Depending on the
176 SASL mechanism used, this may require an additional password prompt from the
178 .RI \*(lq \&.netrc \*(rq
179 file can be used to store this password).
181 switch can be used to select a particular SASL mechanism,
184 switch can be used to select a authorization userid
185 to provide to SASL other than the default.
187 If SASL authentication is successful,
189 will attempt to negotiate a security layer for session encryption.
190 Encrypted data is labelled with `(sasl-encrypted)' and `(sasl-decrypted)' when
191 viewing the SMTP transaction with the
195 switch can be used to select the maximum value of the Security Strength Factor.
196 This is an integer value and the exact meaning of this value depends on the
197 underlying SASL mechanism. A value of 0 disables encryption.
201 has been compiled with TLS support, the
205 switches will require and disable the negotiation of TLS support when
207 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
208 `(tls-decrypted)' when viewing the SMTP transction with the
215 .ta \w'%etcdir%/ExtraBigFileName 'u
216 ^%etcdir%/mts.conf~^nmh mts configuration file
217 ^%etcdir%/MailAliases~^global nmh alias file
218 ^%bindir%/refile~^Program to process Fcc:s
219 ^%libdir%/mhl~^Program to process Bcc:s
222 .SH "PROFILE COMPONENTS"
230 mhmail(1), send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5),
231 .I "Standard for the Format of ARPA Internet Text Messages"
236 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
242 .RB ` "\-width\ 72" '
250 \*(lqReply\-To:\*(rq fields are allowed to have groups in them according
251 to the 822 specification, but
253 won't let you use them.
projects / mmh / blob