1 .TH SEND %manext1% 2017-05-11 "%nmhversion%"
6 send \- send an nmh message
20 .RB [ \-nodraftfolder ]
24 .RB [ \-format " | " \-noformat ]
25 .RB [ \-forward " | " \-noforward ]
26 .RB [ \-mime " | " \-nomime ]
27 .RB [ \-msgid " | " \-nomsgid ]
29 .IR localname " | " random ]
30 .RB [ \-push " | " \-nopush ]
31 .RB [ \-verbose " | " \-noverbose ]
32 .RB [ \-watch " | " \-nowatch ]
34 .IR smtp " | " sendmail/smtp " | " sendmail/pipe ]
40 .IR port-name/number ]
54 .RB [ \-nocertverify ]
62 will cause each of the specified files to be delivered
63 to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
64 \*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
66 is re-distributing a message, as invoked from
69 corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
76 delivery of the messages, although this can be changed by defining the
78 profile component. Most of the features attributed to
80 are actually performed by
87 for delivery, the message is processed by
89 to perform any necessary MIME encoding of the outgoing message. This
98 directives are not processed by default. See
100 for more information.
103 will scan the message draft for a header named
105 The draft is converted to a MIME message if one or more matches are found.
106 This conversion occurs before all other processing.
108 describes the user interface for managing MIME attachments via
111 The first part of the MIME message is the draft body if that body contains
112 any non-blank characters.
115 header field is interpreted as a file name, and each file named is included as a separate
116 part in the MIME message.
118 Determination of the content MIME type inserted into the Content-Type
119 header for each part depends on how the
121 installation was configured. If a program, such as
127 option, was found that can specify the type of a file as a MIME type
128 string, then that will be used. To determine if your
130 was so configured, run
131 .B mhparam mimetypeproc
132 and see if a non-empty string is displayed.
136 was not configured with a program to specify a file type as a MIME
137 string, then a different method is used to determine the content-type
138 string. For file names with dot suffixes, the profile is scanned for a
140 entry for that suffix.
141 The content-type for the part is taken from that profile entry if a match is
142 found. If a match is not found in the user profile, the mhn.defaults
143 profile is scanned next.
144 If no match is found or the file does not have a dot suffix, the content-type
145 is text/plain if the file contains only ASCII characters or application/octet-stream
146 if it contains characters outside of the ASCII range. See
148 for more details and example syntax.
150 Each attached MIME part contains a
151 \*(lqContent-Description\*(rq header that includes the filename, and
152 adds a \*(lqContent-Disposition\*(rq header.
153 Here is an example of MIME part headers for an attachment:
156 Content-Type: text/plain; name="VERSION"; charset="us-ascii"
157 Content-Description: VERSION
158 Content-Disposition: attachment; filename="VERSION"
163 for explanation of how the Content-Disposition value is selected.
169 will detach itself from the user's
170 terminal and perform its actions in the background. If
172 and the draft can't be sent, then an error message will be sent (using
173 the mailproc) back to the user. If
175 is given, then a copy
176 of the draft will be attached to this failure notice. Using
180 in the background because the output is
181 trapped and analyzed by
188 will indicate the interactions
189 occurring with the transport system, prior to actual delivery.
194 will monitor the delivery of local
195 and network mail. Hence, by specifying both switches, a large detail
196 of information can be gathered about each step of the message's entry
197 into the transport system.
208 draft folder facility. This is an advanced (and highly
209 useful) feature. Consult
217 argument will query whether the draft
218 is the intended file, whereas
220 will suppress this question.
221 Once the transport system has successfully accepted custody of the
222 message, the file will be renamed with a site-dependent prefix
223 (usually a comma), which allows
224 it to be retrieved until the next draft message is sent. If there are
225 errors in the formatting of the message,
228 (hopefully) helpful error message.
230 If a \*(lqBcc:\*(rq field is encountered, its addresses will be used for
231 delivery, and the \*(lqBcc:\*(rq field will be removed from the message
232 sent to sighted recipients. The blind recipients will receive an entirely
233 new message with a minimal set of headers. The body of this new message
234 will contain a copy of the message sent to the sighted recipients, either
235 marked up with the indicator text "Blind-Carbon-Copy" or encapsulated
238 If a \*(lqDcc:\*(rq field is encountered and the
240 mail transport method is not in use, 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 exactly the same message as 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
257 mail transport method is used, then messages containing
258 a \*(lqDcc:\*(rq field are rejected.
264 is specified, then this copy is filtered
267 prior to being sent to the blind recipients.
268 Alternately, if you specify the
273 use the MIME rules for encapsulation.
275 Prior to sending the message, the \*(lqDate:\ now\*(rq field will be appended to the headers in the message.
278 is specified, then a \*(lqMessage\-ID:\*(rq field will also
279 be added to the message.
283 switch selects the style used for the part appearing after the @
284 in \*(lqMessage\-ID:\*(rq, \*(lqResent\-Message\-ID:\*(rq, and
285 \*(lqContent\-ID:\*(rq header fields. The two acceptable options are
287 (which is the default),
292 the local hostname is used. With
294 a random sequence of characters is used instead. Note that the
296 switch must be enabled for this switch to have any effect.
300 is re-distributing a message (when invoked by
302 then \*(lqResent\-\*(rq will be prepended to each of these
303 fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
305 A \*(lqFrom:\*(rq field is required for all outgoing messages. Multiple
306 addresses are permitted in the \*(lqFrom:\*(rq field, but a \*(lqSender:\*(rq
307 field is required in this case. Otherwise a \*(lqSender:\*(rq field
310 If a message with multiple \*(lqFrom:\*(rq
313 include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
314 field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
315 a \*(lqSender:\*(rq field.
317 When using SMTP for mail submission, the envelope-from used for the SMTP
318 transaction is derived from the \*(lqEnvelope\-From:\*(rq field.
319 If no \*(lqEnvelope\-From:\*(rq field is present, the \*(lqSender:\*(rq
320 field is used. If neither the \*(lqEnvelope\-From:\*(rq nor the
321 \*(lqSender:\*(rq field is present, the \*(lqFrom:\*(rq field is used.
322 When \*(lqEnvelope\-From:\*(rq appears in a message
323 it will be removed from the final outgoing message.
327 switch, each of the entries in the \*(lqTo:\*(rq
328 and \*(lqcc:\*(rq fields will be replaced with \*(lqstandard\*(rq
329 format entries. This standard format is designed to be usable by all
330 of the message handlers on the various systems around the Internet.
333 is given, then headers are output exactly as they appear
334 in the message draft.
336 If an \*(lqFcc:\ folder\*(rq is encountered, the message will be copied
337 to the specified folder for the sender in the format in which it will
338 appear to any non\-Bcc receivers of the message. That is, it will have
339 the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
340 will be removed from all outgoing copies of the message.
342 Beware that if an \*(lqFcc:\*(rq with one or more folders is present
343 but none of the folders exist, and the default
349 will prompt the user to create the folder(s) if
351 is not specified. If all responses are negative, or creation of each folder
354 is specified, the message will not be copied to any folder and will be
359 switches, the message draft will be renamed according to the specification
367 switch, the user can direct
369 as to how long it should make header lines containing addresses.
371 The mail transport system default is provided in
372 .I %nmhetcdir%/mts.conf
373 but can be overridden here with the
381 as its mail transport system, the
383 switch can be used to override the default
387 If nmh is using the SMTP MTA, the
391 switches can be used to override the default mail server (defined by the
392 .I %nmhetcdir%/mts.conf
396 switch can be used to view the SMTP transaction. (Beware that the
397 SMTP transaction may contain authentication information either in
398 plaintext or easily decoded base64.) If
399 .B \-sasl \-saslmech xoauth2
400 is used, the HTTP transaction is also shown.
404 has been compiled with SASL support, the
408 switches will enable and disable
409 the use of SASL authentication with the SMTP MTA. Depending on the
410 SASL mechanism used, this may require an additional password prompt from the
413 file can be used to store this password, as described in
417 switch can be used to select a particular SASL mechanism,
420 switch can be used to select a authorization userid to provide to SASL
421 other than the default. The credentials profile entry in
423 describes the ways to supply a username and
426 If SASL authentication is successful,
428 will attempt to negotiate a security layer for session encryption.
429 Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
430 viewing the SMTP transaction with the
436 for its other features.
440 has been compiled with OAuth support, the
443 .B \-saslmech xoauth2
444 switches will enable OAuth authentication. The
446 switch must be used, and the
448 must be an email address the user has for the service, which must
449 be specified with the
452 switch. Before using OAuth authentication, the user must authorize nmh by
455 and grant authorization to that account. See
461 has been compiled with TLS support, the
465 switches will require the negotiation of TLS when
466 connecting to the SMTP MTA. The
468 switch will negotiate TLS as part of the normal SMTP protocol
469 using the STARTTLS command. The
471 will negotiate TLS immediately after the connection has
472 taken place, before any SMTP commands are sent or received. Encrypted data
473 is labelled with `(tls-encrypted)' and
474 `(tls-decrypted)' when viewing the SMTP transaction with the
480 for its other features.
483 switch will disable all attempts to negotiate TLS.
485 If port 465 is specified and none of the TLS switches were enabled,
487 will be implied if TLS support was compiled in. Though port 465 for
488 SMTPS (SMTP over SSL) was deregistered by IANA in 1998, it is still
489 used for that service.
491 When using TLS the default is to verify the remote certificate and SubjectName
492 against the local trusted certificate store. This can be controlled by
497 switches. See your OpenSSL documentation for more information on certificate
500 The files specified by the profile entry \*(lqAliasfile:\*(rq and any
501 additional alias files given by the
505 read (more than one file, each preceded by
510 for more information.
511 .SS Selection based on sender address: sendfrom
514 profile components can be used to select a mail server address, mail server
515 port, or any other switch that can be supplied to
517 It works by first looking at the sender address and domain name in the
518 message draft, as described below.
519 It then looks for a corresponding profile entry, which contains the
522 To enable, add profile entries of the form:
525 .RI sendfrom- "address/domain name" : " post switches"
528 The email address is extracted from the Envelope-From: header, if not blank,
529 the Sender: header, or the From: header line in the message draft.
530 Multiple profile entries, with different email addresses or domain names, are
532 This allows different switches to
534 such as -user, to be associated with different email addresses.
535 If a domain name is used, it matches all users in that domain.
537 Here is an example profile entry using OAuth for an account hosted by gmail:
541 sendfrom-gmail_address@example.com: -sasl -saslmech xoauth2
543 -authservice gmail -tls -server smtp.gmail.com
544 -user gmail_login@example.com
549 (Indentation indicates a continued line, as supported in MH profiles.)
550 The username need not be the same as the sender address, which was extracted
551 from the appropriate header line as noted above.
553 Here are example profile entries that use an nmh credentials file:
557 credentials: file:nmhcreds
558 sendfrom-sendgrid_address@example.com: -sasl -tls
560 -server smtp.sendgrid.net
562 sendfrom-outbound.att.net: -sasl -initialtls
564 -server outbound.att.net -port 465
566 sendfrom-fastmail.com: -initialtls -sasl -saslmech LOGIN
568 -server smtps-proxy.messagingengine.com -port 80
573 where nmhcreds is in the user's nmh directory (from the Path profile component)
578 machine smtp.sendgrid.net
580 login sendgrid_login@example.com
583 machine outbound.att.net
585 login att_login@example.com
588 machine smtps-proxy.messagingengine.com
590 login fastmail_login@example.com
596 For more information on authentication to mail servers, see
598 for OAuth services, and
600 for login credentials.
605 .ta \w'%nmhetcdir%/ExtraBigFileName 'u
606 ^$HOME/.mh_profile~^The user profile
608 .SH "PROFILE COMPONENTS"
612 .ta \w'ExtraBigProfileName 'u
613 ^Path:~^To determine the user's nmh directory
614 ^Draft\-Folder:~^To find the default draft-folder
615 ^Aliasfile:~^For a default alias file
616 ^Signature:~^To determine the user's mail signature
617 ^mailproc:~^Program to post failure notices
618 ^postproc:~^Program to post the message
619 ^sendfrom-address:~^Switches to post for sender address
620 ^sendfrom-domain:~^Switches to post for sender domain name
639 .RB ` file "' defaults to <mh-dir>/draft"
640 .RB ` \-alias "' defaults to %nmhetcdir%/MailAliases"
641 .RB ` \-nodraftfolder '
647 .RB ` "\-messageid\ localname" '
651 .RB ` "\-width\ 72" '
657 Under some configurations, it is not possible to monitor the mail delivery
660 is a no-op on those systems.
projects / nmh / blob