4 .TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
18 .RB [ \-nodraftfolder ]
22 .RB [ \-format " | " \-noformat ]
23 .RB [ \-forward " | " \-noforward ]
24 .RB [ \-mime " | " \-nomime ]
25 .RB [ \-msgid " | " \-nomsgid ]
26 .RB [ \-push " | " \-nopush ]
29 .RB [ \-verbose " | " \-noverbose ]
30 .RB [ \-watch " | " \-nowatch ]
32 .IR smtp " | " sendmail/smtp " | " sendmail/pipe ]
36 .IR port-name/number ]
55 .IR header-field-name ]
58 .IR 0 " | " 1 " | " 2 ]
62 will cause each of the specified files to be delivered
63 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
64 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
66 is re\-distributing a message, as invoked from
69 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
76 delivery of the messages, although this can be changed by defining the
78 profile component. Most of the features attributed to
80 are actually performed by
84 By default the draft is scanned for a header named
86 The draft is converted to a MIME message if one or more matches are found.
87 This conversion occurs before all other processing. The header name
88 can be changed with the
90 option. This behavior can be disabled completely with the
94 The first part of the MIME message is the draft body if that body contains
95 any non-blank characters.
96 The body of each header field whose name matches the
98 is interpreted as a file name, and each file named is included as a separate
99 part in the MIME message.
101 For file names with dot suffixes, the profile is scanned for a
103 entry for that suffix.
104 The content-type for the part is taken from that profile entry if a match is
105 found. If a match is not found in the user profile, the mhn.defaults
106 profile is scanned next.
107 If no match is found or the file does not have a dot suffix, the content-type
108 is text/plain if the file contains only ASCII characters or application/octet-stream
109 if it contains characters outside of the ASCII range. See
111 for more details and example syntax.
113 Each part contains a name attribute that is the last component of the path name.
116 attribute containing the file mode accompanies each part.
117 Finally, a description attribute is generated by running the
123 option specifies the MIME header field formats: a value of
127 attribute as noted above. A value of
130 suppresses that, puts the file name in the
131 \*(lqContent-Description\*(rq header, and
132 adds a \*(lqContent-Disposition\*(rq header. A value of
136 parameter to the \*(lqContent-Disposition\*(rq header. You can
137 specify one value in your profile, and override it for individual
142 Here are example message part headers, for an attachment, for each of the
148 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
150 Content-Description: ASCII text
153 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
154 Content-Description: VERSION
155 Content-Disposition: attachment; filename="VERSION"
158 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
159 Content-Description: VERSION
160 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
167 will detach itself from the user's
168 terminal and perform its actions in the background. If
170 and the draft can't be sent, then an error message will be sent (using
171 the mailproc) back to the user. If
173 is given, then a copy
174 of the draft will be attached to this failure notice. Using
178 in the background because the output is
179 trapped and analyzed by
186 will indicate the interactions
187 occurring with the transport system, prior to actual delivery.
192 will monitor the delivery of local
193 and network mail. Hence, by specifying both switches, a large detail
194 of information can be gathered about each step of the message's entry
195 into the transport system.
206 draft folder facility. This is an advanced (and highly
207 useful) feature. Consult the
216 will split the draft into one
217 or more partial messages prior to sending. This makes use of the
225 then this switch is ignored\0--\0it makes
226 no sense to redistribute a message in this fashion. Sometimes you want
228 to pause after posting a partial message. This is usually
229 the case when you are running
231 and expect to generate a
232 lot of partial messages. The argument to
235 to pause between postings.
240 argument will query whether the draft
241 is the intended file, whereas
243 will suppress this question.
244 Once the transport system has successfully accepted custody of the
245 message, the file will be renamed with a site-dependent prefix
246 (usually a comma), which allows
247 it to be retrieved until the next draft message is sent. If there are
248 errors in the formatting of the message,
251 (hopefully) helpful error message.
253 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
254 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
255 sent to sighted recipients. The blind recipients will receive an entirely
256 new message with a minimal set of headers. Included in the body of the
257 message will be a copy of the message sent to the sighted recipients.
259 If a \*(lqDcc:\*(rq field is encountered and the
261 mail transport method is not in use, its addresses will be used for
262 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
263 blind recipients will receive the same message sent to the sighted
264 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
265 explicit indication that they have received a \*(lqblind copy\*(rq.
266 This can cause blind recipients to
267 inadvertently reply to all of the sighted recipients of the
268 original message, revealing that they received a blind copy.
269 On the other hand, since a normal reply to a message sent
270 via a \*(lqBcc:\*(rq field
271 will generate a reply only to the sender of the original message,
272 it takes extra effort in most mailers to reply to the included
273 message, and so would usually only be done deliberately, rather
279 is specified, then this copy is filtered
282 prior to being sent to the blind recipients.
283 Alternately, if you specify the
288 use the MIME rules for encapsulation.
290 Prior to sending the message, the \*(lqDate:\ now\*(rq field will be appended to the headers in the message.
293 is specified, then a \*(lqMessage\-ID:\*(rq field will also
294 be added to the message.
298 is re\-distributing a message (when invoked by
300 then \*(lqResent\-\*(rq will be prepended to each of these
301 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
303 A \*(lqFrom:\*(rq field is required for all outgoing messages. Multiple
304 addresses are permitted in the \*(lqFrom:\*(rq field, but a \*(lqSender:\*(rq
305 field is required in this case. Otherwise a \*(lqSender:\*(rq field
308 If a message with multiple \*(lqFrom:\*(rq
311 include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
312 field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
313 a \*(lqSender:\*(rq field.
315 When using SMTP for mail submission, the envelope\-from used for the SMTP
316 transaction is derived from the \*(lqEnvelope\-From:\*(rq field.
317 If no \*(lqEnvelope\-From:\*(rq field is present, the \*(lqSender:\*(rq
318 field is used. If neither the \*(lqEnvelope\-From:\*(rq nor the
319 \*(lqSender:\*(rq field is present, the \*(lqFrom:\*(rq field is used.
320 When \*(lqEnvelope\-From:\*(rq appears in a message
321 it will be removed from the final outgoing message.
325 switch, each of the entries in the \*(lqTo:\*(rq
326 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
327 format entries. This standard format is designed to be usable by all
328 of the message handlers on the various systems around the Internet.
331 is given, then headers are output exactly as they appear
332 in the message draft.
334 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
335 to the specified folder for the sender in the format in which it will
336 appear to any non\-Bcc receivers of the message. That is, it will have
337 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
338 will be removed from all outgoing copies of the message.
343 switch, the user can direct
345 as to how long it should make header lines containing addresses.
347 The mail transport system default is provided in
349 but can be overriiden here with the
353 If nmh is using the SMTP MTA, the
357 switches can be used to override the default mail server (defined by the
362 switch can be used to view the SMTP transaction. (Beware that the
363 SMTP transaction may contain authentication information either in
364 plaintext or easily decoded base64.)
368 has been compiled with SASL support, the
372 switches will enable and disable
373 the use of SASL authentication with the SMTP MTA. Depending on the
374 SASL mechanism used, this may require an additional password prompt from the
376 .RI \*(lq \&.netrc \*(rq
377 file can be used to store this password).
379 switch can be used to select a particular SASL mechanism,
382 switch can be used to select a authorization userid
383 to provide to SASL other than the default.
385 If SASL authentication is successful,
387 will attempt to negotiate a security layer for session encryption.
388 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
389 viewing the SMTP transaction with the
393 switch can be used to select the maximum value of the Security Strength Factor.
394 This is an integer value and the exact meaning of this value depends on the
395 underlying SASL mechanism. A value of 0 disables encryption.
399 has been compiled with TLS support, the
403 switches will require and disable the negotiation of TLS support when connecting to the
404 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
405 `(tls-decrypted)' when viewing the SMTP transction with the
409 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
410 additional alias files given by the
414 read (more than one file, each preceded by
419 for more information.
424 .ta \w'%etcdir%/ExtraBigFileName 'u
425 ^$HOME/\&.mh\(ruprofile~^The user profile
428 .SH "PROFILE COMPONENTS"
432 .ta \w'ExtraBigProfileName 'u
433 ^Path:~^To determine the user's nmh directory
434 ^Draft\-Folder:~^To find the default draft\-folder
435 ^Aliasfile:~^For a default alias file
436 ^Signature:~^To determine the user's mail signature
437 ^mailproc:~^Program to post failure notices
438 ^postproc:~^Program to post the message
442 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), mh\-tailor(5), post(8)
446 .RB ` file "' defaults to <mh\-dir>/draft"
447 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
448 .RB ` \-nodraftfolder '
457 .RB ` "\-width\ 72" '
458 .RB ` "\-attach\ Nmh-Attachment" '
459 .RB ` "\-attachformat\ 1" '
466 Under some configurations, it is not possible to monitor the mail delivery
469 is a no-op on those systems.
474 doesn't work correctly.