X-Git-Url: http://git.marmaro.de/?p=mmh;a=blobdiff_plain;f=man%2Fspost.man8;h=1e962860a56bb59d44248422889ba1825a29e7c7;hp=76d10a8f21a63126645cc134d5c0f3e0d2f0555d;hb=18591f8e001ecedbee48a51c1d1f08ebaa1c15c8;hpb=00b5842e0c5feef345a8e69cdb501f8a4c5c8c0f

diff --git a/man/spost.man8 b/man/spost.man8
index 76d10a8..1e96286 100644
--- 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
-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 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 ...
+.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
@@ -61,13 +65,29 @@ invokes
 .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
-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
@@ -76,15 +96,17 @@ For example, the `\-v' switch will be added to the
 .B sendmail
 invocation.
 .PP
-.B Spost
-puts the
+If you specify a `From:' line manually in the message draft,
+it will be used as provided.
+If there is no `From:' line in the draft,
+.B spost
+uses the
 .RI ` Default-From '
-profile entry in the `From:' line of the message.
-If `Default-From' is not set,
+profile entry, if set.
+Otherwise
 .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.
+constructs the `From:' line from the user's login name
+and the full name from the GECOS field of the passwd file.
 An example is `From: Dan Harkless <dan>'.
 .PP
 If you set the
@@ -92,24 +114,24 @@ If you set the
 environment variable.
 Its value overrides the full name from the GECOS field.
 .PP
-If you specify a `From:'
-line manually in the message draft.
-It will be used as provided.
-A `Sender:' header with the user's
-.B real
-address will be added, if the `From' line don't contain a address
-from the user
+A `Sender:' header will be added in two cases.
+First, if the `From:' line given in the draft contains one or
+more addresses, of which none is the user's own one, as defined by
 .RI ` Alternate-Mailboxes '.
+(The sender address will then be determined equally as described
+above for the absent `From:' header.)
+Second, if the `From:' line contains multiple addresses, of
+which at least one is the user's own address. The first own
+address will be used as the sender address.
 .PP
 Note that this applies equally to `Resent\-From:' lines
 in messages sent with
 .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 .
@@ -129,6 +151,7 @@ None
 ^Aliasfile:~^For default alias files
 ^Default\-From:~^The default From header
 ^Alternate\-Mailboxes:~^The user's addresses
+^Sendmail:~^The path name to the sendmail program.
 .fi
 
 .SH "SEE ALSO"
@@ -146,3 +169,15 @@ 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.