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 ]
56 .IR 0 " | " 1 " | " 2 ]
60 will cause each of the specified files to be delivered
61 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
62 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
64 is re\-distributing a message, as invoked from
67 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
74 delivery of the messages, although this can be changed by defining the
76 profile component. Most of the features attributed to
78 are actually performed by
82 By default the draft is scanned for a header named
84 The draft is converted to a MIME message if one or more matches are found.
85 This conversion occurs before all other processing. The header name
86 can be changed with the
88 option. This behavior can be disabled completely with the
92 The first part of the MIME message is the draft body if that body contains
93 any non-blank characters.
94 The body of each header field whose name matches the
96 is interpreted as a file name, and each file named is included as a separate
97 part in the MIME message.
99 For file names with dot suffixes, the profile is scanned for a
101 entry for that suffix.
102 The content-type for the part is taken from that profile entry if a match is
103 found. If a match is not found in the user profile, the mhn.defaults
104 profile is scanned next.
105 If no match is found or the file does not have a dot suffix, the content-type
106 is text/plain if the file contains only ASCII characters or application/octet-stream
107 if it contains characters outside of the ASCII range. See
109 for more details and example syntax.
111 Each part contains a name attribute that is the last component of the path name.
114 attribute containing the file mode accompanies each part.
115 Finally, a description attribute is generated by running the
121 option specifies the MIME header field formats: a value of
125 attribute as noted above. A value of
128 suppresses that, puts the file name in the
129 \*(lqContent-Description\*(rq header, and
130 adds a \*(lqContent-Disposition\*(rq header. A value of
134 parameter to the \*(lqContent-Disposition\*(rq header. You can
135 specify one value in your profile, and override it for individual
140 Here are example message part headers, for an attachment, for each of the
146 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
148 Content-Description: ASCII text
151 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
152 Content-Description: VERSION
153 Content-Disposition: attachment; filename="VERSION"
156 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
157 Content-Description: VERSION
158 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
165 will detach itself from the user's
166 terminal and perform its actions in the background. If
168 and the draft can't be sent, then an error message will be sent (using
169 the mailproc) back to the user. If
171 is given, then a copy
172 of the draft will be attached to this failure notice. Using
176 in the background because the output is
177 trapped and analyzed by
184 will indicate the interactions
185 occurring with the transport system, prior to actual delivery.
190 will monitor the delivery of local
191 and network mail. Hence, by specifying both switches, a large detail
192 of information can be gathered about each step of the message's entry
193 into the transport system.
204 draft folder facility. This is an advanced (and highly
205 useful) feature. Consult the
214 will split the draft into one
215 or more partial messages prior to sending. This makes use of the
223 then this switch is ignored\0--\0it makes
224 no sense to redistribute a message in this fashion. Sometimes you want
226 to pause after posting a partial message. This is usually
227 the case when you are running
229 and expect to generate a
230 lot of partial messages. The argument to
233 to pause between postings.
238 argument will query whether the draft
239 is the intended file, whereas
241 will suppress this question.
242 Once the transport system has successfully accepted custody of the
243 message, the file will be renamed with a site-dependent prefix
244 (usually a comma), which allows
245 it to be retrieved until the next draft message is sent. If there are
246 errors in the formatting of the message,
249 (hopefully) helpful error message.
251 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
252 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
253 sent to sighted recipients. The blind recipients will receive an entirely
254 new message with a minimal set of headers. Included in the body of the
255 message will be a copy of the message sent to the sighted recipients.
257 If a \*(lqDcc:\*(rq field is encountered and the
259 mail transport method is not in use, its addresses will be used for
260 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
261 blind recipients will receive the same message sent to the sighted
262 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
263 explicit indication that they have received a \*(lqblind copy\*(rq.
264 This can cause blind recipients to
265 inadvertently reply to all of the sighted recipients of the
266 original message, revealing that they received a blind copy.
267 On the other hand, since a normal reply to a message sent
268 via a \*(lqBcc:\*(rq field
269 will generate a reply only to the sender of the original message,
270 it takes extra effort in most mailers to reply to the included
271 message, and so would usually only be done deliberately, rather
277 is specified, then this copy is filtered
280 prior to being sent to the blind recipients.
281 Alternately, if you specify the
286 use the MIME rules for encapsulation.
288 Prior to sending the message, the \*(lqDate:\ now\*(rq field will be appended to the headers in the message.
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.
301 A \*(lqFrom:\*(rq field is required for all outgoing messages. Multiple
302 addresses are permitted in the \*(lqFrom:\*(rq field, but a \*(lqSender:\*(rq
303 field is required in this case. Otherwise a \*(lqSender:\*(rq field
306 If a message with multiple \*(lqFrom:\*(rq
309 include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
310 field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
311 a \*(lqSender:\*(rq field.
313 When using SMTP for mail submission, the envelope\-from used for the SMTP
314 transaction is derived from the \*(lqEnvelope\-From:\*(rq field.
315 If no \*(lqEnvelope\-From:\*(rq field is present, the \*(lqSender:\*(rq
316 field is used. If neither the \*(lqEnvelope\-From:\*(rq nor the
317 \*(lqSender:\*(rq field is present, the \*(lqFrom:\*(rq field is used.
318 When \*(lqEnvelope\-From:\*(rq appears in a message
319 it will be removed from the final outgoing message.
323 switch, each of the entries in the \*(lqTo:\*(rq
324 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
325 format entries. This standard format is designed to be usable by all
326 of the message handlers on the various systems around the Internet.
329 is given, then headers are output exactly as they appear
330 in the message draft.
332 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
333 to the specified folder for the sender in the format in which it will
334 appear to any non\-Bcc receivers of the message. That is, it will have
335 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
336 will be removed from all outgoing copies of the message.
341 switch, the user can direct
343 as to how long it should make header lines containing addresses.
345 If nmh is using the SMTP MTA, the
349 switches can be used to override the default mail server (defined by the
354 switch can be used to view the SMTP transaction. (Beware that the
355 SMTP transaction may contain authentication information either in
356 plaintext or easily decoded base64.)
360 has been compiled with SASL support, the
364 switches will enable and disable
365 the use of SASL authentication with the SMTP MTA. Depending on the
366 SASL mechanism used, this may require an additional password prompt from the
368 .RI \*(lq \&.netrc \*(rq
369 file can be used to store this password).
371 switch can be used to select a particular SASL mechanism,
374 switch can be used to select a authorization userid
375 to provide to SASL other than the default.
377 If SASL authentication is successful,
379 will attempt to negotiate a security layer for session encryption.
380 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
381 viewing the SMTP transaction with the
385 switch can be used to select the maximum value of the Security Strength Factor.
386 This is an integer value and the exact meaning of this value depends on the
387 underlying SASL mechanism. A value of 0 disables encryption.
391 has been compiled with TLS support, the
395 switches will require and disable the negotiation of TLS support when connecting to the
396 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
397 `(tls-decrypted)' when viewing the SMTP transction with the
401 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
402 additional alias files given by the
406 read (more than one file, each preceded by
411 for more information.
416 .ta \w'%etcdir%/ExtraBigFileName 'u
417 ^$HOME/\&.mh\(ruprofile~^The user profile
420 .SH "PROFILE COMPONENTS"
424 .ta \w'ExtraBigProfileName 'u
425 ^Path:~^To determine the user's nmh directory
426 ^Draft\-Folder:~^To find the default draft\-folder
427 ^Aliasfile:~^For a default alias file
428 ^Signature:~^To determine the user's mail signature
429 ^mailproc:~^Program to post failure notices
430 ^postproc:~^Program to post the message
434 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), mh\-tailor(5), post(8)
438 .RB ` file "' defaults to <mh\-dir>/draft"
439 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
440 .RB ` \-nodraftfolder '
449 .RB ` "\-width\ 72" '
450 .RB ` "\-attach\ Nmh-Attachment" '
451 .RB ` "\-attachformat\ 1" '
458 Under some configurations, it is not possible to monitor the mail delivery
461 is a no-op on those systems.
466 doesn't work correctly.
projects / mmh / blob