![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to bugfiler.8 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8|
Return to bugfiler.8 CVS log | Up to [Power 6/32 Unix Tahoe 4.2BSD] / cci / usr / src / man / man8 |
1.1 root 1: .TH BUGFILER 8 "18 July 1983"
2: .UC 4
3: .SH NAME
4: bugfiler \- file bug reports in folders automatically
5: .SH SYNOPSIS
6: .B bugfiler
7: [ mail directory ]
8: .SH DESCRIPTION
9: .I Bugfiler
10: is a program to automatically intercept bug reports, summarize them and
11: store them in the appropriate sub directories of the mail directory
12: specified on the command line or the (system dependent) default.
13: It is designed to be compatible with the Rand MH mail system.
14: .I Bugfiler
15: is normally invoked by the mail delivery program through
16: .IR aliases (5)
17: with a line such as the following in /usr/lib/aliases.
18: .PP
19: .DT
20: bugs:"|bugfiler /usr/bugs/mail"
21: .PP
22: It reads the message from the standard input or the named file, checks
23: the format and returns mail acknowledging receipt or a message
24: indicating the proper format. Valid reports are then summarized and
25: filed in the appropriate folder. Users can then log onto the system and
26: check the summary file for bugs that pertain to them.
27: Bug reports are submitted in RFC822 format and
28: must contain the following header lines:
29: .PP
30: .DT
31: Date: <date the report is received>
32: .br
33: From: <valid return address>
34: .br
35: Subject: <short summary of the problem>
36: .br
37: Index: <source directory>/<source file> <version> [Fix]
38: .PP
39: In addition, the body of the message must contain a line which
40: begins with ``Description:'' followed by zero or more lines describing the
41: problem in detail and a line beginning with ``Repeat-By:'' followed by zero or
42: more lines describing how to repeat the problem.
43: If the keyword `Fix' is specified in the `Index' line, then there must
44: also be a line beginning with ``Fix:'' followed by a diff of the old and new
45: source files or a description of what was done to fix the problem.
46: .PP
47: The `Index' line is the key to the filing mechanism. The source directory
48: name must match one of the folder names in the mail directory.
49: The message is then filed in this folder
50: and a line appended to the summary file in the following format:
51: .PP
52: .DT
53: <folder name>/<message number> <Index info>
54: .br
55: <Subject info>
56: .SH FILES
57: .ta 2.5i
58: /usr/new/lib/mh/deliver mail delivery program
59: .br
60: /usr/new/lib/mh/unixtomh converts unix mail format to mh format
61: .br
62: maildir/.ack the message sent in acknowledgement
63: .br
64: maildir/.format the message sent when format errors are detected
65: .br
66: maildir/summary the summary file
67: .br
68: maildir/Bf?????? temporary copy of the input message
69: .br
70: maildir/Rp?????? temporary file for the reply message.
71: .SH "SEE ALSO"
72: mh(1),
73: newaliases(1),
74: aliases(5)
75: .SH BUGS
76: .PP
77: Since mail can be forwarded in a number of different ways,
78: .I bugfiler
79: does not recognize forwarded mail and will reply/complain to the
80: forwarder instead of the original sender unless there is a `Reply-To'
81: field in the header.
82: .PP
83: Duplicate messages should be discarded or recognized and put somewhere
84: else.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.