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 ]
44 .IR header-field-name ]
46 .IR 0 " | " 1 " | " 2 ]
50 will cause each of the specified files to be delivered
51 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
52 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
54 is re\-distributing a message, as invoked from
57 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
64 delivery of the messages, although this can be changed by defining the
66 profile component. Most of the features attributed to
68 are actually performed by
76 option, the draft is scanned for a header whose field name matches the
78 .IR header-field-name .
79 The draft is converted to a MIME message if one or more matches are found.
80 This conversion occurs before all other processing.
82 The first part of the MIME message is the draft body if that body contains
83 any non-blank characters.
84 The body of each header field whose name matches the
86 is interpreted as a file name, and each file named is included as a separate
87 part in the MIME message.
89 For file names with dot suffixes, the context is scanned for a
91 entry for that suffix.
92 The content-type for the part is taken from that context entry if a match is
94 If no match is found or the file does not have a dot suffix, the content-type
95 is text/plain if the file contains only ASCII characters or application/octet-stream
96 if it contains characters outside of the ASCII range.
98 Each part contains a name attribute that is the last component of the path name.
101 attribute containing the file mode accompanies each part.
102 Finally, a description attribute is generated by running the
108 option specifies the MIME header field formats: a value of
113 attribute as noted above. A value of
115 suppresses both that and the \*(lqContent-Description\*(rq header, and
116 adds a \*(lqContent-Disposition\*(rq header. A value of
120 parameter to the \*(lqContent-Disposition\*(rq header. You can
121 specify one value in your profile, and override it for individual
126 Here are example message part headers for each of the
132 Content-Type: text/plain; name="VERSION"; x-unix-mode="0644";
134 Content-Description: ASCII text
137 Content-Type: text/plain; charset="us-ascii"
138 Content-Disposition: attachment; filename="VERSION"
141 Content-Type: text/plain; charset="us-ascii"
142 Content-Disposition: attachment; filename="VERSION"; modification-date="Mon, 19 Dec 2005 22:39:51 -0600"
149 will detach itself from the user's
150 terminal and perform its actions in the background. If
152 and the draft can't be sent, then an error message will be sent (using
153 the mailproc) back to the user. If
155 is given, then a copy
156 of the draft will be attached to this failure notice. Using
160 in the background because the output is
161 trapped and analyzed by
168 will indicate the interactions
169 occurring with the transport system, prior to actual delivery.
174 will monitor the delivery of local
175 and network mail. Hence, by specifying both switches, a large detail
176 of information can be gathered about each step of the message's entry
177 into the transport system.
188 draft folder facility. This is an advanced (and highly
189 useful) feature. Consult the
198 will split the draft into one
199 or more partial messages prior to sending. This makes use of the
207 then this switch is ignored\0--\0it makes
208 no sense to redistribute a message in this fashion. Sometimes you want
210 to pause after posting a partial message. This is usually
211 the case when you are running
213 and expect to generate a
214 lot of partial messages. The argument to
217 to pause between postings.
222 argument will query whether the draft
223 is the intended file, whereas
225 will suppress this question.
226 Once the transport system has successfully accepted custody of the
227 message, the file will be renamed with a leading comma, which allows
228 it to be retrieved until the next draft message is sent. If there are
229 errors in the formatting of the message,
232 (hopefully) helpful error message.
234 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
235 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
236 sent to sighted recipients. The blind recipients will receive an entirely
237 new message with a minimal set of headers. Included in the body of the
238 message will be a copy of the message sent to the sighted recipients.
240 If a \*(lqDcc:\*(rq field is encountered, its addresses will be used for
241 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
242 blind recipients will receive the same message sent to the sighted
243 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
244 explicit indication that they have received a \*(lqblind copy\*(rq.
245 This can cause blind recipients to
246 inadvertently reply to all of the sighted recipients of the
247 original message, revealing that they received a blind copy.
248 On the other hand, since a normal reply to a message sent
249 via a \*(lqBcc:\*(rq field
250 will generate a reply only to the sender of the original message,
251 it takes extra effort in most mailers to reply to the included
252 message, and so would usually only be done deliberately, rather
258 is specified, then this copy is filtered
261 prior to being sent to the blind recipients.
262 Alternately, if you specify the
267 use the MIME rules for encapsulation.
269 Prior to sending the message, the fields \*(lqFrom:\ user@local\*(rq,
270 and \*(lqDate:\ now\*(rq will be appended to the headers in the message.
271 If the environment variable
273 is set, then its value
274 is used as your personal name when constructing the \*(lqFrom:\*(rq
275 line of the message. If this environment variable is not set, then
277 will consult the profile entry \*(lqSignature\*(rq for
281 is specified, then a \*(lqMessage\-ID:\*(rq field will also
282 be added to the message.
286 is re\-distributing a message (when invoked by
288 then \*(lqResent\-\*(rq will be prepended to each of these
289 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
290 If the message already contains a \*(lqFrom:\*(rq field, then a
291 \*(lqSender: user@local\*(rq field will be added as well. (An already
292 existing \*(lqSender:\*(rq field is an error!)
296 switch, each of the entries in the \*(lqTo:\*(rq
297 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
298 format entries. This standard format is designed to be usable by all
299 of the message handlers on the various systems around the Internet.
302 is given, then headers are output exactly as they appear
303 in the message draft.
305 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
306 to the specified folder for the sender in the format in which it will
307 appear to any non\-Bcc receivers of the message. That is, it will have
308 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
309 will be removed from all outgoing copies of the message.
314 switch, the user can direct
316 as to how long it should make header lines containing addresses.
320 has been compiled with SASL support, the
323 the use of SASL authentication with the SMTP MTA. Depending on the
324 SASL mechanism used, this may require an additional password prompt from the
326 .RI \*(lq \&.netrc \*(rq
327 file can be used to store this password).
329 switch can be used to select a particular SASL mechanism,
332 switch can be used to select a authorization userid
333 to provide to SASL other than the default.
335 Currently SASL security layers are not supported for SMTP.
338 will always negotiate an unencrypted connection. This means that while the SMTP
339 authentication can be encrypted, the subsequent data stream can not. This is in
342 POP3 SASL support, where encryption is supported for both the
343 authentication and the data stream.
345 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
346 additional alias files given by the
350 read (more than one file, each preceded by
355 for more information.
360 .ta \w'%etcdir%/ExtraBigFileName 'u
361 ^$HOME/\&.mh\(ruprofile~^The user profile
364 .SH "PROFILE COMPONENTS"
368 .ta \w'ExtraBigProfileName 'u
369 ^Path:~^To determine the user's nmh directory
370 ^Draft\-Folder:~^To find the default draft\-folder
371 ^Aliasfile:~^For a default alias file
372 ^Signature:~^To determine the user's mail signature
373 ^mailproc:~^Program to post failure notices
374 ^postproc:~^Program to post the message
378 comp(1), dist(1), forw(1), repl(1), mh\-alias(5), post(8)
382 .RB ` file "' defaults to <mh\-dir>/draft"
383 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
384 .RB ` \-nodraftfolder '
393 .RB ` "\-width\ 72" '
394 .RB ` "\-attachformat\ 0" '
401 Under some configurations, it is not possible to monitor the mail delivery
404 is a no-op on those systems.
409 doesn't work correctly.