From: Matti Aarnio <matti.aarnio@zmailer.org>
To: "Dhr N. Van Alphen" <mastex@servicez.org>
Cc: Jim Roland <jroland@roland.net>, linux-kernel@vger.kernel.org
Subject: Re: The spam problem.
Date: Mon, 12 Aug 2002 11:42:58 +0300 [thread overview]
Message-ID: <20020812084258.GT32427@mea-ext.zmailer.org> (raw)
In-Reply-To: <001c01c241bd$37fbabe0$0200010a@jennifer>
Good morning,
Please refrain from fights on email issues while I am asleep..
DaveM is in California, I am in Finland. About 9-10 hours
time difference there. (depending on our personal rythms, also.)
On Mon, Aug 12, 2002 at 07:00:46AM +0200, Dhr N. Van Alphen wrote:
> cause there would be many non-members who wanna post bugs but can't because
> they dont have access maybe?
>
> I suggest too block every email adres wich sends crap, easy done.
Consider:
- Number of faked source addresses
- Number of cases using somebody's address
- Number of throw-away addresses
- How many times they use HOTMAIL/YAHOO/EMAIL/MAIL/... addresses ?
I think I will stick to the (weakish) method of matching texts in
message body (and sometimes on headers)..
I just reviewed Majordomo's BOUNCE log. It is bouncing (into oblivion)
practically every posting from HOTMAIL (because of Received: header
text: "from mail pickup service", which appears also in a number of
looped messages..)
Over past 3 days Majordomo has trapped ONE of those money-scam
letters. A lot more of various other spams have been blocked.
Messages with HTML content don't make it into VGER at all, which
should give a very big clue to legitimate posters making a mistake
of posting such.
I am very worried of trapping too much. A bit of leakage is (to me)
accptable, but similar amounts of falsely trapped ones I don't like.
I also receive so much spam directly, that I don't always detect every
instance when it is leaking thru VGER's lists. If you want to raise
the attention of VGERs postmasters, I suggest you forward it to:
postmaster@vger.kernel.org
with subject: "leaked spam"
Also, in case of non-english spam, I would like to receive suggestions
for PERL RE patterns matching juicy keywords in the messages.
(To me Chinese or Russian texts are just line noise...)
> Niek van alphen
> mastex@servicez.org
/Matti Aarnio
next prev parent reply other threads:[~2002-08-12 8:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 1:44 Hell.Surfers
2002-08-12 1:36 ` David S. Miller
2002-08-12 2:22 ` David D. Hagood
2002-08-12 2:12 ` David S. Miller
2002-08-12 2:48 ` David D. Hagood
2002-08-12 3:56 ` [OT] " Rik van Riel
2002-08-12 4:41 ` Jim Roland
2002-08-12 4:50 ` Rik van Riel
2002-08-12 5:11 ` David S. Miller
2002-08-12 8:47 ` Willy Tarreau
2002-08-12 9:09 ` [OT] " Manik Raina
2002-08-12 13:58 ` Rik van Riel
2002-08-12 14:31 ` Richard B. Johnson
2002-08-12 15:09 ` Martin J. Bligh
2002-08-12 23:45 ` Paul Jakma
[not found] ` <5.1.0.14.2.20020812064112.00b6b9c0@pop.gmx.net>
2002-08-12 4:48 ` Jim Roland
2002-08-12 5:00 ` Dhr N. Van Alphen
2002-08-12 8:42 ` Matti Aarnio [this message]
2002-08-12 5:12 ` David S. Miller
2002-08-12 11:23 ` Richard B. Johnson
2002-08-12 3:04 Hell.Surfers
2002-08-12 2:54 ` David S. Miller
2002-08-12 3:18 ` David D. Hagood
2002-08-12 5:15 Jim Roland
2002-08-12 7:35 ` David Schwartz
2002-08-12 7:50 ` David S. Miller
2002-08-12 13:50 ` Rik van Riel
2002-08-13 18:25 ` Benjamin LaHaise
2002-08-12 20:24 ` Thunder from the hill
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=20020812084258.GT32427@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=jroland@roland.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mastex@servicez.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
all inboxes | Powered by JetHome®