On Thu, Dec 09, 2004 at 01:22:51PM +0100, Uwe Brauer wrote: > Hi > > Some 14 days ago I sent a bug report about that issue. > It is really urgent since I cannot install nor upgrade nor anything > right now on the system. > > Here come the bug report again, I really would appreciate any help.
1) Sending the same bug report again and again is not a good way to
persuade volunteers to help you;
2) You're in violating of the Debian Mailing List Code of Conduct. See
below.
[The following is a form letter.]
Hello,
You recently sent a message to a Debian Project mailing list to which I am
subscribed, and also included me in the To or CC header.
Please don't do this. The Debian Mailing List Code of Conduct says:
When using the Debian mailing lists, please follow these rules:
[...]
* When replying to messages on the mailing list, do not send a carbon
copy (CC) to the original poster unless they explicitly request to be
copied.
(You can review the entire Debian Mailing List Code of Conduct at
<URL:http://www.debian.org/MailingLists/>.)
Rationally interpreted, this of course includes anything that works
equivalently to a CC, such including the original poster in the To: or Bcc:
headers, forwarding the message to the original poster, or using the
"bounce" feature of some mailers to send the message again, but rewriting the
SMTP envelope to address the original poster instead of the list.
Some people feel that it is best to send email to everyone who might
possibly be interested in a message, indifferent to whom might be
subscribed to various mailing lists, be part of the expansion of various
mailing lists, be behind an SMTP exploder, and so forth -- in other words,
that it is the responsibility of the recipient of duplicate mail messages
to handle them.
The Debian Mailing List Code of Conduct does not endorse that philosophy.
There are proven limitations with using procmail rules to eliminate
duplicate message based on Message-ID, for instance. More importantly, the
Debian Mailing List Code of Conduct expects the *senders* of mail to
exercise discretion and good judgement; it does not place the burden of
pruning unwanted copies of mail messages upon the recipient. You can find
discussions of this aspect of the Mailing List Code of Conduct in the
Debian mailing lists themselves, if you are interested: please see
<URL:http://lists.debian.org/search.html> to perform a search.
The subject has come up several times over the past years, and time and
again, the existing policy has been affirmed as the wisest course of
action. Many people, myself included, use the Mail-Followup-To and
Mail-Copies-To message headers, which are honored by mail user agents such
as Mutt to control the distribution of replies to mailing lists. Using
such headers, a person can easily indicate that he does (or does not) want
to be sent copies of replies to his message. You may want to use an MUA
that honors these headers, as they are in fairly wide usage on the Debian
mailing lists, and may help you avoid mistakes resulting in inadvertent
violations of Debian's Mailing List Code of Conduct.
You can read more about the Mail-Followup-To and Mail-Copies-To message
headers at:
http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt
http://www.newsreaders.com/misc/mail-copies-to.html
Please note that no assertions of deliberate misconduct on your part are
intended by this message. It is meant only to advise you as to how to
communicate more harmoniously with people involved with the Debian Project.
Thank you for your patience with this form letter, for your respect for the
Debian Project's mailing list conventions, and for your participation in
Debian.
--
G. Branden Robinson | If you want your name spelled
Debian GNU/Linux | wrong, die.
[EMAIL PROTECTED] | -- Al Blanchard
http://people.debian.org/~branden/ |
signature.asc
Description: Digital signature
