[mmh] / man / send.man1

.\"
.\" %nmhwarning%
.\"
.TH SEND %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
.SH NAME
send \- send a message
.SH SYNOPSIS
.HP 5
.na
.B send
.RB [ \-verbose " | " \-noverbose ]
.RB [ msg
\&...]
.RB [ \-Version ]
.RB [ \-help ]
.ad
.SH DESCRIPTION
.B Send
will cause each of the specified messages to be delivered
to each of the destinations in the `To:', `Cc:',
`Bcc:', `Dcc:', and `Fcc:' fields of the message.  If
.B send
is re\-distributing a message, as invoked from
.BR dist ,
then the
corresponding `Resent\-xxx' fields are examined instead.
.PP
.B send
uses the program
.B spost
to do the actual delivery of the messages.
Most of the features attributed to
.B send
are actually performed by
.BR spost .
.PP
The draft is scanned for attachment header fields.
Their name defaults to ``Attach'', but may be changed by the value of the
.I Attachment-Header
profile entry.
If such header fields are found, or the body contains non-ASCII characters,
the message is converted to a MIME message.
This conversion occurs before all other processing.
.PP
The first part of the MIME message is the draft body if the body is non-empty.
The body of each attachment header field is interpreted as a file name,
and each file named is included as a separate part in the MIME message.
.PP
The MIME type of each file is determined by the MIME type query program,
as defined by the
.I Mime-Type-Query
profile entry.
Mmh distributes the program
.BR print-mimetype ,
in case no better alternative is available on the system.
.PP
The last component of the path name is taken as the name of the MIME parts.
A message part header for an attachment might be:
.PP
.nf
Content-Type: text/plain; name="VERSION"; charset="us-ascii"
Content-Description: VERSION
Content-Disposition: attachment; filename="VERSION"
.fi
.PP
If
.B \-verbose
is specified,
.B send
will request verbose information of the transport system.
.PP
.B Send
with no
.I msg
argument will send the current message in the draft folder.
.B Send
always takes messages from the draft folder.
(But, a
.I +folder
argument might be added in the future.)
Consult the
.BR mh-draft (7)
man page for more information.
.PP
Once the transport system has successfully accepted custody of the
message, the message will be renamed with a leading comma, which allows
it to be retrieved until the next draft message is sent.  If there are
errors in the formatting of the message,
.B send
will abort with a
(hopefully) helpful error message.
.PP
If a `Bcc:' field is encountered, its addresses will be used for
delivery, and the `Bcc:' field will be removed from the message
sent to sighted recipients.  The blind recipients will receive an entirely
new message with a minimal set of headers.  Included in the body of the
message will be a copy of the message sent to the sighted recipients.
.PP
If a `Dcc:' field is encountered, its addresses will be used for
delivery, and the `Dcc:' 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 `Dcc:' field receive no
explicit indication that they have received a `blind copy'.
This can cause blind recipients to
inadvertently reply to all of the sighted recipients of the
original message, revealing that they received a blind copy.
On the other hand, since a normal reply to a message sent
via a `Bcc:' field
will generate a reply only to the sender of the original message,
it takes extra effort in most mailers to reply to the included
message, and so would usually only be done deliberately, rather
than by accident.
.PP
Prior to sending the message, the fields `From:\ user@local',
and `Date:\ now' will be appended to the headers in the message.
If the environment variable
.B $SIGNATURE
is set, then its value
is used as your personal name when constructing the `From:'
line of the message.  If this environment variable is not set, then
.B send
will consult the profile entry `Signature' for
this information.
.PP
If
.B send
is re\-distributing a message (when invoked by
.BR dist ),
then `Resent\-' will be prepended to each of these
fields: `From:', `Date:', and `Message\-ID:'.
If the message already contains a `From:' field, then a
`Sender: user@local' field will be added as well.  (An already
existing `Sender:' field is an error!)
.PP
If an `Fcc:\ folder' is encountered, the message will be copied
to the specified folder for the sender in the format in which it will
appear to any non\-Bcc receivers of the message.  That is, it will have
the appended fields and field reformatting.  The `Fcc:' fields
will be removed from all outgoing copies of the message.
.PP
The files specified by the profile entry `Aliasfile:' will be read.
See
.BR mh\-alias (5)
for more information.

.SH FILES
.fc ^ ~
.nf
.ta \w'%etcdir%/ExtraBigFileName  'u
^$HOME/.mmh/profile~^The user profile
^+drafts~^The draft folder
.fi

.SH "PROFILE COMPONENTS"
.fc ^ ~
.nf
.ta 2.4i
.ta \w'ExtraBigProfileName  'u
^Path:~^To determine the user's mail storage
^Draft\-Folder:~^To set the default draft\-folder
^Aliasfile:~^For a default alias file
^Signature:~^To determine the user's mail signature
^Attachment\-Header:~^To set the name of the attachment header field
^Mime\-Type\-Query:~^Program to determine the MIME types of files
.fi

.SH "SEE ALSO"
comp(1), dist(1), forw(1), repl(1), mh\-alias(5), spost(8)

.SH DEFAULTS
.nf
.RB ` msg "' defaults to the current message in the draft folder"
.RB ` \-noverbose '
.fi

.SH CONTEXT
None

.SH BUGS
None