Commit | Line | Data |
---|---|---|
55b91bc1 KM |
1 | .\" Copyright (c) 1983 Regents of the University of California. |
2 | .\" All rights reserved. The Berkeley software License Agreement | |
3 | .\" specifies the terms and conditions for redistribution. | |
4 | .\" | |
19438d19 | 5 | .\" @(#)bugfiler.8 6.1 (Berkeley) %G% |
55b91bc1 | 6 | .\" |
19438d19 | 7 | .TH BUGFILER 8 "" |
55b91bc1 KM |
8 | .UC 5 |
9 | .SH NAME | |
10 | bugfiler \- file bug reports in folders automatically | |
11 | .SH SYNOPSIS | |
12 | .B bugfiler | |
13 | [ mail directory ] | |
14 | .SH DESCRIPTION | |
15 | .I Bugfiler | |
16 | is a program to automatically intercept bug reports, summarize them and | |
17 | store them in the appropriate sub directories of the mail directory | |
18 | specified on the command line or the (system dependent) default. | |
19 | It is designed to be compatible with the Rand MH mail system. | |
20 | .I Bugfiler | |
21 | is normally invoked by the mail delivery program through | |
22 | .IR aliases (5) | |
23 | with a line such as the following in /usr/lib/aliases. | |
24 | .PP | |
25 | .DT | |
26 | bugs:"|bugfiler /usr/bugs/mail" | |
27 | .PP | |
28 | It reads the message from the standard input or the named file, checks | |
29 | the format and returns mail acknowledging receipt or a message | |
30 | indicating the proper format. Valid reports are then summarized and | |
31 | filed in the appropriate folder. Users can then log onto the system and | |
32 | check the summary file for bugs that pertain to them. | |
33 | Bug reports are submitted in RFC822 format and | |
34 | must contain the following header lines: | |
35 | .PP | |
36 | .DT | |
37 | Date: <date the report is received> | |
38 | .br | |
39 | From: <valid return address> | |
40 | .br | |
41 | Subject: <short summary of the problem> | |
42 | .br | |
43 | Index: <source directory>/<source file> <version> [Fix] | |
44 | .PP | |
45 | In addition, the body of the message must contain a line which | |
46 | begins with ``Description:'' followed by zero or more lines describing the | |
47 | problem in detail and a line beginning with ``Repeat-By:'' followed by zero or | |
48 | more lines describing how to repeat the problem. | |
49 | If the keyword `Fix' is specified in the `Index' line, then there must | |
50 | also be a line beginning with ``Fix:'' followed by a diff of the old and new | |
51 | source files or a description of what was done to fix the problem. | |
52 | .PP | |
53 | The `Index' line is the key to the filing mechanism. The source directory | |
54 | name must match one of the folder names in the mail directory. | |
55 | The message is then filed in this folder | |
56 | and a line appended to the summary file in the following format: | |
57 | .PP | |
58 | .DT | |
59 | <folder name>/<message number> <Index info> | |
60 | .br | |
61 | <Subject info> | |
62 | .SH FILES | |
63 | .ta 2.5i | |
64 | /usr/new/lib/mh/deliver mail delivery program | |
65 | .br | |
66 | /usr/new/lib/mh/unixtomh converts unix mail format to mh format | |
67 | .br | |
68 | maildir/.ack the message sent in acknowledgement | |
69 | .br | |
70 | maildir/.format the message sent when format errors are detected | |
71 | .br | |
72 | maildir/summary the summary file | |
73 | .br | |
74 | maildir/Bf?????? temporary copy of the input message | |
75 | .br | |
76 | maildir/Rp?????? temporary file for the reply message. | |
77 | .SH "SEE ALSO" | |
78 | mh(1), | |
79 | newaliases(1), | |
80 | aliases(5) | |
81 | .SH BUGS | |
82 | .PP | |
83 | Since mail can be forwarded in a number of different ways, | |
84 | .I bugfiler | |
85 | does not recognize forwarded mail and will reply/complain to the | |
86 | forwarder instead of the original sender unless there is a `Reply-To' | |
87 | field in the header. | |
88 | .PP | |
89 | Duplicate messages should be discarded or recognized and put somewhere | |
90 | else. |