submit\@$gEmailDomain
. This will then be
given a number, acknowledged to the user, and forwarded to a mailing
list (if configured). If the submitter included a Package
line listing a package with a known maintainer the maintainer will get
a copy too.
The Subject
line will have
$gBug#
nnn:
added, and the
Reply-To
will be set to include both the submitter of the
report and nnn\@$gEmailDomain
.
To
field to say
nnn-done\@$gEmailDomain
instead of
nnn\@$gEmailDomain
(nnn-close
is provided as an alias for
nnn-done
).
The address of the original submitter of the $gBug report will be
included in the default To
field, because the $gBug system
included it in the Reply-To
.
`Done' messages are forwarded to a mailing list if the mailing list has been set up.
The person closing the $gBug and the person who submitted it will each get a notification about the change in status of the report.
\@$gEmailDomain
and to the original
submitter of the $gBug report. The $gBug tracking system will file the
reply with the rest of the logs for that $gBug report and forward it to
a designated mailing list. The $gBug will not be marked as done.
If you wish to send a followup message which is not appropriate for
any mailing list you can do so by sending it to
nnn-quiet\@$gEmailDomain
or
nnn-maintonly\@$gEmailDomain
, which only file it (not
forwarding it anywhere) and send it on only to the maintainer of the
package in question, respectively.
Do not use the `reply to all recipients' or `followup'
feature of your mailer unless you intend to edit down the recipients
substantially. In particular, don't send a followup message both to
nnn\@$gEmailDomain
and to
submit\@$gEmailDomain
, because the $gBug system will then
get two copies of it and each one will be forwarded to the designated
mailing list separately.
$gDefaultSeverity
by default, but can be overridden either by
supplying a Severity
line in the pseudo-header when the
$gBug is submitted (see the
instructions for reporting
$gBugs), or by using the severity
command with the
control request server.
The severity levels are:
Make sure that the To
field of your message to the author
to has only the author(s) address(es) in it; put both the person who
reported the $gBug and
nnn-forwarded\@$gEmailDomain
in the
CC
field.
Ask the author to preserve the CC
to
nnn-forwarded\@$gEmailDomain
when they reply, so that
the $gBug tracking system will file their reply with the original
report.
When the $gBug tracking system gets a message at
nnn-forwarded
it will mark the relevant $gBug as
having been forwarded to the address(es) in the To
field
of the message it gets.
You can also manipulate the `forwarded to' information by sending messages to
control\@$gEmailDomain
.
$gBadMaintHtml
control\@$gEmailDomain
.
The format of these messages is
described in another document available on the World Wide Web or in
the file bug-maint-mailcontrol.txt
. A plain text version
can also be obtained by mailing the word help
to the
server at the address above.
submit
or $gBugs
whose
Subject starts Bug#
nnn will be treated as
having been sent to nnn\@$gEmailDomain
. This is both
for backwards compatibility with mail forwarded from the old
addresses, and to catch followup mail sent to submit
by
mistake (for example, by using reply to all recipients).
A similar scheme operates for maintonly
,
done
, quiet
and forwarded
,
which treat mail arriving with a Subject tag as having been sent to
the corresponding nnn-whatever\@$gEmailDomain
address.
Messages arriving at plain forwarded
and
done
- ie, with no $gBug report number in the address - and
without a $gBug number in the Subject will be filed under `junk' and
kept for a few weeks, but otherwise ignored.
Package:
secondary header field may
become mandatory - at the moment omitting it just produces a warning
message.