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 ]
44 .IR header-field-name ]
48 will cause each of the specified files to be delivered
49 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
50 \*(lqBcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
52 is re\-distributing a message, as invoked from
55 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
62 delivery of the messages, although this can be changed by defining the
64 profile component. Most of the features attributed to
66 are actually performed by
74 option, the draft is scanned for a header whose field name matches the
76 .IR header-field-name .
77 The draft is converted to a MIME message if one or more matches are found.
78 This conversion occurs before all other processing.
80 The first part of the MIME message is the draft body if that body contains
81 any non-blank characters.
82 The body of each header field whose name matches the
84 is interpreted as a file name, and each file named is included as a separate
85 part in the MIME message.
87 For file names with dot suffixes, the context is scanned for a
89 entry for that suffix.
90 The content-type for the part is taken from that context entry if a match is
92 If no match is found or the file does not have a dot suffix, the content-type
93 is text/plain if the file contains only ASCII characters or application/octet-stream
94 if it contains characters outside of the ASCII range.
96 Each part contains a name attribute that is the last component of the path name.
99 attribute containing the file mode accompanies each part.
100 Finally, a description attribute is generated by running the
108 will detach itself from the user's
109 terminal and perform its actions in the background. If
111 and the draft can't be sent, then an error message will be sent (using
112 the mailproc) back to the user. If
114 is given, then a copy
115 of the draft will be attached to this failure notice. Using
119 in the background because the output is
120 trapped and analyzed by
127 will indicate the interactions
128 occurring with the transport system, prior to actual delivery.
133 will monitor the delivery of local
134 and network mail. Hence, by specifying both switches, a large detail
135 of information can be gathered about each step of the message's entry
136 into the transport system.
147 draft folder facility. This is an advanced (and highly
148 useful) feature. Consult the
157 will split the draft into one
158 or more partial messages prior to sending. This makes use of the
166 then this switch is ignored\0--\0it makes
167 no sense to redistribute a message in this fashion. Sometimes you want
169 to pause after posting a partial message. This is usually
170 the case when you are running
172 and expect to generate a
173 lot of partial messages. The argument to
176 to pause between postings.
181 argument will query whether the draft
182 is the intended file, whereas
184 will suppress this question.
185 Once the transport system has successfully accepted custody of the
186 message, the file will be renamed with a leading comma, which allows
187 it to be retrieved until the next draft message is sent. If there are
188 errors in the formatting of the message,
191 (hopefully) helpful error message.
193 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
194 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
195 sent to sighted recipients. The blind recipients will receive an entirely
196 new message with a minimal set of headers. Included in the body of the
197 message will be a copy of the message sent to the sighted recipients.
201 is specified, then this copy is filtered
204 prior to being sent to the blind recipients.
205 Alternately, if you specify the
210 use the MIME rules for encapsulation.
212 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
213 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
214 If the environment variable
216 is set, then its value
217 is used as your personal name when constructing the \*(lqFrom:\*(rq
218 line of the message. If this environment variable is not set, then
220 will consult the profile entry \*(lqSignature\*(rq for
224 is specified, then a \*(lqMessage\-ID:\*(rq field will also
225 be added to the message.
229 is re\-distributing a message (when invoked by
231 then \*(lqResent\-\*(rq will be prepended to each of these
232 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
233 If the message already contains a \*(lqFrom:\*(rq field, then a
234 \*(lqSender: user@local\*(rq field will be added as well. (An already
235 existing \*(lqSender:\*(rq field is an error!)
239 switch, each of the entries in the \*(lqTo:\*(rq
240 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
241 format entries. This standard format is designed to be usable by all
242 of the message handlers on the various systems around the Internet.
245 is given, then headers are output exactly as they appear
246 in the message draft.
248 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
249 to the specified folder for the sender in the format in which it will
250 appear to any non\-Bcc receivers of the message. That is, it will have
251 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
252 will be removed from all outgoing copies of the message.
257 switch, the user can direct
259 as to how long it should make header lines containing addresses.
263 has been compiled with SASL support, the
266 the use of SASL authentication with the SMTP MTA. Depending on the
267 SASL mechanism used, this may require an additional password prompt from the
269 .RI \*(lq \&.netrc \*(rq
270 file can be used to store this password).
272 switch can be used to select a particular SASL mechanism,
275 switch can be used to select a authorization userid
276 to provide to SASL other than the default.
278 Currently SASL security layers are not supported for SMTP.
281 will always negotiate an unencrypted connection. This means that while the SMTP
282 authentication can be encrypted, the subsequent data stream can not. This is in
285 POP3 SASL support, where encryption is supported for both the
286 authentication and the data stream.
288 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
289 additional alias files given by the
293 read (more than one file, each preceded by
298 for more information.
303 .ta \w'%etcdir%/ExtraBigFileName 'u
304 ^$HOME/\&.mh\(ruprofile~^The user profile
307 .SH "PROFILE COMPONENTS"
311 .ta \w'ExtraBigProfileName 'u
312 ^Path:~^To determine the user's nmh directory
313 ^Draft\-Folder:~^To find the default draft\-folder
314 ^Aliasfile:~^For a default alias file
315 ^Signature:~^To determine the user's mail signature
316 ^mailproc:~^Program to post failure notices
317 ^postproc:~^Program to post the message
321 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
325 .RB ` file "' defaults to <mh\-dir>/draft"
326 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
327 .RB ` \-nodraftfolder '
336 .RB ` "\-width\ 72" '
343 Under some configurations, it is not possible to monitor the mail delivery
346 is a no-op on those systems.
351 doesn't work correctly.