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 ]
42 .IR header-field-name ]
44 .IR 0 " | " 1 " | " 2 ]
48 will cause each of the specified files to be delivered
49 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
50 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
52 is re\-distributing a message, as invoked from
55 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
62 delivery of the messages, although this can be changed by defining the
64 profile component. Most of the features attributed to
66 are actually performed by
74 option, the draft is scanned for a header whose field name matches the
76 .IR header-field-name .
77 The draft is converted to a MIME message if one or more matches are found.
78 This conversion occurs before all other processing.
80 The first part of the MIME message is the draft body if that body contains
81 any non-blank characters.
82 The body of each header field whose name matches the
84 is interpreted as a file name, and each file named is included as a separate
85 part in the MIME message.
87 For file names with dot suffixes, the context is scanned for a
89 entry for that suffix.
90 The content-type for the part is taken from that context entry if a match is
92 If no match is found or the file does not have a dot suffix, the content-type
93 is text/plain if the file contains only ASCII characters or application/octet-stream
94 if it contains characters outside of the ASCII range.
96 Each part contains a name attribute that is the last component of the path name.
99 attribute containing the file mode accompanies each part.
100 Finally, a description attribute is generated by running the
106 option specifies the MIME header field formats: a value of
111 attribute as noted above. A value of
113 suppresses both that and the \*(lqContent-Description\*(rq header, and
114 adds a \*(lqContent-Disposition\*(rq header. A value of
118 parameter to the \*(lqContent-Disposition\*(rq header. You can
119 specify one value in your profile, and override it for individual
124 Here are example message part headers, for an attachment, for each of the
130 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
132 Content-Description: ASCII text
135 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
136 Content-Disposition: attachment; filename="VERSION"
139 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
140 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
147 will detach itself from the user's
148 terminal and perform its actions in the background. If
150 and the draft can't be sent, then an error message will be sent (using
151 the mailproc) back to the user. If
153 is given, then a copy
154 of the draft will be attached to this failure notice. Using
158 in the background because the output is
159 trapped and analyzed by
166 will indicate the interactions
167 occurring with the transport system, prior to actual delivery.
172 will monitor the delivery of local
173 and network mail. Hence, by specifying both switches, a large detail
174 of information can be gathered about each step of the message's entry
175 into the transport system.
186 draft folder facility. This is an advanced (and highly
187 useful) feature. Consult the
196 will split the draft into one
197 or more partial messages prior to sending. This makes use of the
205 then this switch is ignored\0--\0it makes
206 no sense to redistribute a message in this fashion. Sometimes you want
208 to pause after posting a partial message. This is usually
209 the case when you are running
211 and expect to generate a
212 lot of partial messages. The argument to
215 to pause between postings.
220 argument will query whether the draft
221 is the intended file, whereas
223 will suppress this question.
224 Once the transport system has successfully accepted custody of the
225 message, the file will be renamed with a leading comma, which allows
226 it to be retrieved until the next draft message is sent. If there are
227 errors in the formatting of the message,
230 (hopefully) helpful error message.
232 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
233 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
234 sent to sighted recipients. The blind recipients will receive an entirely
235 new message with a minimal set of headers. Included in the body of the
236 message will be a copy of the message sent to the sighted recipients.
238 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
239 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
240 blind recipients will receive the same message sent to the sighted
241 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
242 explicit indication that they have received a \*(lqblind copy\*(rq.
243 This can cause blind recipients to
244 inadvertently reply to all of the sighted recipients of the
245 original message, revealing that they received a blind copy.
246 On the other hand, since a normal reply to a message sent
247 via a \*(lqBcc:\*(rq field
248 will generate a reply only to the sender of the original message,
249 it takes extra effort in most mailers to reply to the included
250 message, and so would usually only be done deliberately, rather
256 is specified, then this copy is filtered
259 prior to being sent to the blind recipients.
260 Alternately, if you specify the
265 use the MIME rules for encapsulation.
267 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
268 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
269 If the environment variable
271 is set, then its value
272 is used as your personal name when constructing the \*(lqFrom:\*(rq
273 line of the message. If this environment variable is not set, then
275 will consult the profile entry \*(lqSignature\*(rq for
279 is specified, then a \*(lqMessage\-ID:\*(rq field will also
280 be added to the message.
284 is re\-distributing a message (when invoked by
286 then \*(lqResent\-\*(rq will be prepended to each of these
287 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
288 If the message already contains a \*(lqFrom:\*(rq field, then a
289 \*(lqSender: user@local\*(rq field will be added as well. (An already
290 existing \*(lqSender:\*(rq field is an error!)
294 switch, each of the entries in the \*(lqTo:\*(rq
295 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
296 format entries. This standard format is designed to be usable by all
297 of the message handlers on the various systems around the Internet.
300 is given, then headers are output exactly as they appear
301 in the message draft.
303 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
304 to the specified folder for the sender in the format in which it will
305 appear to any non\-Bcc receivers of the message. That is, it will have
306 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
307 will be removed from all outgoing copies of the message.
312 switch, the user can direct
314 as to how long it should make header lines containing addresses.
316 If nmh is using the SMTP MTA, the
320 switches can be used to override the default mail server (defined by the
328 has been compiled with TLS support, the
330 switch will require the negotiation of TLS support when connecting to the
331 SMTP MTA. Encrypted data is labelled with `(tls-encrypted)' and
332 `(tls-decrypted)' when viewing the SMTP transction with the
336 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
337 additional alias files given by the
341 read (more than one file, each preceded by
346 for more information.
351 .ta \w'%etcdir%/ExtraBigFileName 'u
352 ^$HOME/\&.mh\(ruprofile~^The user profile
355 .SH "PROFILE COMPONENTS"
359 .ta \w'ExtraBigProfileName 'u
360 ^Path:~^To determine the user's nmh directory
361 ^Draft\-Folder:~^To find the default draft\-folder
362 ^Aliasfile:~^For a default alias file
363 ^Signature:~^To determine the user's mail signature
364 ^mailproc:~^Program to post failure notices
365 ^postproc:~^Program to post the message
369 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
373 .RB ` file "' defaults to <mh\-dir>/draft"
374 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
375 .RB ` \-nodraftfolder '
384 .RB ` "\-width\ 72" '
385 .RB ` "\-attachformat\ 0" '
392 Under some configurations, it is not possible to monitor the mail delivery
395 is a no-op on those systems.
400 doesn't work correctly.