.na
.HP 5
.B spost
-.RB [ \-alias
-.IR aliasfile
-.RB " | " \-noalias ]
.RB [ \-verbose " | " \-noverbose ]
.I file
.RB [ \-Version ]
will not normally be called directly by the user.
.PP
.B Spost
-searches the `To:', `Cc:', `Bcc:',
+searches the `To:', `Cc:', `Bcc:', `Dcc',
`Fcc:', and `Resent\-xxx:' header lines of the specified
message for destination addresses,
.PP
+.B Spost
+invokes
+.B sendmail
+with all recipients, except the blind ones (`Bcc:'),
+as command line arguments:
+.RS
+.B sendmail
+.B \-i
+.RB [ \-v ]
+.I recipients ...
+.RE
+.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 a newly
.B send
to send the Bcc message.)
.PP
-The
-.B \-alias
-.I aliasfile
-switch can be used to specify a file that spost
-should take aliases from. More than one file can be specified, each
-being preceded with
-.BR \-alias .
-In any event, the alias file, set with the `Aliasfile' profile entry, is
-read first.
+If a `Dcc' field is encountered, the field will be removed
+before sending the message. The Dcc recipient will receive the
+message as well, but without being mentioned in the recipient
+headers.
+.PP
+In contrast to Bcc, the Dcc recipient receives the
+same original message as all the sighted reciepients, whereas
+the Bcc recipient receives a special, newly constructed message,
+which contains the original message as an attachment.
+.PP
+Bcc is probably a good choice for a message with both sighted
+and invisible reciepients (e.g. inform someone privately about
+the message being sent). Dcc is probably a good choice for
+a message to a group of only invisible recipients (e.g. invite
+to a party).
+.PP
+The `Aliasfile' profile entry
+can be used to specify one or more files that spost
+should take aliases from.
+.PP
+Aliasing is done on any address field. Those are:
+`From:', `To:', `Cc:', `Bcc:' and `Dcc',
+or the `Resent\-xxx:' versions of these fields.
.PP
The
.B \-verbose
invocation.
.PP
.B Spost
+puts the
+.RI ` Default-From '
+profile entry in the `From:' line of the message.
+If `Default-From' is not set,
+.B spost
constructs the `From:' line of the
message from the user's login name and the full name from the GECOS field
of the passwd file.
If you specify a `From:'
line manually in the message draft.
It will be used as provided.
-However, a `Sender:' header with the user's
+A `Sender:' header with the user's
.B real
-address will be added.
+address will be added, if the `From' line don't contain a address
+from the user
+.RI ` Alternate-Mailboxes '.
.PP
Note that this applies equally to `Resent\-From:' lines
in messages sent with
.BR dist .
.PP
-Your MTA is supposed to care to fully qualitfy the addresses
-with the correct domain name.
+.B Spost
+tries to fully qualify the addresses in every address field.
+Your MTA is supposed to add the correct domain,
+if there is none after aliasing.
.PP
The draft is filed to the folders in the Fcc headers by
.BR refile .
.fi
.SH "PROFILE COMPONENTS"
-.B spost
-does
-.B NOT
-consult the user's profile.
+.fc ^ ~
+.nf
+.ta 3.5i
+.ta \w'ExtraBigProfileName 'u
+^Aliasfile:~^For default alias files
+^Default\-From:~^The default From header
+^Alternate\-Mailboxes:~^The user's addresses
+.fi
.SH "SEE ALSO"
send(1), mh\-mail(5), mh\-alias(5), mh\-tailor(5), refile(1),
None
.SH BUGS
-Spost does not qualify addresses.
-.PP
-Spost does only basic processing and checking, yet.
+None
+
+.SH HISTORY
+The
+.B spost
+in mmh-0.1 used
+.BR sendmail 's
+.I -t
+flag to have
+.B sendmail
+extract the recipients from the message headers. Now, it
+passes the recipients as command line arguments. This provides
+better compatibility to other sendmail implementations.