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 ]
35 .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 both that and the \*(lqContent-Description\*(rq header, and
120 adds a \*(lqContent-Disposition\*(rq header. A value of
124 parameter to the \*(lqContent-Disposition\*(rq header. You can
125 specify one value in your profile, and override it for individual
130 Here are example message part headers for each of the
136 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
138 Content-Description: ASCII text
141 Content-Type: text/plain; charset="us-ascii"
142 Content-Disposition: attachment; filename="VERSION"
145 Content-Type: text/plain; charset="us-ascii"
146 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
153 will detach itself from the user's
154 terminal and perform its actions in the background. If
156 and the draft can't be sent, then an error message will be sent (using
157 the mailproc) back to the user. If
159 is given, then a copy
160 of the draft will be attached to this failure notice. Using
164 in the background because the output is
165 trapped and analyzed by
172 will indicate the interactions
173 occurring with the transport system, prior to actual delivery.
178 will monitor the delivery of local
179 and network mail. Hence, by specifying both switches, a large detail
180 of information can be gathered about each step of the message's entry
181 into the transport system.
192 draft folder facility. This is an advanced (and highly
193 useful) feature. Consult the
202 will split the draft into one
203 or more partial messages prior to sending. This makes use of the
211 then this switch is ignored\0--\0it makes
212 no sense to redistribute a message in this fashion. Sometimes you want
214 to pause after posting a partial message. This is usually
215 the case when you are running
217 and expect to generate a
218 lot of partial messages. The argument to
221 to pause between postings.
226 argument will query whether the draft
227 is the intended file, whereas
229 will suppress this question.
230 Once the transport system has successfully accepted custody of the
231 message, the file will be renamed with a leading comma, which allows
232 it to be retrieved until the next draft message is sent. If there are
233 errors in the formatting of the message,
236 (hopefully) helpful error message.
238 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
239 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
240 sent to sighted recipients. The blind recipients will receive an entirely
241 new message with a minimal set of headers. Included in the body of the
242 message will be a copy of the message sent to the sighted recipients.
244 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
245 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
246 blind recipients will receive the same message sent to the sighted
247 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
248 explicit indication that they have received a \*(lqblind copy\*(rq.
249 This can cause blind recipients to
250 inadvertently reply to all of the sighted recipients of the
251 original message, revealing that they received a blind copy.
252 On the other hand, since a normal reply to a message sent
253 via a \*(lqBcc:\*(rq field
254 will generate a reply only to the sender of the original message,
255 it takes extra effort in most mailers to reply to the included
256 message, and so would usually only be done deliberately, rather
262 is specified, then this copy is filtered
265 prior to being sent to the blind recipients.
266 Alternately, if you specify the
271 use the MIME rules for encapsulation.
273 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
274 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
275 If the environment variable
277 is set, then its value
278 is used as your personal name when constructing the \*(lqFrom:\*(rq
279 line of the message. If this environment variable is not set, then
281 will consult the profile entry \*(lqSignature\*(rq for
285 is specified, then a \*(lqMessage\-ID:\*(rq field will also
286 be added to the message.
290 is re\-distributing a message (when invoked by
292 then \*(lqResent\-\*(rq will be prepended to each of these
293 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
294 If the message already contains a \*(lqFrom:\*(rq field, then a
295 \*(lqSender: user@local\*(rq field will be added as well. (An already
296 existing \*(lqSender:\*(rq field is an error!)
300 switch, each of the entries in the \*(lqTo:\*(rq
301 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
302 format entries. This standard format is designed to be usable by all
303 of the message handlers on the various systems around the Internet.
306 is given, then headers are output exactly as they appear
307 in the message draft.
309 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
310 to the specified folder for the sender in the format in which it will
311 appear to any non\-Bcc receivers of the message. That is, it will have
312 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
313 will be removed from all outgoing copies of the message.
318 switch, the user can direct
320 as to how long it should make header lines containing addresses.
322 If nmh is using the SMTP MTA, the
326 switches can be used to override the default mail server (defined by the
334 has been compiled with SASL support, the
337 the use of SASL authentication with the SMTP MTA. Depending on the
338 SASL mechanism used, this may require an additional password prompt from the
340 .RI \*(lq \&.netrc \*(rq
341 file can be used to store this password).
343 switch can be used to select a particular SASL mechanism,
346 switch can be used to select a authorization userid
347 to provide to SASL other than the default.
349 If SASL authentication is successful,
351 will attempt to negotiate a security layer for session encryption.
352 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
353 viewing the SMTP transaction with the
357 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
358 additional alias files given by the
362 read (more than one file, each preceded by
367 for more information.
372 .ta \w'%etcdir%/ExtraBigFileName 'u
373 ^$HOME/\&.mh\(ruprofile~^The user profile
376 .SH "PROFILE COMPONENTS"
380 .ta \w'ExtraBigProfileName 'u
381 ^Path:~^To determine the user's nmh directory
382 ^Draft\-Folder:~^To find the default draft\-folder
383 ^Aliasfile:~^For a default alias file
384 ^Signature:~^To determine the user's mail signature
385 ^mailproc:~^Program to post failure notices
386 ^postproc:~^Program to post the message
390 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
394 .RB ` file "' defaults to <mh\-dir>/draft"
395 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
396 .RB ` \-nodraftfolder '
405 .RB ` "\-width\ 72" '
406 .RB ` "\-attachformat\ 0" '
413 Under some configurations, it is not possible to monitor the mail delivery
416 is a no-op on those systems.
421 doesn't work correctly.
projects / mmh / blob