All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Nick Rout <nick@rout.co.nz>
Cc: alsa-devel@alsa-project.org
Subject: Re: spam and this list
Date: Wed, 13 Jul 2005 23:02:47 -0400	[thread overview]
Message-ID: <1121310167.4435.138.camel@mindpipe> (raw)
In-Reply-To: <20050714144842.170F.NICK@rout.co.nz>

On Thu, 2005-07-14 at 14:51 +1200, Nick Rout wrote:
> Why does this list get so much spam? Does it accept email from
> non-subscribers?
> 
> If it does, it bloody well shouldn't!
> 

Yes, it has to so people on the kernel list can cc: this list without
having to be subscribed.  And it actually gets very little spam, like a
handful of messages a day.

Finally, every list message has headers like this:

X-Spam-Score: 1.0 (+)
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 1.0
FORGED_RCVD_HELO Received: contains a forged HELO 0.0
SF_CHICKENPOX_MINUS    BODY: Text interparsed with - 0.0
SF_CHICKENPOX_APOSTROPHE BODY: Text interparsed with ' -0.0 AWL
AWL: From: address is in the auto white-list

Lee



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar

  reply	other threads:[~2005-07-14  3:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14  2:51 spam and this list Nick Rout
2005-07-14  3:02 ` Lee Revell [this message]
2005-07-14  9:06   ` Jan Buchholz
     [not found] <20050714090953.8864212FF0@sc8-sf-spam2.sourceforge.net>
2005-07-14  9:14 ` Tom Watson
2005-07-14 14:25   ` Lee Revell

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=1121310167.4435.138.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=nick@rout.co.nz \
    /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.