1BUGFILER(8) System Manager's Manual BUGFILER(8)
2
6 bugfiler - file bug reports in folders automatically
7
9 bugfiler [ mail directory ]
10
12 Bugfiler is a program to automatically intercept bug reports, summarize
13 them and store them in the appropriate sub directories of the mail
14 directory specified on the command line or the (system dependent)
15 default. It is designed to be compatible with the Rand MH mail system.
16 Bugfiler is normally invoked by the mail delivery program through
17 aliases(5) with a line such as the following in /etc/aliases.
18 bugs:"|bugfiler /usr/bugs/mail"
20 It reads the message from the standard input or the named file, checks
22 the format and returns mail acknowledging receipt or a message indicat‐
23 ing the proper format. Valid reports are then summarized and filed in
24 the appropriate folder; improperly formatted messages are filed in a
25 folder named ``errors.'' Program maintainers can then log onto the
26 system and check the summary file for bugs that pertain to them. Bug
27 reports should be submitted in RFC822 format and aremust contain the
28 following header lines to be properly indexed:
29 Date: <date the report is received>
31 From: <valid return address>
32 Subject: <short summary of the problem>
33 Index: <source directory>/<source file> <version> [Fix]
34 In addition, the body of the message must contain a line which begins
36 with ``Description:'' followed by zero or more lines describing the
37 problem in detail and a line beginning with ``Repeat-By:'' followed by
38 zero or more lines describing how to repeat the problem. If the key‐
39 word `Fix' is specified in the `Index' line, then there must also be a
40 line beginning with ``Fix:'' followed by a diff of the old and new
41 source files or a description of what was done to fix the problem.
42 The `Index' line is the key to the filing mechanism. The source direc‐
44 tory name must match one of the folder names in the mail directory.
45 The message is then filed in this folder and a line appended to the
46 summary file in the following format:
47 <folder name>/<message number> <Index info>
49 <Subject info>
50 The bug report may also be redistributed according to the index. If
52 the file maildir/.redist exists, it is examined for a line beginning
53 with the index name followed with a tab. The remainder of this line
54 contains a comma-separated list of mail addresses which should receive
55 copies of bugs with this index. The list may be continued onto multi‐
56 ple lines by ending each but the last with a backslash (`\').
57
59 /usr/sbin/sendmail mail delivery program
60 /usr/libexec/unixtomh converts unix mail format to mh format
61 maildir/.ack the message sent in acknowledgement
62 maildir/.format the message sent when format errors are
63 detected
64 maildir/.redist the redistribution list
65 maildir/summary the summary file
66 maildir/Bf?????? temporary copy of the input message
67 maildir/Rp?????? temporary file for the reply message.
68
70 mh(1), newaliases(1), aliases(5)
71
73 Since mail can be forwarded in a number of different ways, bugfiler
74 does not recognize forwarded mail and will reply/complain to the for‐
75 warder instead of the original sender unless there is a `Reply-To'
76 field in the header.
77 Duplicate messages should be discarded or recognized and put somewhere
79 else.
804.2 Berkeley Distribution October 23, 1996 BUGFILER(8)