From: Tom Watson Subject: Re: You've been selected (aka SPAM) Date: Wed, 27 Oct 2004 15:59:11 -0700 (PDT) Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: <20041027225911.68651.qmail@web60802.mail.yahoo.com> References: Reply-To: tsw@johana.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org > Message: 4 > Date: Wed, 27 Oct 2004 17:27:41 -0400 > From: Glenn Maynard > 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