source: trunk/athena/bin/discuss/mclient/dsmail.1 @ 11346

Revision 11346, 3.0 KB checked in by danw, 26 years ago (diff)
Add Message-ID and MIME headers to the list of default (-d) headers to keep
Line 
1.TH DSMAIL SIPB "12 Feb 93" "Student Information Processing Board"
2.SH NAME
3dsmail \- discuss mail feed program
4.SH SYNOPSIS
5.B dsmail
6[
7.B \-dAD
8] [
9.B \-a
10.I regexp
11] [
12.B \-r
13.I regexp
14] [
15.B \-s
16.I subject-match-limit
17]
18.B meeting-path-name
19
20.SH DESCRIPTION
21.I Dsmail
22is used to feed incoming mail into the discuss conferencing system.
23It takes a mail message from standard input, formats it, and inserts
24it into the proper discuss meeting.  The user running
25.B dsmail
26must have ``write'' permission for that meeting.  Typically this will
27be daemon, since sendmail runs as daemon.  To enter replies, the user
28must have ``answer`` permission for that meeting.
29.PP
30To setup a mail feed for a meeting, do the following:  Give the user
31daemon ``answer'', ``status'', and ``write''access using the discuss command
32.BR set_acl .
33Then, insert a pipe to
34.B dsmail
35into the sendmail aliases file /usr/lib/aliases.  For example:
36.in +0.5i
37tytso@charon.LOCAL:"/site/sipb/bin/dsmail -d
38/usr/spool/discuss/mailtest"@charon.LOCAL
39.in
40Then, any mail sent to
41.I tytso@charon.LOCAL
42will be entered in the meeting
43.IR mailtest .
44.PP
45If desired, dsmail will process the mail headers, and remove the
46unnecessary cruft.  If no options are specified, all of the mail
47headers are stripped.  By using the options detailed below, you can
48have fine control over which headers should be retained:
49.TP
50.B \-d
51will cause
52.B dsmail
53to retain the ``default'' fields.  These are the to, from, cc, and
54date fields, the Message-Id field, the MIME-related fields, and any
55other fields ending in ``-to'' or ``-from''.
56.TP
57.B \-A
58causes ALL fields to be retained.  This can be modified by the
59.B \-r
60option.
61.TP
62.B \-a \fIregexp
63causes any fields matching the specified regular expression to be
64accepted.
65.TP
66.B \-r \fIregexp
67causes any fields matching the specified regular expression to be
68rejected.
69.TP
70.B \-s \fIsubject-match-limit
71specifies that subject matching should be used to chain transactions. 
72If this option is specified, the last subject-match-limit number of
73transactions are searched backwards to find a matching subject.  If found, the
74transaction is chained to the given transaction.  Daemon should have either
75``read'' or ``owner'' access to the meeting for this to work.
76.TP
77.B \-D
78turns on the debugging mode.  In this mode, the mail message is not
79entered into the discuss meeting.  Instead, it is sent to standard
80output so that the formatting of the mail messages can be checked
81easily.   This option should only be used interactively.
82
83.SH "IN-REPLY-TO"
84dsmail parses the ``In-reply-to'' field in the mail header for
85transaction numbers of the form ``[nnnn] in meeting name''.  If one is
86found where the given meeting name matches the short or long name of
87the meeting, the transaction chained to that transaction number.  If a
88meeting name is not given, or the user does not have access to find
89out the long name of the meeting, the transaction is automatically
90chained to that transaction number.
91
92.SH "SEE ALSO"
93discuss(1), aliases(5)
94.SH BUGS
95Hopefully few.
Note: See TracBrowser for help on using the repository browser.