4 .TH SEND %manext1% "January 23, 2014" "%nmhversion%"
18 .RB [ \-nodraftfolder ]
22 .RB [ \-format " | " \-noformat ]
23 .RB [ \-forward " | " \-noforward ]
24 .RB [ \-mime " | " \-nomime ]
25 .RB [ \-msgid " | " \-nomsgid ]
27 .IR localname " | " random ]
28 .RB [ \-push " | " \-nopush ]
31 .RB [ \-verbose " | " \-noverbose ]
32 .RB [ \-watch " | " \-nowatch ]
34 .IR smtp " | " sendmail/smtp " | " sendmail/pipe ]
38 .IR port-name/number ]
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
85 for delivery, the message is processed by
87 to perform any necessary MIME encoding of the outgoing message. This
96 directives are not processed by default. See
101 will scan the message draft for a header named
103 The draft is converted to a MIME message if one or more matches are found.
104 This conversion occurs before all other processing. The
106 man page describes the user interface for managing MIME attachments via
109 The first part of the MIME message is the draft body if that body contains
110 any non-blank characters.
113 header field is interpreted as a file name, and each file named is included as a separate
114 part in the MIME message.
116 Determination of the content MIME type inserted into the Content-Type
117 header for each part depends on how the
119 installation was configured. If a program, such as
125 option, was found that can specify the type of a file as a MIME type
126 string, then that will be used. To determine if your
128 was so configured, run
129 .B mhparam mimetypeproc
130 and see if a non-empty string is displayed.
134 was not configured with a program to specify a file type as a MIME
135 string, then a different method is used to determine the content-type
136 string. For file names with dot suffixes, the profile is scanned for a
138 entry for that suffix.
139 The content-type for the part is taken from that profile entry if a match is
140 found. If a match is not found in the user profile, the mhn.defaults
141 profile is scanned next.
142 If no match is found or the file does not have a dot suffix, the content-type
143 is text/plain if the file contains only ASCII characters or application/octet-stream
144 if it contains characters outside of the ASCII range. See
146 for more details and example syntax.
148 Each attached MIME part contains a
149 \*(lqContent-Description\*(rq header that includes the filename, and
150 adds a \*(lqContent-Disposition\*(rq header.
151 Here is an example of MIME part headers for an attachment:
154 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
155 Content-Description: VERSION
156 Content-Disposition: attachment; filename="VERSION"
163 will detach itself from the user's
164 terminal and perform its actions in the background. If
166 and the draft can't be sent, then an error message will be sent (using
167 the mailproc) back to the user. If
169 is given, then a copy
170 of the draft will be attached to this failure notice. Using
174 in the background because the output is
175 trapped and analyzed by
182 will indicate the interactions
183 occurring with the transport system, prior to actual delivery.
188 will monitor the delivery of local
189 and network mail. Hence, by specifying both switches, a large detail
190 of information can be gathered about each step of the message's entry
191 into the transport system.
202 draft folder facility. This is an advanced (and highly
203 useful) feature. Consult the
212 will split the draft into one
213 or more partial messages prior to sending. This makes use of the
221 then this switch is ignored\0--\0it makes
222 no sense to redistribute a message in this fashion. Sometimes you want
224 to pause after posting a partial message. This is usually
225 the case when you are running
227 and expect to generate a
228 lot of partial messages. The argument to
231 to pause between postings.
236 argument will query whether the draft
237 is the intended file, whereas
239 will suppress this question.
240 Once the transport system has successfully accepted custody of the
241 message, the file will be renamed with a site-dependent prefix
242 (usually a comma), which allows
243 it to be retrieved until the next draft message is sent. If there are
244 errors in the formatting of the message,
247 (hopefully) helpful error message.
249 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
250 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
251 sent to sighted recipients. The blind recipients will receive an entirely
252 new message with a minimal set of headers. Included in the body of the
253 message will be a copy of the message sent to the sighted recipients.
255 If a \*(lqDcc:\*(rq field is encountered and the
257 mail transport method is not in use, its addresses will be used for
258 delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
259 blind recipients will receive the same message sent to the sighted
260 recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
261 explicit indication that they have received a \*(lqblind copy\*(rq.
262 This can cause blind recipients to
263 inadvertently reply to all of the sighted recipients of the
264 original message, revealing that they received a blind copy.
265 On the other hand, since a normal reply to a message sent
266 via a \*(lqBcc:\*(rq field
267 will generate a reply only to the sender of the original message,
268 it takes extra effort in most mailers to reply to the included
269 message, and so would usually only be done deliberately, rather
275 is specified, then this copy is filtered
278 prior to being sent to the blind recipients.
279 Alternately, if you specify the
284 use the MIME rules for encapsulation.
286 Prior to sending the message, the \*(lqDate:\ now\*(rq field will be appended to the headers in the message.
289 is specified, then a \*(lqMessage\-ID:\*(rq field will also
290 be added to the message.
294 switch selects the style used for the part appearing after the @
295 in \*(lqMessage\-ID:\*(rq, \*(lqResent\-Message\-ID:\*(rq, and
296 \*(lqContent\-ID:\*(rq header fields. The two acceptable options are
298 (which is the default),
303 the local hostname is used. With
305 a random sequence of characters is used instead. Note that the
307 switch must be enabled for this switch to have any effect.
311 is re\-distributing a message (when invoked by
313 then \*(lqResent\-\*(rq will be prepended to each of these
314 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
316 A \*(lqFrom:\*(rq field is required for all outgoing messages. Multiple
317 addresses are permitted in the \*(lqFrom:\*(rq field, but a \*(lqSender:\*(rq
318 field is required in this case. Otherwise a \*(lqSender:\*(rq field
321 If a message with multiple \*(lqFrom:\*(rq
324 include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
325 field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
326 a \*(lqSender:\*(rq field.
328 When using SMTP for mail submission, the envelope\-from used for the SMTP
329 transaction is derived from the \*(lqEnvelope\-From:\*(rq field.
330 If no \*(lqEnvelope\-From:\*(rq field is present, the \*(lqSender:\*(rq
331 field is used. If neither the \*(lqEnvelope\-From:\*(rq nor the
332 \*(lqSender:\*(rq field is present, the \*(lqFrom:\*(rq field is used.
333 When \*(lqEnvelope\-From:\*(rq appears in a message
334 it will be removed from the final outgoing message.
338 switch, each of the entries in the \*(lqTo:\*(rq
339 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
340 format entries. This standard format is designed to be usable by all
341 of the message handlers on the various systems around the Internet.
344 is given, then headers are output exactly as they appear
345 in the message draft.
347 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
348 to the specified folder for the sender in the format in which it will
349 appear to any non\-Bcc receivers of the message. That is, it will have
350 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
351 will be removed from all outgoing copies of the message.
356 switch, the user can direct
358 as to how long it should make header lines containing addresses.
360 The mail transport system default is provided in
362 but can be overriiden here with the
366 If nmh is using the SMTP MTA, the
370 switches can be used to override the default mail server (defined by the
375 switch can be used to view the SMTP transaction. (Beware that the
376 SMTP transaction may contain authentication information either in
377 plaintext or easily decoded base64.)
381 has been compiled with SASL support, the
385 switches will enable and disable
386 the use of SASL authentication with the SMTP MTA. Depending on the
387 SASL mechanism used, this may require an additional password prompt from the
390 file can be used to store this password, as described in the
391 mh-profile(5) man page). The
393 switch can be used to select a particular SASL mechanism,
396 switch can be used to select a authorization userid to provide to SASL
397 other than the default. The credentials profile entry in the
398 mh_profile(5) man page describes the ways to supply a username and
401 If SASL authentication is successful,
403 will attempt to negotiate a security layer for session encryption.
404 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
405 viewing the SMTP transaction with the
409 switch can be used to select the maximum value of the Security Strength Factor.
410 This is an integer value and the exact meaning of this value depends on the
411 underlying SASL mechanism. A value of 0 disables encryption.
415 has been compiled with TLS support, the
419 switches will require the negotiation of TLS when
420 connecting to the SMTP MTA. The
422 switch will negotiate TLS as part of the normal SMTP protocol
423 using the STARTTLS command. The
425 will negotiate TLS immediately after the connection has
426 taken place, before any SMTP commands are sent or received. Encrypted data
427 is labelled with `(tls-encrypted)' and
428 `(tls-decrypted)' when viewing the SMTP transction with the
433 switch will disable all attempts to negotiate TLS.
435 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
436 additional alias files given by the
440 read (more than one file, each preceded by
445 for more information.
449 .ta \w'%etcdir%/ExtraBigFileName 'u
450 ^$HOME/\&.mh\(ruprofile~^The user profile
452 .SH "PROFILE COMPONENTS"
456 .ta \w'ExtraBigProfileName 'u
457 ^Path:~^To determine the user's nmh directory
458 ^Draft\-Folder:~^To find the default draft\-folder
459 ^Aliasfile:~^For a default alias file
460 ^Signature:~^To determine the user's mail signature
461 ^mailproc:~^Program to post failure notices
462 ^postproc:~^Program to post the message
478 .RB ` file "' defaults to <mh\-dir>/draft"
479 .RB ` \-alias "' defaults to %etcdir%/MailAliases"
480 .RB ` \-nodraftfolder '
486 .RB ` "\-messageid\ localname" '
490 .RB ` "\-width\ 72" '
495 Under some configurations, it is not possible to monitor the mail delivery
498 is a no-op on those systems.
503 doesn't work correctly.
projects / nmh / blob