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 ]
48 .IR header-field-name ]
50 .IR 0 " | " 1 " | " 2 ]
54 will cause each of the specified files to be delivered
55 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
56 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
58 is re\-distributing a message, as invoked from
61 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
68 delivery of the messages, although this can be changed by defining the
70 profile component. Most of the features attributed to
72 are actually performed by
80 option, the draft is scanned for a header whose field name matches the
82 .IR header-field-name .
83 The draft is converted to a MIME message if one or more matches are found.
84 This conversion occurs before all other processing.
86 The first part of the MIME message is the draft body if that body contains
87 any non-blank characters.
88 The body of each header field whose name matches the
90 is interpreted as a file name, and each file named is included as a separate
91 part in the MIME message.
93 For file names with dot suffixes, the context is scanned for a
95 entry for that suffix.
96 The content-type for the part is taken from that context entry if a match is
98 If no match is found or the file does not have a dot suffix, the content-type
99 is text/plain if the file contains only ASCII characters or application/octet-stream
100 if it contains characters outside of the ASCII range.
102 Each part contains a name attribute that is the last component of the path name.
105 attribute containing the file mode accompanies each part.
106 Finally, a description attribute is generated by running the
112 option specifies the MIME header field formats: a value of
117 attribute as noted above. A value of
119 suppresses that, puts the file name in the
120 \*(lqContent-Description\*(rq header, and
121 adds a \*(lqContent-Disposition\*(rq header. A value of
125 parameter to the \*(lqContent-Disposition\*(rq header. You can
126 specify one value in your profile, and override it for individual
131 Here are example message part headers, for an attachment, for each of the
137 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
139 Content-Description: ASCII text
142 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
143 Content-Description: VERSION
144 Content-Disposition: attachment; filename="VERSION"
147 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
148 Content-Description: VERSION
149 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
156 will detach itself from the user's
157 terminal and perform its actions in the background. If
159 and the draft can't be sent, then an error message will be sent (using
160 the mailproc) back to the user. If
162 is given, then a copy
163 of the draft will be attached to this failure notice. Using
167 in the background because the output is
168 trapped and analyzed by
175 will indicate the interactions
176 occurring with the transport system, prior to actual delivery.
181 will monitor the delivery of local
182 and network mail. Hence, by specifying both switches, a large detail
183 of information can be gathered about each step of the message's entry
184 into the transport system.
195 draft folder facility. This is an advanced (and highly
196 useful) feature. Consult the
205 will split the draft into one
206 or more partial messages prior to sending. This makes use of the
214 then this switch is ignored\0--\0it makes
215 no sense to redistribute a message in this fashion. Sometimes you want
217 to pause after posting a partial message. This is usually
218 the case when you are running
220 and expect to generate a
221 lot of partial messages. The argument to
224 to pause between postings.
229 argument will query whether the draft
230 is the intended file, whereas
232 will suppress this question.
233 Once the transport system has successfully accepted custody of the
234 message, the file will be renamed with a leading comma, which allows
235 it to be retrieved until the next draft message is sent. If there are
236 errors in the formatting of the message,
239 (hopefully) helpful error message.
241 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
242 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
243 sent to sighted recipients. The blind recipients will receive an entirely
244 new message with a minimal set of headers. Included in the body of the
245 message will be a copy of the message sent to the sighted recipients.
247 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
248 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
249 blind recipients will receive the same message sent to the sighted
250 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
251 explicit indication that they have received a \*(lqblind copy\*(rq.
252 This can cause blind recipients to
253 inadvertently reply to all of the sighted recipients of the
254 original message, revealing that they received a blind copy.
255 On the other hand, since a normal reply to a message sent
256 via a \*(lqBcc:\*(rq field
257 will generate a reply only to the sender of the original message,
258 it takes extra effort in most mailers to reply to the included
259 message, and so would usually only be done deliberately, rather
265 is specified, then this copy is filtered
268 prior to being sent to the blind recipients.
269 Alternately, if you specify the
274 use the MIME rules for encapsulation.
276 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
277 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
278 If the environment variable
280 is set, then its value
281 is used as your personal name when constructing the \*(lqFrom:\*(rq
282 line of the message. If this environment variable is not set, then
284 will consult the profile entry \*(lqSignature\*(rq for
288 is specified, then a \*(lqMessage\-ID:\*(rq field will also
289 be added to the message.
293 is re\-distributing a message (when invoked by
295 then \*(lqResent\-\*(rq will be prepended to each of these
296 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
297 If the message already contains a \*(lqFrom:\*(rq field, then a
298 \*(lqSender: user@local\*(rq field will be added as well. (An already
299 existing \*(lqSender:\*(rq field is an error!)
303 switch, each of the entries in the \*(lqTo:\*(rq
304 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
305 format entries. This standard format is designed to be usable by all
306 of the message handlers on the various systems around the Internet.
309 is given, then headers are output exactly as they appear
310 in the message draft.
312 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
313 to the specified folder for the sender in the format in which it will
314 appear to any non\-Bcc receivers of the message. That is, it will have
315 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
316 will be removed from all outgoing copies of the message.
321 switch, the user can direct
323 as to how long it should make header lines containing addresses.
325 If nmh is using the SMTP MTA, the
329 switches can be used to override the default mail server (defined by the
337 has been compiled with SASL support, the
340 the use of SASL authentication with the SMTP MTA. Depending on the
341 SASL mechanism used, this may require an additional password prompt from the
343 .RI \*(lq \&.netrc \*(rq
344 file can be used to store this password).
346 switch can be used to select a particular SASL mechanism,
349 switch can be used to select a authorization userid
350 to provide to SASL other than the default.
352 If SASL authentication is successful,
354 will attempt to negotiate a security layer for session encryption.
355 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
356 viewing the SMTP transaction with the
362 has been compiled with TLS support, the
364 switch will require the negotiation of TLS support when connecting to the
365 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
366 `(tls-decrypted)' when viewing the SMTP transction with the
370 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
371 additional alias files given by the
375 read (more than one file, each preceded by
380 for more information.
385 .ta \w'%etcdir%/ExtraBigFileName 'u
386 ^$HOME/\&.mh\(ruprofile~^The user profile
389 .SH "PROFILE COMPONENTS"
393 .ta \w'ExtraBigProfileName 'u
394 ^Path:~^To determine the user's nmh directory
395 ^Draft\-Folder:~^To find the default draft\-folder
396 ^Aliasfile:~^For a default alias file
397 ^Signature:~^To determine the user's mail signature
398 ^mailproc:~^Program to post failure notices
399 ^postproc:~^Program to post the message
403 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
407 .RB ` file "' defaults to <mh\-dir>/draft"
408 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
409 .RB ` \-nodraftfolder '
418 .RB ` "\-width\ 72" '
419 .RB ` "\-attachformat\ 0" '
426 Under some configurations, it is not possible to monitor the mail delivery
429 is a no-op on those systems.
434 doesn't work correctly.
projects / mmh / blob