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