Improve wording and more description in man page spost(8)

[mmh] / man / spost.man8

diff --git a/man/spost.man8 b/man/spost.man8
index 76d10a8..c4558be 100644 (file)
--- a/man/spost.man8
+++ b/man/spost.man8
@@ -39,17 +39,21 @@ and finally feeds the message to the MTA.
 will not normally be called directly by the user.
 .PP
 .B Spost
 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
 `Fcc:', and `Resent\-xxx:' header lines of the specified
 message for destination addresses,
 .PP

-.B Sendmail
-is called witch all recipients, expect these from Bcc-field
-.br
+.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 ...
 .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
 .PP
 If a `Bcc:' field is encountered, its addresses will be used for
 delivery, and the `Bcc:' field will be removed from the message

@@ -61,13 +65,29 @@ invokes
 .B send
 to send the Bcc message.)
 .PP
 .B send
 to send the Bcc message.)
 .PP

+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
 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 will.
-The address-fields are `From:', `To:', `Bcc:',
-or rather the `Resent\-xxx:' versions of this fields.
+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
 .PP
 The
 .B \-verbose

@@ -106,10 +126,9 @@ in messages sent with
 .BR dist .
 .PP
 .B Spost
 .BR dist .
 .PP
 .B Spost

-takes care about full qualitfy addresses,
-in every address-field.
-Your MTA is supposed to care to add the correct domain,
-if there is no after aliasing.
+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 .
 .PP
 The draft is filed to the folders in the Fcc headers by
 .BR refile .

@@ -146,3 +165,15 @@ None
 
 .SH BUGS
 None
 
 .SH BUGS
 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.