+++ /dev/null
-You've misdirected an email to owner@bugs.debian.org or one of the
-aliases that points to it. This email address is only for reporting
-problems with the Debian bug tracking system itself, including reports
-of spam that is archived in the Debian bug tracking system.
-
-For general information on Debian, see: http://www.debian.org/
-
-To discuss things without submitting a specific bug, please use
-an appropriate mailing list such as debian-user@lists.debian.org .
-For a list of Debian mailing lists, see: http://lists.debian.org/
-
-To contact the maintainer of package foobar, send email to
-foobar@packages.debian.org .
-
-To report a new bug please follow the instructions on
-http://www.debian.org/Bugs/Reporting to submit a bug report. The
-reportbug command is the recommended way. If you don't know what
-package to report the bug on, use your best guess or report it to an
-appropriate pseudo-package.
-
-To send information about an existing bug 123, send email to
-123@bugs.debian.org . To send to the submitter of 123, use
-123-submitter@bugs.debian.org . If the bug is archived (closed for 28
-days with no new information) you need to request to
-owner@bugs.debian.org to unarchive the bug.
-
-http://www.debian.org/Bugs/ can be used to search the Debian bug
-database by various criteria.
-
-If you are trying to unsubscribe, view the headers of the mail that
-was sent you and follow the unsubscription information there. In the
-cases where you are the submitter of a bug, there is no unsubscription
-information, and you need to use the control interface to change the
-submitter or send a mail to -done to close your bug. See the
-documentation above for information on how to do that.
+++ /dev/null
-As a rule we do not modify bug reports that have been submitted to the
-BTS. This includes deleting content, masking e-mails or otherwise
-hiding information that has been submitted to the BTS.
-
-The only modifications that we do make are removing messages which are
-obviously spam.
-
-If you are concerned about your e-mail address being made public by
-continuing to be present on bugs.debian.org, it is already too late.
-Every message that is sent to the BTS is broadcast to a number of
-mailing lists and mirrored throughout the internet. Spammers are known
-to be subscribed to these mailing lists.
-
-Instead, we strongly suggest that you invest in anti spam software
-like spamassassin or similar, as removing or otherwise munging
-information will not stem the tide of spam at all.
-
-Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63995 et
-al. if you have more questions about this.
+++ /dev/null
-You've misdirected an email to owner@bugs.debian.org or one of the
-aliases that points to it. This email address is only for reporting
-problems with the Debian bug tracking system itself, including reports
-of spam that is archived in the Debian bug tracking system.
-
-For general information on Debian, see: http://www.debian.org/
-
-To discuss things without submitting a specific bug, please use
-an appropriate mailing list such as debian-user@lists.debian.org .
-For a list of Debian mailing lists, see: http://lists.debian.org/
-
-To contact the maintainer of package foobar, send email to
-foobar@packages.debian.org .
-
-To report a new bug please follow the instructions on
-http://www.debian.org/Bugs/Reporting to submit a bug report. The
-reportbug command is the recommended way. If you don't know what
-package to report the bug on, use your best guess or report it to an
-appropriate pseudo-package.
-
-To send information about an existing bug 123, send email to
-123@bugs.debian.org . To send to the submitter of 123, use
-123-submitter@bugs.debian.org . If the bug is archived (closed for 28
-days with no new information) you need to request to
-owner@bugs.debian.org to unarchive the bug.
-
-http://www.debian.org/Bugs/ can be used to search the Debian bug
-database by various criteria.
-
-If you are trying to unsubscribe, view the headers of the mail that
-was sent you and follow the unsubscription information there. In the
-cases where you are the submitter of a bug, there is no unsubscription
-information, and you need to use the control interface to change the
-submitter or send a mail to -done to close your bug. See the
-documentation above for information on how to do that.
+++ /dev/null
-You've misdirected an email to owner@bugs.debian.org or one of the
-aliases that points to it. This email address is only for reporting
-problems with the Debian bug tracking system itself, including reports
-of spam that is archived in the Debian bug tracking system.
-
-To send information about an existing bug 123, send email to
-123@bugs.debian.org . To send to the submitter of 123, use
-123-submitter@bugs.debian.org . If the bug is archived (closed for 28
-days with no new information) you need to request to
-owner@bugs.debian.org to unarchive the bug.
-
-http://www.debian.org/Bugs/ can be used to search the Debian bug
-database by various criteria.
+++ /dev/null
-You've misdirected an email to owner@bugs.debian.org or one of the
-aliases that points to it. This email address is only for reporting
-problems with the Debian bug tracking system itself, including reports
-of spam that is archived in the Debian bug tracking system.
-
-If you are trying to unsubscribe, view the headers of the mail that
-was sent you and follow the unsubscription information there. In the
-cases where you are the submitter of a bug, there is no unsubscription
-information, and you need to use the control interface to change the
-submitter or send a mail to -done to close your bug. See
-http://www.debian.org/Bugs/server-control for information on how to do
-that.
--- /dev/null
+You've misdirected an email to owner@bugs.debian.org or one of the
+aliases that points to it. This email address is only for reporting
+problems with the Debian bug tracking system itself, including reports
+of spam that is archived in the Debian bug tracking system.
+
+For general information on Debian, see: http://www.debian.org/
+
+To discuss things without submitting a specific bug, please use
+an appropriate mailing list such as debian-user@lists.debian.org .
+For a list of Debian mailing lists, see: http://lists.debian.org/
+
+To contact the maintainer of package foobar, send email to
+foobar@packages.debian.org .
+
+To report a new bug please follow the instructions on
+http://www.debian.org/Bugs/Reporting to submit a bug report. The
+reportbug command is the recommended way. If you don't know what
+package to report the bug on, use your best guess or report it to an
+appropriate pseudo-package.
+
+To send information about an existing bug 123, send email to
+123@bugs.debian.org . To send to the submitter of 123, use
+123-submitter@bugs.debian.org . If the bug is archived (closed for 28
+days with no new information) you need to request to
+owner@bugs.debian.org to unarchive the bug.
+
+http://www.debian.org/Bugs/ can be used to search the Debian bug
+database by various criteria.
+
+If you are trying to unsubscribe, view the headers of the mail that
+was sent you and follow the unsubscription information there. In the
+cases where you are the submitter of a bug, there is no unsubscription
+information, and you need to use the control interface to change the
+submitter or send a mail to -done to close your bug. See the
+documentation above for information on how to do that.
--- /dev/null
+As a rule we do not modify bug reports that have been submitted to the
+BTS. This includes deleting content, masking e-mails or otherwise
+hiding information that has been submitted to the BTS.
+
+The only modifications that we do make are removing messages which are
+obviously spam.
+
+If you are concerned about your e-mail address being made public by
+continuing to be present on bugs.debian.org, it is already too late.
+Every message that is sent to the BTS is broadcast to a number of
+mailing lists and mirrored throughout the internet. Spammers are known
+to be subscribed to these mailing lists.
+
+Instead, we strongly suggest that you invest in anti spam software
+like spamassassin or similar, as removing or otherwise munging
+information will not stem the tide of spam at all.
+
+Please see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63995 et
+al. if you have more questions about this.
--- /dev/null
+You've misdirected an email to owner@bugs.debian.org or one of the
+aliases that points to it. This email address is only for reporting
+problems with the Debian bug tracking system itself, including reports
+of spam that is archived in the Debian bug tracking system.
+
+For general information on Debian, see: http://www.debian.org/
+
+To discuss things without submitting a specific bug, please use
+an appropriate mailing list such as debian-user@lists.debian.org .
+For a list of Debian mailing lists, see: http://lists.debian.org/
+
+To contact the maintainer of package foobar, send email to
+foobar@packages.debian.org .
+
+To report a new bug please follow the instructions on
+http://www.debian.org/Bugs/Reporting to submit a bug report. The
+reportbug command is the recommended way. If you don't know what
+package to report the bug on, use your best guess or report it to an
+appropriate pseudo-package.
+
+To send information about an existing bug 123, send email to
+123@bugs.debian.org . To send to the submitter of 123, use
+123-submitter@bugs.debian.org . If the bug is archived (closed for 28
+days with no new information) you need to request to
+owner@bugs.debian.org to unarchive the bug.
+
+http://www.debian.org/Bugs/ can be used to search the Debian bug
+database by various criteria.
+
+If you are trying to unsubscribe, view the headers of the mail that
+was sent you and follow the unsubscription information there. In the
+cases where you are the submitter of a bug, there is no unsubscription
+information, and you need to use the control interface to change the
+submitter or send a mail to -done to close your bug. See the
+documentation above for information on how to do that.
--- /dev/null
+You've misdirected an email to owner@bugs.debian.org or one of the
+aliases that points to it. This email address is only for reporting
+problems with the Debian bug tracking system itself, including reports
+of spam that is archived in the Debian bug tracking system.
+
+To send information about an existing bug 123, send email to
+123@bugs.debian.org . To send to the submitter of 123, use
+123-submitter@bugs.debian.org . If the bug is archived (closed for 28
+days with no new information) you need to request to
+owner@bugs.debian.org to unarchive the bug.
+
+http://www.debian.org/Bugs/ can be used to search the Debian bug
+database by various criteria.
--- /dev/null
+You've misdirected an email to owner@bugs.debian.org or one of the
+aliases that points to it. This email address is only for reporting
+problems with the Debian bug tracking system itself, including reports
+of spam that is archived in the Debian bug tracking system.
+
+If you are trying to unsubscribe, view the headers of the mail that
+was sent you and follow the unsubscription information there. In the
+cases where you are the submitter of a bug, there is no unsubscription
+information, and you need to use the control interface to change the
+submitter or send a mail to -done to close your bug. See
+http://www.debian.org/Bugs/server-control for information on how to do
+that.
--- /dev/null
+To enable us investigating errors or problems you should provide us
+with more information.
+
+Helpful would be: (we don't need all, provide as much as possible)
+
+ * the IP,
+ * the Time (including timezone),
+ * the Message-Id,
+ * the Adresses you sent from and to,
+ * maybe some more things that could be related with that problem.
+
+We maintain a system with more than 150000 subscribers which gets
+and sends a lot more than 1000000 Mails a day, without that
+information we have no chance to find out what went wrong.
--- /dev/null
+The Debian-Listarchives-Policy is to NOT remove or alter any postings
+if they are published.
+
+Even if we would, it wouldn't help, as our lists are archived
+elsewhere, so once an email has been accepted it is out in the wild
+with its entire content and addresses and theres no way to get it back.
+
+Please see http://www.debian.org/MailingLists/#disclaimer and
+http://www.debian.org/MailingLists/disclaimer
--- /dev/null
+To enable us to investigate errors or problems you should provide us
+with the following information (or as much of it as possible):
+
+ * the IP,
+ * the Time (including timezone),
+ * the Message-Id,
+ * the Adresses you sent from and to,
+ * anything else that you think would help
+
+We maintain a system with more than 150,000 subscribers which receives
+and sends more than 1,000,000 mails a day. Without the information
+above we have little chance of finding out what went wrong.
--- /dev/null
+Please follow the guidelines for new lists at
+
+http://www.debian.org/MailingLists/HOWTO_start_list
+
+After filing the request, it would be very much appreciated if several
+other people interested in the new list would send a mail to the bug,
+in order to record their interest.
+
--- /dev/null
+listmaster@lists.debian.org is for reporting problems related to the
+operation of mailing lists hosted on lists.debian.org.
+
+If you have problems or questions about running Debian, please
+consider posting to debian-user@lists.debian.org. If you have a
+general non-technical project-related query, consider posting to
+debian-project@lists.debian.org.
+
+You can also see http://www.debian.org/support and
+http://lists.debian.org/ for information on other support resources
+and mailing lists.
+
--- /dev/null
+Your mail address isn't on any of our lists.
+
+If you still receive mails from our servers please check the headers
+of the mail carefully. The recipient-address is coded into the
+Return-Path.
+
+Example:
+
+Return-Path: <bounce-debian-devel=don=debian.org@lists.debian.org>
+ ^^^^^^^^^^^^^^
+
--- /dev/null
+Please see
+http://lists.debian.org/debian-devel/2006/01/msg00068.html
--- /dev/null
+We are aware that Debian-Mailinglists aren't 100% spam-free, but if
+you can't accept that, don't subscribe to our lists.
+
+http://www.debian.org/MailingLists/ also contains some hints how you
+can help us to improve the ham/Spam-ratio, you can also simply bounce
+(As in mutt) spams you get through our lists to:
+report-listspam@lists.debian.org
+
+Our filters currently stop about 50000 incoming mails per day, 2500 make it
+through to the filters, i think this is a good job.
--- /dev/null
+It appears you are reporting spam that has been sent to you through the Debian
+lists to Spamcop. Please stop doing this immediately, as it is jeopardising
+bandwidth and hosting facilities for several machines belonging to the Debian
+project.
+
+While I understand that it may seem like a lot of spam makes it through the
+Debian lists, there is a lot more that doesn't. For example, almost 1000 spam
+messages were blocked from going on the debian-laptop list daily.
+
+We will unfortunately have to blacklist you from Debian lists should
+this continue.
+
+Please let us know when this has stopped.
+
--- /dev/null
+Hi.
+
+I wonder why you tried to subscribe to a mailinglist, while you are
+already subscribed to it.
+
+Maybe you can explain?
+
+Background: I see some more people who try to add themself to already
+subscribed debian-lists, so maybe you can shed some light on it?
+
--- /dev/null
+due to several complains about you running a challenge-response system
+and sending eMails to persons posting to our lists, we decided to
+unsubscribe your address from all mailinglists on our listserver.
+
+Feel free to subscribe again to our lists after you verified that your
+challenge-response system is not hitting our users any more. Iff we find
+out you subscribed again and your challenge-response system is still up
+for mails from lists.debian.org, your address will be banned permanently
+from lists.debian.org.
+
--- /dev/null
+I have caused an unsubscription cookie to be sent to your address.
+Please follow the instructions in it to complete the unsubscription
+process.
+++ /dev/null
-To enable us investigating errors or problems you should provide us
-with more information.
-
-Helpful would be: (we don't need all, provide as much as possible)
-
- * the IP,
- * the Time (including timezone),
- * the Message-Id,
- * the Adresses you sent from and to,
- * maybe some more things that could be related with that problem.
-
-We maintain a system with more than 150000 subscribers which gets
-and sends a lot more than 1000000 Mails a day, without that
-information we have no chance to find out what went wrong.
+++ /dev/null
-The Debian-Listarchives-Policy is to NOT remove or alter any postings
-if they are published.
-
-Even if we would, it wouldn't help, as our lists are archived
-elsewhere, so once an email has been accepted it is out in the wild
-with its entire content and addresses and theres no way to get it back.
-
-Please see http://www.debian.org/MailingLists/#disclaimer and
-http://www.debian.org/MailingLists/disclaimer
+++ /dev/null
-To enable us to investigate errors or problems you should provide us
-with the following information (or as much of it as possible):
-
- * the IP,
- * the Time (including timezone),
- * the Message-Id,
- * the Adresses you sent from and to,
- * anything else that you think would help
-
-We maintain a system with more than 150,000 subscribers which receives
-and sends more than 1,000,000 mails a day. Without the information
-above we have little chance of finding out what went wrong.
+++ /dev/null
-Please follow the guidelines for new lists at
-
-http://www.debian.org/MailingLists/HOWTO_start_list
-
-After filing the request, it would be very much appreciated if several
-other people interested in the new list would send a mail to the bug,
-in order to record their interest.
-
+++ /dev/null
-listmaster@lists.debian.org is for reporting problems related to the
-operation of mailing lists hosted on lists.debian.org.
-
-If you have problems or questions about running Debian, please
-consider posting to debian-user@lists.debian.org. If you have a
-general non-technical project-related query, consider posting to
-debian-project@lists.debian.org.
-
-You can also see http://www.debian.org/support and
-http://lists.debian.org/ for information on other support resources
-and mailing lists.
-
+++ /dev/null
-Your mail address isn't on any of our lists.
-
-If you still receive mails from our servers please check the headers
-of the mail carefully. The recipient-address is coded into the
-Return-Path.
-
-Example:
-
-Return-Path: <bounce-debian-devel=don=debian.org@lists.debian.org>
- ^^^^^^^^^^^^^^
-
+++ /dev/null
-Please see
-http://lists.debian.org/debian-devel/2006/01/msg00068.html
+++ /dev/null
-We are aware that Debian-Mailinglists aren't 100% spam-free, but if
-you can't accept that, don't subscribe to our lists.
-
-http://www.debian.org/MailingLists/ also contains some hints how you
-can help us to improve the ham/Spam-ratio, you can also simply bounce
-(As in mutt) spams you get through our lists to:
-report-listspam@lists.debian.org
-
-Our filters currently stop about 50000 incoming mails per day, 2500 make it
-through to the filters, i think this is a good job.
+++ /dev/null
-It appears you are reporting spam that has been sent to you through the Debian
-lists to Spamcop. Please stop doing this immediately, as it is jeopardising
-bandwidth and hosting facilities for several machines belonging to the Debian
-project.
-
-While I understand that it may seem like a lot of spam makes it through the
-Debian lists, there is a lot more that doesn't. For example, almost 1000 spam
-messages were blocked from going on the debian-laptop list daily.
-
-We will unfortunately have to blacklist you from Debian lists should
-this continue.
-
-Please let us know when this has stopped.
-
+++ /dev/null
-Hi.
-
-I wonder why you tried to subscribe to a mailinglist, while you are
-already subscribed to it.
-
-Maybe you can explain?
-
-Background: I see some more people who try to add themself to already
-subscribed debian-lists, so maybe you can shed some light on it?
-
+++ /dev/null
-due to several complains about you running a challenge-response system
-and sending eMails to persons posting to our lists, we decided to
-unsubscribe your address from all mailinglists on our listserver.
-
-Feel free to subscribe again to our lists after you verified that your
-challenge-response system is not hitting our users any more. Iff we find
-out you subscribed again and your challenge-response system is still up
-for mails from lists.debian.org, your address will be banned permanently
-from lists.debian.org.
-
+++ /dev/null
-I have caused an unsubscription cookie to be sent to your address.
-Please follow the instructions in it to complete the unsubscription
-process.
projects / lib.git / commitdiff