-.\"
+.TH SEND %manext1% 2017-05-11 "%nmhversion%"
+.
.\" %nmhwarning%
-.\"
-.TH SEND %manext1% "August 14, 2016" "%nmhversion%"
+.
.SH NAME
-send \- send a message
+send \- send an nmh message
.SH SYNOPSIS
.HP 5
.na
.B send
+.RB [ \-help ]
+.RB [ \-version ]
.RB [ \-alias
.IR aliasfile ]
.RB [ \-draft ]
.IR port-name/number ]
.RB [ \-sasl ]
.RB [ \-nosasl ]
-.RB [ \-saslmaxssf
-.IR ssf ]
.RB [ \-saslmech
.IR mechanism ]
.RB [ \-authservice
.RB [ \-tls ]
.RB [ \-initialtls ]
.RB [ \-notls ]
+.RB [ \-certverify ]
+.RB [ \-nocertverify ]
.RB [ \-width
.IR columns ]
.RB [ file
\&...]
-.RB [ \-version ]
-.RB [ \-help ]
.ad
.SH DESCRIPTION
-.B Send
+.B send
will cause each of the specified files to be delivered
to each of the destinations in the \*(lqTo:\*(rq, \*(lqcc:\*(rq,
\*(lqBcc:\*(rq, \*(lqDcc:\*(rq, and \*(lqFcc:\*(rq fields of the message. If
.B send
-is re\-distributing a message, as invoked from
+is re-distributing a message, as invoked from
.BR dist ,
then the
corresponding \*(lqResent\-xxx\*(rq fields are examined instead.
will scan the message draft for a header named
.IR Attach .
The draft is converted to a MIME message if one or more matches are found.
-This conversion occurs before all other processing. The
+This conversion occurs before all other processing.
.IR whatnow (1)
-man page describes the user interface for managing MIME attachments via
+describes the user interface for managing MIME attachments via
this mechanism.
.PP
The first part of the MIME message is the draft body if that body contains
.IR mhshow (1)
for more details and example syntax.
.PP
-Each attached MIME part contains a
+Each attached MIME part contains a
\*(lqContent-Description\*(rq header that includes the filename, and
adds a \*(lqContent-Disposition\*(rq header.
Here is an example of MIME part headers for an attachment:
the
.B nmh
draft folder facility. This is an advanced (and highly
-useful) feature. Consult the
+useful) feature. Consult
.IR mh-draft (5)
-man page for more
+for more
information.
.PP
If
tells it how long
to pause between postings.
.PP
-.B Send
+.B send
with no
.I file
argument will query whether the draft
mail transport method is not in use, its addresses will be used for
delivery, and the \*(lqDcc:\*(rq field will be removed from the message. The
blind recipients will receive the same message sent to the sighted
-recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
+recipients. *WARNING* Recipients listed in the \*(lqDcc:\*(rq field receive no
explicit indication that they have received a \*(lqblind copy\*(rq.
This can cause blind recipients to
inadvertently reply to all of the sighted recipients of the
.B \-filter
.I filterfile
is specified, then this copy is filtered
-(re\-formatted) by
+(re-formatted) by
.B mhl
prior to being sent to the blind recipients.
Alternately, if you specify the
.PP
If
.B send
-is re\-distributing a message (when invoked by
+is re-distributing a message (when invoked by
.BR dist ),
then \*(lqResent\-\*(rq will be prepended to each of these
fields: \*(lqFrom:\*(rq, \*(lqDate:\*(rq, and \*(lqMessage\-ID:\*(rq.
.PP
If a message with multiple \*(lqFrom:\*(rq
addresses does
-.B NOT
+.I not
include a \*(lqSender:\*(rq field but does include an \*(lqEnvelope\-From:\*(rq
field, the \*(lqEnvelope\-From:\*(rq field will be used to construct
a \*(lqSender:\*(rq field.
.PP
-When using SMTP for mail submission, the envelope\-from used for the SMTP
+When using SMTP for mail submission, the envelope-from used for the SMTP
transaction is derived from the \*(lqEnvelope\-From:\*(rq field.
If no \*(lqEnvelope\-From:\*(rq field is present, the \*(lqSender:\*(rq
field is used. If neither the \*(lqEnvelope\-From:\*(rq nor the
the appended fields and field reformatting. The \*(lqFcc:\*(rq fields
will be removed from all outgoing copies of the message.
.PP
+Beware that if an \*(lqFcc:\*(rq with one or more folders is present
+but none of the folders exist, and the default
+.I fileproc
+and
+.I postproc
+are in use, then
+.B refile
+will prompt the user to create the folder(s) if
+.B \-push
+is not specified. If all responses are negative, or creation of each folder
+fails, or
+.B \-push
+is specified, the message will not be copied to any folder and will be
+removed by
+.BR post .
+With the default
+.B refile
+switches, the message draft will be renamed according to the specification
+of its
+.B \-nolink
+switch.
+.PP
By using the
.B \-width
.I columns
.PP
The mail transport system default is provided in
.I %nmhetcdir%/mts.conf
-but can be overriiden here with the
+but can be overridden here with the
.B \-mts
switch.
.PP
.B \-port
switches can be used to override the default mail server (defined by the
.I %nmhetcdir%/mts.conf
-.RI servers
+.I servers
entry). The
.B \-snoop
switch can be used to view the SMTP transaction. (Beware that the
SMTP transaction may contain authentication information either in
plaintext or easily decoded base64.) If
-.B \-saslmech xoauth2
+.B \-sasl \-saslmech xoauth2
is used, the HTTP transaction is also shown.
.PP
If
SASL mechanism used, this may require an additional password prompt from the
user (but the
.I netrc
-file can be used to store this password, as described in the
-mh-profile(5) man page). The
+file can be used to store this password, as described in
+.IR mh-profile (5).
+The
.B \-saslmech
switch can be used to select a particular SASL mechanism,
and the
.B \-user
switch can be used to select a authorization userid to provide to SASL
-other than the default. The credentials profile entry in the
-mh\-profile(5) man page describes the ways to supply a username and
+other than the default. The credentials profile entry in
+.IR mh\-profile (5)
+describes the ways to supply a username and
password.
.PP
If SASL authentication is successful,
-.BR nmh
+nmh
will attempt to negotiate a security layer for session encryption.
Encrypted data is labelled with `(encrypted)' and `(decrypted)' when
viewing the SMTP transaction with the
.B \-snoop
-switch; see the
-.B post
-man page description of
+switch; see
+.IR post (8)'s
+description of
.B \-snoop
-for its other features. The
-.B \-saslmaxssf
-switch can be used to select the maximum value of the Security Strength Factor.
-This is an integer value and the exact meaning of this value depends on the
-underlying SASL mechanism. A value of 0 disables encryption.
+for its other features.
.PP
If
.B nmh
has been compiled with OAuth support, the
+.B \-sasl
+and
.B \-saslmech xoauth2
-switch will enable OAuth authentication. The
+switches will enable OAuth authentication. The
.B \-user
switch must be used, and the
-.I user-name
+.I username
must be an email address the user has for the service, which must
be specified with the
.B \-authservice
.I service
-switch. Before using this, the user must authorize nmh by running
+switch. Before using OAuth authentication, the user must authorize nmh by
+running
.B mhlogin
-and grant authorization to that account. See the
-.B mhlogin
-man page for more details.
+and grant authorization to that account. See
+.IR mhlogin (1)
+for more details.
.PP
If
.B nmh
will negotiate TLS immediately after the connection has
taken place, before any SMTP commands are sent or received. Encrypted data
is labelled with `(tls-encrypted)' and
-`(tls-decrypted)' when viewing the SMTP transction with the
+`(tls-decrypted)' when viewing the SMTP transaction with the
.B \-snoop
-switch; see the
-.B post
-man page description of
+switch; see
+.IR post (8)'s
+description of
.B \-snoop
for its other features.
The
SMTPS (SMTP over SSL) was deregistered by IANA in 1998, it is still
used for that service.
.PP
+When using TLS the default is to verify the remote certificate and SubjectName
+against the local trusted certificate store. This can be controlled by
+the
+.B \-certverify
+and
+.B \-nocertverify
+switches. See your OpenSSL documentation for more information on certificate
+verification.
+.PP
The files specified by the profile entry \*(lqAliasfile:\*(rq and any
additional alias files given by the
.B \-alias
.PP
.nf
.RS 5
-sendfrom-gmail_address@example.com: -saslmech xoauth2
+sendfrom-gmail_address@example.com: -sasl -saslmech xoauth2
.RS 5
-authservice gmail -tls -server smtp.gmail.com
-user gmail_login@example.com
.RE
.fi
.PP
-For more information on authentication to mail servers, see the
+For more information on authentication to mail servers, see
.IR mhlogin (1)
-man page for OAuth services, and
+for OAuth services, and
.IR mh-profile (5)
-man page for login credentials.
+for login credentials.
.PP
.SH FILES
.fc ^ ~
.nf
.ta \w'%nmhetcdir%/ExtraBigFileName 'u
-^$HOME/\&.mh\(ruprofile~^The user profile
+^$HOME/.mh_profile~^The user profile
.fi
.SH "PROFILE COMPONENTS"
.fc ^ ~
.ta 2.4i
.ta \w'ExtraBigProfileName 'u
^Path:~^To determine the user's nmh directory
-^Draft\-Folder:~^To find the default draft\-folder
+^Draft\-Folder:~^To find the default draft-folder
^Aliasfile:~^For a default alias file
^Signature:~^To determine the user's mail signature
^mailproc:~^Program to post failure notices
.IR mhbuild (1),
.IR mhparam (1),
.IR mhlogin (1),
+.IR refile (1),
.IR repl (1),
.IR whatnow (1),
.IR mh\-alias (5),
.IR post (8)
.SH DEFAULTS
.nf
-.RB ` file "' defaults to <mh\-dir>/draft"
+.RB ` file "' defaults to <mh-dir>/draft"
.RB ` \-alias "' defaults to %nmhetcdir%/MailAliases"
.RB ` \-nodraftfolder '
.RB ` \-nofilter '
.RB ` \-noverbose '
.RB ` \-nowatch '
.RB ` "\-width\ 72" '
+.RB ` \-certverify '
.fi
.SH CONTEXT
None
projects / nmh / blobdiff