5 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
19 .RB [ \-nodraftfolder ]
23 .RB [ \-format " | " \-noformat ]
24 .RB [ \-forward " | " \-noforward ]
25 .RB [ \-mime " | " \-nomime ]
26 .RB [ \-msgid " | " \-nomsgid ]
27 .RB [ \-push " | " \-nopush ]
30 .RB [ \-verbose " | " \-noverbose ]
31 .RB [ \-watch " | " \-nowatch ]
46 will cause each of the specified files to be delivered
47 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
48 \*(lqBcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
50 is re\-distributing a message, as invoked from
53 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
60 delivery of the messages, although this can be changed by defining the
62 profile component. Most of the features attributed to
64 are actually performed by
71 will detach itself from the user's
72 terminal and perform its actions in the background. If
74 and the draft can't be sent, then an error message will be sent (using
75 the mailproc) back to the user. If
78 of the draft will be attached to this failure notice. Using
82 in the background because the output is
83 trapped and analyzed by
90 will indicate the interactions
91 occurring with the transport system, prior to actual delivery.
96 will monitor the delivery of local
97 and network mail. Hence, by specifying both switches, a large detail
98 of information can be gathered about each step of the message's entry
99 into the transport system.
110 draft folder facility. This is an advanced (and highly
111 useful) feature. Consult the
120 will split the draft into one
121 or more partial messages prior to sending. This makes use of the
129 then this switch is ignored\0--\0it makes
130 no sense to redistribute a message in this fashion. Sometimes you want
132 to pause after posting a partial message. This is usually
133 the case when you are running
135 and expect to generate a
136 lot of partial messages. The argument to
139 to pause between postings.
144 argument will query whether the draft
145 is the intended file, whereas
147 will suppress this question.
148 Once the transport system has successfully accepted custody of the
149 message, the file will be renamed with a leading comma, which allows
150 it to be retrieved until the next draft message is sent. If there are
151 errors in the formatting of the message,
154 (hopefully) helpful error message.
156 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
157 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
158 sent to sighted recipients. The blind recipients will receive an entirely
159 new message with a minimal set of headers. Included in the body of the
160 message will be a copy of the message sent to the sighted recipients.
164 is specified, then this copy is filtered
167 prior to being sent to the blind recipients.
168 Alternately, if you specify the
173 use the MIME rules for encapsulation.
175 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
176 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
177 If the environment variable
179 is set, then its value
180 is used as your personal name when constructing the \*(lqFrom:\*(rq
181 line of the message. If this environment variable is not set, then
183 will consult the profile entry \*(lqSignature\*(rq for
187 is specified, then a \*(lqMessage\-ID:\*(rq field will also
188 be added to the message.
192 is re\-distributing a message (when invoked by
194 then \*(lqResent\-\*(rq will be prepended to each of these
195 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
196 If the message already contains a \*(lqFrom:\*(rq field, then a
197 \*(lqSender: user@local\*(rq field will be added as well. (An already
198 existing \*(lqSender:\*(rq field is an error!)
202 switch, each of the entries in the \*(lqTo:\*(rq
203 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
204 format entries. This standard format is designed to be usable by all
205 of the message handlers on the various systems around the Internet.
208 is given, then headers are output exactly as they appear
209 in the message draft.
211 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
212 to the specified folder for the sender in the format in which it will
213 appear to any non\-Bcc receivers of the message. That is, it will have
214 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
215 will be removed from all outgoing copies of the message.
220 switch, the user can direct
222 as to how long it should make header lines containing addresses.
226 has been compiled with SASL support, the
229 the use of SASL authentication with the SMTP MTA. Depending on the
230 SASL mechanism used, this may require an additional password prompt from the
232 .RI \*(lq \&.netrc \*(rq
233 file can be used to store this password).
235 switch can be used to select a particular SASL mechanism,
238 switch can be used to select a authorization userid
239 to provide to SASL other than the default.
241 Currently SASL security layers are not supported for SMTP.
244 will always negotiate an unencrypted connection. This means that while the SMTP
245 authentication can be encrypted, the subsequent data stream can not. This is in
248 POP3 SASL support, where encryption is supported for both the
249 authentication and the data stream.
251 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
252 additional alias files given by the
256 read (more than one file, each preceded by
261 for more information.
266 .ta \w'%etcdir%/ExtraBigFileName 'u
267 ^$HOME/\&.mh\(ruprofile~^The user profile
270 .SH "PROFILE COMPONENTS"
274 .ta \w'ExtraBigProfileName 'u
275 ^Path:~^To determine the user's nmh directory
276 ^Draft\-Folder:~^To find the default draft\-folder
277 ^Aliasfile:~^For a default alias file
278 ^Signature:~^To determine the user's mail signature
279 ^mailproc:~^Program to post failure notices
280 ^postproc:~^Program to post the message
284 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
288 .RB ` file "' defaults to <mh\-dir>/draft"
289 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
290 .RB ` \-nodraftfolder '
299 .RB ` "\-width\ 72" '
306 Under some configurations, it is not possible to monitor the mail delivery
309 is a no-op on those systems.
314 doesn't work correctly.