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 ]
34 .IR port-name/number ]
53 .IR header-field-name ]
55 .IR 0 " | " 1 " | " 2 ]
59 will cause each of the specified files to be delivered
60 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
61 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
63 is re\-distributing a message, as invoked from
66 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
73 delivery of the messages, although this can be changed by defining the
75 profile component. Most of the features attributed to
77 are actually performed by
85 option, the draft is scanned for a header whose field name matches the
87 .IR header-field-name .
88 The draft is converted to a MIME message if one or more matches are found.
89 This conversion occurs before all other processing.
91 The first part of the MIME message is the draft body if that body contains
92 any non-blank characters.
93 The body of each header field whose name matches the
95 is interpreted as a file name, and each file named is included as a separate
96 part in the MIME message.
98 For file names with dot suffixes, the context is scanned for a
100 entry for that suffix.
101 The content-type for the part is taken from that context entry if a match is
103 If no match is found or the file does not have a dot suffix, the content-type
104 is text/plain if the file contains only ASCII characters or application/octet-stream
105 if it contains characters outside of the ASCII range.
107 Each part contains a name attribute that is the last component of the path name.
110 attribute containing the file mode accompanies each part.
111 Finally, a description attribute is generated by running the
117 option specifies the MIME header field formats: a value of
122 attribute as noted above. A value of
124 suppresses that, puts the file name in the
125 \*(lqContent-Description\*(rq header, and
126 adds a \*(lqContent-Disposition\*(rq header. A value of
130 parameter to the \*(lqContent-Disposition\*(rq header. You can
131 specify one value in your profile, and override it for individual
136 Here are example message part headers, for an attachment, for each of the
142 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
144 Content-Description: ASCII text
147 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
148 Content-Description: VERSION
149 Content-Disposition: attachment; filename="VERSION"
152 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
153 Content-Description: VERSION
154 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
161 will detach itself from the user's
162 terminal and perform its actions in the background. If
164 and the draft can't be sent, then an error message will be sent (using
165 the mailproc) back to the user. If
167 is given, then a copy
168 of the draft will be attached to this failure notice. Using
172 in the background because the output is
173 trapped and analyzed by
180 will indicate the interactions
181 occurring with the transport system, prior to actual delivery.
186 will monitor the delivery of local
187 and network mail. Hence, by specifying both switches, a large detail
188 of information can be gathered about each step of the message's entry
189 into the transport system.
200 draft folder facility. This is an advanced (and highly
201 useful) feature. Consult the
210 will split the draft into one
211 or more partial messages prior to sending. This makes use of the
219 then this switch is ignored\0--\0it makes
220 no sense to redistribute a message in this fashion. Sometimes you want
222 to pause after posting a partial message. This is usually
223 the case when you are running
225 and expect to generate a
226 lot of partial messages. The argument to
229 to pause between postings.
234 argument will query whether the draft
235 is the intended file, whereas
237 will suppress this question.
238 Once the transport system has successfully accepted custody of the
239 message, the file will be renamed with a leading comma, which allows
240 it to be retrieved until the next draft message is sent. If there are
241 errors in the formatting of the message,
244 (hopefully) helpful error message.
246 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
247 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
248 sent to sighted recipients. The blind recipients will receive an entirely
249 new message with a minimal set of headers. Included in the body of the
250 message will be a copy of the message sent to the sighted recipients.
252 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
253 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
254 blind recipients will receive the same message sent to the sighted
255 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
256 explicit indication that they have received a \*(lqblind copy\*(rq.
257 This can cause blind recipients to
258 inadvertently reply to all of the sighted recipients of the
259 original message, revealing that they received a blind copy.
260 On the other hand, since a normal reply to a message sent
261 via a \*(lqBcc:\*(rq field
262 will generate a reply only to the sender of the original message,
263 it takes extra effort in most mailers to reply to the included
264 message, and so would usually only be done deliberately, rather
270 is specified, then this copy is filtered
273 prior to being sent to the blind recipients.
274 Alternately, if you specify the
279 use the MIME rules for encapsulation.
281 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
282 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
283 If the environment variable
285 is set, then its value
286 is used as your personal name when constructing the \*(lqFrom:\*(rq
287 line of the message. If this environment variable is not set, then
289 will consult the profile entry \*(lqSignature\*(rq for
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.
302 If the message already contains a \*(lqFrom:\*(rq field, then a
303 \*(lqSender: user@local\*(rq field will be added as well. (An already
304 existing \*(lqSender:\*(rq field is an error!)
308 switch, each of the entries in the \*(lqTo:\*(rq
309 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
310 format entries. This standard format is designed to be usable by all
311 of the message handlers on the various systems around the Internet.
314 is given, then headers are output exactly as they appear
315 in the message draft.
317 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
318 to the specified folder for the sender in the format in which it will
319 appear to any non\-Bcc receivers of the message. That is, it will have
320 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
321 will be removed from all outgoing copies of the message.
326 switch, the user can direct
328 as to how long it should make header lines containing addresses.
330 If nmh is using the SMTP MTA, the
334 switches can be used to override the default mail server (defined by the
339 switch can be used to view the SMTP transaction. (Beware that the
340 SMTP transaction may contain authentication information either in
341 plaintext or easily decoded base64.)
345 has been compiled with SASL support, the
349 switches will enable and disable
350 the use of SASL authentication with the SMTP MTA. Depending on the
351 SASL mechanism used, this may require an additional password prompt from the
353 .RI \*(lq \&.netrc \*(rq
354 file can be used to store this password).
356 switch can be used to select a particular SASL mechanism,
359 switch can be used to select a authorization userid
360 to provide to SASL other than the default.
362 If SASL authentication is successful,
364 will attempt to negotiate a security layer for session encryption.
365 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
366 viewing the SMTP transaction with the
370 switch can be used to select the maximum value of the Security Strength Factor.
371 This is an integer value and the exact meaning of this value depends on the
372 underlying SASL mechanism. A value of 0 disables encryption.
376 has been compiled with TLS support, the
380 switches will require and disable the negotiation of TLS support when connecting to the
381 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
382 `(tls-decrypted)' when viewing the SMTP transction with the
386 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
387 additional alias files given by the
391 read (more than one file, each preceded by
396 for more information.
401 .ta \w'%etcdir%/ExtraBigFileName 'u
402 ^$HOME/\&.mh\(ruprofile~^The user profile
405 .SH "PROFILE COMPONENTS"
409 .ta \w'ExtraBigProfileName 'u
410 ^Path:~^To determine the user's nmh directory
411 ^Draft\-Folder:~^To find the default draft\-folder
412 ^Aliasfile:~^For a default alias file
413 ^Signature:~^To determine the user's mail signature
414 ^mailproc:~^Program to post failure notices
415 ^postproc:~^Program to post the message
419 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
423 .RB ` file "' defaults to <mh\-dir>/draft"
424 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
425 .RB ` \-nodraftfolder '
434 .RB ` "\-width\ 72" '
435 .RB ` "\-attachformat\ 0" '
442 Under some configurations, it is not possible to monitor the mail delivery
445 is a no-op on those systems.
450 doesn't work correctly.
projects / mmh / blob