Skip to contentSkip to conversation

You've been selected (aka SPAM)

DISCUSSION Tom Watson 3 participants 3 messages Oct 27, 2004 – Oct 28, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Tom Watson

author
#1 lore raw
Quoted 24 lines

Message: 4
Date: Wed, 27 Oct 2004 17:27:41 -0400
From: Glenn Maynard <[email protected]>
To: [email protected]
Subject: Re: [Alsa-devel] You've been selected!

Quoted 3 lines · Dan Hollis
Quoted 2 lines · Eleanor Lee

[a09fvjoqpvapktqct]
Available to anyone currently living in the US as well as international

applicants

Quoted 4 lines

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%".

Quoted 8 lines

:0
* ^X-Spam-Status: Yes
spam

Signature · 1 line
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.....

=====

Signature · 16 lines
Tom Watson
[email protected]


		
__________________________________
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
#2 lore raw
Quoted 3 lines · Tom Watson

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

The fact that digests are inflexible doesn't make suggestions like "disallow thread crossposting" and "ban an entire IP block wholesale" good ones.

Quoted 4 lines

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?

Spam filtering isn't perfect; it's up to each individual to decide for himself whether he trusts it not to lose mails (false positives), and putting the spam scanning results in a header allows this, instead of forcing it on everyone.

Signature · 8 lines
Glenn Maynard


-------------------------------------------------------
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
#3 lore raw
Quoted 8 lines · Glenn Maynard
Quoted 3 lines · Tom Watson

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

The fact that digests are inflexible doesn't make suggestions like "disallow thread crossposting" and "ban an entire IP block wholesale" good ones.

Quoted 9 lines
Quoted 4 lines

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?

Spam filtering isn't perfect; it's up to each individual to decide for himself whether he trusts it not to lose mails (false positives), and putting the spam scanning results in a header allows this, instead of forcing it on everyone.

That being said, the original poster does have a point - the result of this policy decision by Sourceforge, to add headers but not to filter, is that digest users are stuck with all the spam. There should probably be an option to filter spam out of the digests. SpamAssassin can do this, you would just pipe the digest through it deleting anything above a configurable spam score.

You should report this to Sourceforge though, I don't think the people who could implement this read alsa-devel.

Signature · 9 lines
Lee Revell <[email protected]>



-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/