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 ]
51 .IR header-field-name ]
53 .IR 0 " | " 1 " | " 2 ]
57 will cause each of the specified files to be delivered
58 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
59 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
61 is re\-distributing a message, as invoked from
64 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
71 delivery of the messages, although this can be changed by defining the
73 profile component. Most of the features attributed to
75 are actually performed by
83 option, the draft is scanned for a header whose field name matches the
85 .IR header-field-name .
86 The draft is converted to a MIME message if one or more matches are found.
87 This conversion occurs before all other processing.
89 The first part of the MIME message is the draft body if that body contains
90 any non-blank characters.
91 The body of each header field whose name matches the
93 is interpreted as a file name, and each file named is included as a separate
94 part in the MIME message.
96 For file names with dot suffixes, the context is scanned for a
98 entry for that suffix.
99 The content-type for the part is taken from that context entry if a match is
101 If no match is found or the file does not have a dot suffix, the content-type
102 is text/plain if the file contains only ASCII characters or application/octet-stream
103 if it contains characters outside of the ASCII range.
105 Each part contains a name attribute that is the last component of the path name.
108 attribute containing the file mode accompanies each part.
109 Finally, a description attribute is generated by running the
115 option specifies the MIME header field formats: a value of
120 attribute as noted above. A value of
122 suppresses that, puts the file name in the
123 \*(lqContent-Description\*(rq header, and
124 adds a \*(lqContent-Disposition\*(rq header. A value of
128 parameter to the \*(lqContent-Disposition\*(rq header. You can
129 specify one value in your profile, and override it for individual
134 Here are example message part headers, for an attachment, for each of the
140 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
142 Content-Description: ASCII text
145 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
146 Content-Description: VERSION
147 Content-Disposition: attachment; filename="VERSION"
150 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
151 Content-Description: VERSION
152 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
159 will detach itself from the user's
160 terminal and perform its actions in the background. If
162 and the draft can't be sent, then an error message will be sent (using
163 the mailproc) back to the user. If
165 is given, then a copy
166 of the draft will be attached to this failure notice. Using
170 in the background because the output is
171 trapped and analyzed by
178 will indicate the interactions
179 occurring with the transport system, prior to actual delivery.
184 will monitor the delivery of local
185 and network mail. Hence, by specifying both switches, a large detail
186 of information can be gathered about each step of the message's entry
187 into the transport system.
198 draft folder facility. This is an advanced (and highly
199 useful) feature. Consult the
208 will split the draft into one
209 or more partial messages prior to sending. This makes use of the
217 then this switch is ignored\0--\0it makes
218 no sense to redistribute a message in this fashion. Sometimes you want
220 to pause after posting a partial message. This is usually
221 the case when you are running
223 and expect to generate a
224 lot of partial messages. The argument to
227 to pause between postings.
232 argument will query whether the draft
233 is the intended file, whereas
235 will suppress this question.
236 Once the transport system has successfully accepted custody of the
237 message, the file will be renamed with a leading comma, which allows
238 it to be retrieved until the next draft message is sent. If there are
239 errors in the formatting of the message,
242 (hopefully) helpful error message.
244 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
245 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
246 sent to sighted recipients. The blind recipients will receive an entirely
247 new message with a minimal set of headers. Included in the body of the
248 message will be a copy of the message sent to the sighted recipients.
250 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
251 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
252 blind recipients will receive the same message sent to the sighted
253 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
254 explicit indication that they have received a \*(lqblind copy\*(rq.
255 This can cause blind recipients to
256 inadvertently reply to all of the sighted recipients of the
257 original message, revealing that they received a blind copy.
258 On the other hand, since a normal reply to a message sent
259 via a \*(lqBcc:\*(rq field
260 will generate a reply only to the sender of the original message,
261 it takes extra effort in most mailers to reply to the included
262 message, and so would usually only be done deliberately, rather
268 is specified, then this copy is filtered
271 prior to being sent to the blind recipients.
272 Alternately, if you specify the
277 use the MIME rules for encapsulation.
279 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
280 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
281 If the environment variable
283 is set, then its value
284 is used as your personal name when constructing the \*(lqFrom:\*(rq
285 line of the message. If this environment variable is not set, then
287 will consult the profile entry \*(lqSignature\*(rq for
291 is specified, then a \*(lqMessage\-ID:\*(rq field will also
292 be added to the message.
296 is re\-distributing a message (when invoked by
298 then \*(lqResent\-\*(rq will be prepended to each of these
299 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
300 If the message already contains a \*(lqFrom:\*(rq field, then a
301 \*(lqSender: user@local\*(rq field will be added as well. (An already
302 existing \*(lqSender:\*(rq field is an error!)
306 switch, each of the entries in the \*(lqTo:\*(rq
307 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
308 format entries. This standard format is designed to be usable by all
309 of the message handlers on the various systems around the Internet.
312 is given, then headers are output exactly as they appear
313 in the message draft.
315 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
316 to the specified folder for the sender in the format in which it will
317 appear to any non\-Bcc receivers of the message. That is, it will have
318 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
319 will be removed from all outgoing copies of the message.
324 switch, the user can direct
326 as to how long it should make header lines containing addresses.
328 If nmh is using the SMTP MTA, the
332 switches can be used to override the default mail server (defined by the
340 has been compiled with SASL support, the
344 switches will enable and disable
345 the use of SASL authentication with the SMTP MTA. Depending on the
346 SASL mechanism used, this may require an additional password prompt from the
348 .RI \*(lq \&.netrc \*(rq
349 file can be used to store this password).
351 switch can be used to select a particular SASL mechanism,
354 switch can be used to select a authorization userid
355 to provide to SASL other than the default.
357 If SASL authentication is successful,
359 will attempt to negotiate a security layer for session encryption.
360 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
361 viewing the SMTP transaction with the
365 switch can be used to select the maximum value of the Security Strength Factor.
366 This is an integer value and the exact meaning of this value depends on the
367 underlying SASL mechanism. A value of 0 disables encryption.
371 has been compiled with TLS support, the
373 switch will require the negotiation of TLS support when connecting to the
374 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
375 `(tls-decrypted)' when viewing the SMTP transction with the
379 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
380 additional alias files given by the
384 read (more than one file, each preceded by
389 for more information.
394 .ta \w'%etcdir%/ExtraBigFileName 'u
395 ^$HOME/\&.mh\(ruprofile~^The user profile
398 .SH "PROFILE COMPONENTS"
402 .ta \w'ExtraBigProfileName 'u
403 ^Path:~^To determine the user's nmh directory
404 ^Draft\-Folder:~^To find the default draft\-folder
405 ^Aliasfile:~^For a default alias file
406 ^Signature:~^To determine the user's mail signature
407 ^mailproc:~^Program to post failure notices
408 ^postproc:~^Program to post the message
412 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
416 .RB ` file "' defaults to <mh\-dir>/draft"
417 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
418 .RB ` \-nodraftfolder '
427 .RB ` "\-width\ 72" '
428 .RB ` "\-attachformat\ 0" '
435 Under some configurations, it is not possible to monitor the mail delivery
438 is a no-op on those systems.
443 doesn't work correctly.
projects / mmh / blob