From: Lee Revell <rlrevell@joe-job.com>
To: tsw@johana.com
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Bug reports forwarded to the 'alsa-devel' list
Date: Thu, 21 Oct 2004 15:20:29 -0400 [thread overview]
Message-ID: <1098386429.3705.3.camel@krustophenia.net> (raw)
In-Reply-To: <20041021095327.47067.qmail@web60803.mail.yahoo.com>
On Thu, 2004-10-21 at 05:53, Tom Watson wrote:
> I'd mention more about spam, but that is not as annoying (or preventable) as
> the quoted-printable mess.
Every message to alsa-devel contains a header like this:
X-Spam-Report: Spam Filtering performed by sourceforge.net. See
http://spamassassin.org/tag/ for more details. Report problems to
http://sf.net/tracker/?func=add&group_id=1&atid=200001 0.3
NO_REAL_NAME From: does not include a real name 0.0
SF_CHICKENPOX_SLASH BODY: Text interparsed with / 0.0
SF_CHICKENPOX_MINUS BODY: Text interparsed with - 0.0
SF_CHICKENPOX_APOSTROPHE BODY: Text interparsed with ' 0.0
SF_CHICKENPOX_PERIOD BODY: Text interparsed with . 0.0
SF_CHICKENPOX_QUESTION BODY: Text interparsed with ?
Please, stop complaining about spam on alsa-devel. Use the URL in the
X-Spam-Report header. That is what it's for.
Lee
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
prev parent reply other threads:[~2004-10-21 19:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CKTh2-00070Z-E2@sc8-sf-list2.sourceforge.net>
2004-10-21 9:53 ` Bug reports forwarded to the 'alsa-devel' list Tom Watson
2004-10-21 11:09 ` Jaroslav Kysela
2004-10-21 19:22 ` Lee Revell
2004-10-22 11:20 ` Jaroslav Kysela
2004-10-21 19:20 ` Lee Revell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1098386429.3705.3.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tsw@johana.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.