Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Watson <sdc695@yahoo.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: You've been selected (aka SPAM)
Date: Wed, 27 Oct 2004 15:59:11 -0700 (PDT)	[thread overview]
Message-ID: <20041027225911.68651.qmail@web60802.mail.yahoo.com> (raw)
In-Reply-To: <E1CMwWX-0000Tt-9j@sc8-sf-list2.sourceforge.net>

> Message: 4
> Date: Wed, 27 Oct 2004 17:27:41 -0400
> From: Glenn Maynard <glenn@zewt.org>
> To: alsa-devel@lists.sourceforge.net
> Subject: Re: [Alsa-devel] You've been selected!
> 
> On Wed, Oct 27, 2004 at 02:21:05AM -0700, Dan Hollis wrote:
> > On Wed, 27 Oct 2004, Eleanor Lee wrote:
> > > [a09fvjoqpvapktqct]
> > > Available to anyone currently living in the US as well as international
> applicants
> > 
> > time to allow only registered subscribers to post to the list, perhaps?
> > 
> > alsa-devel is now 99% spam :-(
> 
> This is the second time (in a brief period) where I've seen you whining
> about spam, when I never even saw the spam itself.  As Lee pointed out,
> there's a SpamAssassin header right there; use it.  Allowing posts from
> non-subscribers is very useful; stop asking that it be disabled simply
> because you won't use existing spam filtering mechanisms.  I see perhaps
> one spam or spam-related bounce per page of 50 mails on this list--and
> that's *after* filtering out BTS messages--a far cry from your "99%".
> 
> :0
> * ^X-Spam-Status: Yes
> 	spam
> 
> -- 
> Glenn Maynard
> 
> 

Glenn...

Unfortunately the digester (or whatever assembles the group of messages into a
digest) DOES NOT forward SpamAssassin Headers.  It treats ALL messages as
equal.  This means that the digest traffic has more visable SPAM in it.  I
suspect that what everyone would like (as suggested before) is to get
sourceforge to do the filtering.  If it were done there, us users (regular and
digest ones) wouldn't need to do it.  Why do the filtering for every subscriber
when it can be done once at the source.  Isn't that logical?

My understanding is that sourceforge doesn't do the filtering (or won't do it)
for some reason.  Why, I don't know.

For the moment I will live with it.  We all live with it to some degree.

If you want to experiment, just use another address and subscribe in the digest
format.  You will readly see the problem.  I'm not really complaining about the
problem, but your answer of "Look at the headers" is FAR from universal.

Enough.....

=====
-- 
Tom Watson
tsw@johana.com


		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

       reply	other threads:[~2004-10-27 22:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CMwWX-0000Tt-9j@sc8-sf-list2.sourceforge.net>
2004-10-27 22:59 ` Tom Watson [this message]
2004-10-28  3:44   ` Re: You've been selected (aka SPAM) Glenn Maynard
2004-10-28 21:00     ` 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=20041027225911.68651.qmail@web60802.mail.yahoo.com \
    --to=sdc695@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox