linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Harding <cdharding@comcast.net>
To: Linux Kernel Discussion List <linux-kernel@vger.kernel.org>
Subject: Re: E-cards for You
Date: Tue, 22 Feb 2005 00:48:06 -0800	[thread overview]
Message-ID: <421AF1C6.2030902@comcast.net> (raw)
In-Reply-To: <20050217225246.GH23467@freenet.de>

[-- Attachment #1: Type: text/plain, Size: 3074 bytes --]

Michelle Konzack wrote:

>Sorry ?
>
>I remember, that for some month I have gotten minimum 15 SPAMs per
>day from this List. Siche two (???) month it is very silent here..
>
>  
>
I am subscribed to several of the vger.kernel.org lists and the *same* 
spam gets dumped on each of them.
I have *no* problem whatsoever having the lists be open to posting so 
that anyone having a problem with
getting the kernel or other parts of Linux to work for them will be able 
to access the collective knowlege of
the community. But, my desktop machine is capable of identifying the 
garbage that gets dumped on the lists
without much problem. I am using a triple layered approach - 
SpamAssassin, SpamBayes, and SpamBouncer,
to filter all of my incoming mail. This approach works very well in that 
it has a miniscule false-positive rate, yet
catches all of the 419, phish, E-cards, etc, etc, etc, that get sent to 
the list. I am only an end-user in that I do
not control the mailservers that receive the spams from vger.kernel.org 
but my setup can certainly identify
without fail the junk sent through the lists. So my question is really, 
if my puny little end-user setup can determine
which messages sent to /whatever-list@/vger.kernel.org are spam, why 
can't the admins at vger.kernel.org
set up the same kind of filtering so that the junk never even gets into 
the outbound majordomo queue? I've
set up majordomo and I know how the internals work and how messages get 
run through the architecture.
I know it's possible to filter the incoming messages *to* majordomo. The 
spam is coming through majordomo
through the list. If you expand your MUA's view of the message so that 
you see all of the headers in the
message, you will see that the spammage goes through the same processing 
as any other legitimate message.
Your two-address scheme has other functionality in play to explain the 
difference in the number of spam message
are received. I am only talking about messages processed through 
majordomo@vger.kenel.org

>I think, there was an Admin which had changed the SPAM-Filter setings.
>
>But one thing:
>
>I an subscribed with two E-Mails to this list, the first one is
>secret and get all the mails from the List... SPAM is very rarely.
>
>The second E-Mail is, which I use to post here... and on which I
>get per day between 300 and 6000 SPAMs.
>
>I run my own spamassassin on my FileServer for all incoming Messges
>and see only 5-20 messages coming through my filters.
>
>Same for the 56 Debian mailinglist where I am subscribed.
>
>I do not know, what happen if kernel.org and debian.org deactivate
>the filters... maybe the Internet connection will not sufficiant to
>distribute the SPAM.
>
>
>Greetings
>Michelle
>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-= Charles D. (Chuck) Harding <cdharding@comcast.SPAM.ME.AND.DIE.net> =-
-= Livermore, CA USA   K6CKT  DOD#1408  http://www.harding-family.org =-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Manual Writer's Creed:  Garbage in, gospel out.


[-- Attachment #2: Signature.txt --]
[-- Type: text/plain, Size: 340 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-= Charles D. (Chuck) Harding <cdharding@comcast.SPAM.ME.AND.DIE.net> =-
-= Livermore, CA USA   K6CKT  DOD#1408  http://www.harding-family.org =-
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Manual Writer's Creed:  Garbage in, gospel out.

  reply	other threads:[~2005-02-22  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-17 14:35 E-cards for You e-cards
2005-02-17 21:20 ` James Colannino
2005-02-17 21:52   ` Gene Heskett
2005-02-17 22:03     ` Chuck Harding
2005-02-17 22:23       ` Thomas Gleixner
2005-02-17 22:35       ` Lee Revell
2005-02-17 22:37       ` Matti Aarnio
2005-02-17 22:52       ` Michelle Konzack
2005-02-22  8:48         ` Chuck Harding [this message]
2005-02-22  9:47           ` Thomas Gleixner
2005-02-17 23:26   ` Marco Iannantuoni

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=421AF1C6.2030902@comcast.net \
    --to=cdharding@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).