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 ]
27 .IR localname " | " random ]
28 .RB [ \-push " | " \-nopush ]
31 .RB [ \-verbose " | " \-noverbose ]
32 .RB [ \-watch " | " \-nowatch ]
34 .IR smtp " | " sendmail/smtp " | " sendmail/pipe ]
38 .IR port-name/number ]
57 .IR header-field-name ]
60 .IR 0 " | " 1 " | " 2 ]
64 will cause each of the specified files to be delivered
65 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
66 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
68 is re\-distributing a message, as invoked from
71 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
78 delivery of the messages, although this can be changed by defining the
80 profile component. Most of the features attributed to
82 are actually performed by
86 By default the draft is scanned for a header named
88 The draft is converted to a MIME message if one or more matches are found.
89 This conversion occurs before all other processing. The header name
90 can be changed with the
92 option. This behavior can be disabled completely with the
96 The first part of the MIME message is the draft body if that body contains
97 any non-blank characters.
98 The body of each header field whose name matches the
100 is interpreted as a file name, and each file named is included as a separate
101 part in the MIME message.
103 For file names with dot suffixes, the profile is scanned for a
105 entry for that suffix.
106 The content-type for the part is taken from that profile entry if a match is
107 found. If a match is not found in the user profile, the mhn.defaults
108 profile is scanned next.
109 If no match is found or the file does not have a dot suffix, the content-type
110 is text/plain if the file contains only ASCII characters or application/octet-stream
111 if it contains characters outside of the ASCII range. See
113 for more details and example syntax.
115 Each part contains a name attribute that is the last component of the path name.
118 attribute containing the file mode accompanies each part.
119 Finally, a description attribute is generated by running the
125 option specifies the MIME header field formats: a value of
129 attribute as noted above. A value of
132 suppresses that, puts the file name in the
133 \*(lqContent-Description\*(rq header, and
134 adds a \*(lqContent-Disposition\*(rq header. A value of
138 parameter to the \*(lqContent-Disposition\*(rq header. You can
139 specify one value in your profile, and override it for individual
144 Here are example message part headers, for an attachment, for each of the
150 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
152 Content-Description: ASCII text
155 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
156 Content-Description: VERSION
157 Content-Disposition: attachment; filename="VERSION"
160 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
161 Content-Description: VERSION
162 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
169 will detach itself from the user's
170 terminal and perform its actions in the background. If
172 and the draft can't be sent, then an error message will be sent (using
173 the mailproc) back to the user. If
175 is given, then a copy
176 of the draft will be attached to this failure notice. Using
180 in the background because the output is
181 trapped and analyzed by
188 will indicate the interactions
189 occurring with the transport system, prior to actual delivery.
194 will monitor the delivery of local
195 and network mail. Hence, by specifying both switches, a large detail
196 of information can be gathered about each step of the message's entry
197 into the transport system.
208 draft folder facility. This is an advanced (and highly
209 useful) feature. Consult the
218 will split the draft into one
219 or more partial messages prior to sending. This makes use of the
227 then this switch is ignored\0--\0it makes
228 no sense to redistribute a message in this fashion. Sometimes you want
230 to pause after posting a partial message. This is usually
231 the case when you are running
233 and expect to generate a
234 lot of partial messages. The argument to
237 to pause between postings.
242 argument will query whether the draft
243 is the intended file, whereas
245 will suppress this question.
246 Once the transport system has successfully accepted custody of the
247 message, the file will be renamed with a site-dependent prefix
248 (usually a comma), which allows
249 it to be retrieved until the next draft message is sent. If there are
250 errors in the formatting of the message,
253 (hopefully) helpful error message.
255 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
256 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
257 sent to sighted recipients. The blind recipients will receive an entirely
258 new message with a minimal set of headers. Included in the body of the
259 message will be a copy of the message sent to the sighted recipients.
261 If a \*(lqDcc:\*(rq field is encountered and the
263 mail transport method is not in use, its addresses will be used for
264 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
265 blind recipients will receive the same message sent to the sighted
266 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
267 explicit indication that they have received a \*(lqblind copy\*(rq.
268 This can cause blind recipients to
269 inadvertently reply to all of the sighted recipients of the
270 original message, revealing that they received a blind copy.
271 On the other hand, since a normal reply to a message sent
272 via a \*(lqBcc:\*(rq field
273 will generate a reply only to the sender of the original message,
274 it takes extra effort in most mailers to reply to the included
275 message, and so would usually only be done deliberately, rather
281 is specified, then this copy is filtered
284 prior to being sent to the blind recipients.
285 Alternately, if you specify the
290 use the MIME rules for encapsulation.
292 Prior to sending the message, the \*(lqDate:\ now\*(rq field will be appended to the headers in the message.
295 is specified, then a \*(lqMessage\-ID:\*(rq field will also
296 be added to the message.
300 switch selects the style used for the part appearing after the @
301 in \*(lqMessage\-ID:\*(rq, \*(lqResent\-Message\-ID:\*(rq, and
302 \*(lqContent\-ID:\*(rq header fields. The two acceptable options are
304 (which is the default),
309 the local hostname is used. With
311 a random sequence of characters is used instead. Note that the
313 switch must be enabled for this switch to have any effect.
317 is re\-distributing a message (when invoked by
319 then \*(lqResent\-\*(rq will be prepended to each of these
320 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
322 A \*(lqFrom:\*(rq field is required for all outgoing messages. Multiple
323 addresses are permitted in the \*(lqFrom:\*(rq field, but a \*(lqSender:\*(rq
324 field is required in this case. Otherwise a \*(lqSender:\*(rq field
327 If a message with multiple \*(lqFrom:\*(rq
330 include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
331 field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
332 a \*(lqSender:\*(rq field.
334 When using SMTP for mail submission, the envelope\-from used for the SMTP
335 transaction is derived from the \*(lqEnvelope\-From:\*(rq field.
336 If no \*(lqEnvelope\-From:\*(rq field is present, the \*(lqSender:\*(rq
337 field is used. If neither the \*(lqEnvelope\-From:\*(rq nor the
338 \*(lqSender:\*(rq field is present, the \*(lqFrom:\*(rq field is used.
339 When \*(lqEnvelope\-From:\*(rq appears in a message
340 it will be removed from the final outgoing message.
344 switch, each of the entries in the \*(lqTo:\*(rq
345 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
346 format entries. This standard format is designed to be usable by all
347 of the message handlers on the various systems around the Internet.
350 is given, then headers are output exactly as they appear
351 in the message draft.
353 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
354 to the specified folder for the sender in the format in which it will
355 appear to any non\-Bcc receivers of the message. That is, it will have
356 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
357 will be removed from all outgoing copies of the message.
362 switch, the user can direct
364 as to how long it should make header lines containing addresses.
366 The mail transport system default is provided in
368 but can be overriiden here with the
372 If nmh is using the SMTP MTA, the
376 switches can be used to override the default mail server (defined by the
381 switch can be used to view the SMTP transaction. (Beware that the
382 SMTP transaction may contain authentication information either in
383 plaintext or easily decoded base64.)
387 has been compiled with SASL support, the
391 switches will enable and disable
392 the use of SASL authentication with the SMTP MTA. Depending on the
393 SASL mechanism used, this may require an additional password prompt from the
395 .RI \*(lq \&.netrc \*(rq
396 file can be used to store this password).
398 switch can be used to select a particular SASL mechanism,
401 switch can be used to select a authorization userid
402 to provide to SASL other than the default.
404 If SASL authentication is successful,
406 will attempt to negotiate a security layer for session encryption.
407 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
408 viewing the SMTP transaction with the
412 switch can be used to select the maximum value of the Security Strength Factor.
413 This is an integer value and the exact meaning of this value depends on the
414 underlying SASL mechanism. A value of 0 disables encryption.
418 has been compiled with TLS support, the
422 switches will require and disable the negotiation of TLS support when connecting to the
423 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
424 `(tls-decrypted)' when viewing the SMTP transction with the
428 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
429 additional alias files given by the
433 read (more than one file, each preceded by
438 for more information.
443 .ta \w'%etcdir%/ExtraBigFileName 'u
444 ^$HOME/\&.mh\(ruprofile~^The user profile
447 .SH "PROFILE COMPONENTS"
451 .ta \w'ExtraBigProfileName 'u
452 ^Path:~^To determine the user's nmh directory
453 ^Draft\-Folder:~^To find the default draft\-folder
454 ^Aliasfile:~^For a default alias file
455 ^Signature:~^To determine the user's mail signature
456 ^mailproc:~^Program to post failure notices
457 ^postproc:~^Program to post the message
461 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), mh\-tailor(5), post(8)
465 .RB ` file "' defaults to <mh\-dir>/draft"
466 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
467 .RB ` \-nodraftfolder '
473 .RB ` "\-messageid\ localname" '
477 .RB ` "\-width\ 72" '
478 .RB ` "\-attach\ Nmh-Attachment" '
479 .RB ` "\-attachformat\ 1" '
486 Under some configurations, it is not possible to monitor the mail delivery
489 is a no-op on those systems.
494 doesn't work correctly.
projects / mmh / blob