From: Glenn Maynard <glenn@zewt.org>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Re: You've been selected (aka SPAM)
Date: Wed, 27 Oct 2004 23:44:49 -0400 [thread overview]
Message-ID: <20041028034449.GF1904@zewt.org> (raw)
In-Reply-To: <20041027225911.68651.qmail@web60802.mail.yahoo.com>
On Wed, Oct 27, 2004 at 03:59:11PM -0700, Tom Watson wrote:
> 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.
> 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.
--
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
next prev parent reply other threads:[~2004-10-28 3:44 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 ` You've been selected (aka SPAM) Tom Watson
2004-10-28 3:44 ` Glenn Maynard [this message]
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=20041028034449.GF1904@zewt.org \
--to=glenn@zewt.org \
--cc=alsa-devel@lists.sourceforge.net \
/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