From: Wakko Warner <wakko@animx.eu.org>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Confirmation Spam Blocking was: List 'linux-dvb' closed to public posts
Date: Wed, 21 Jan 2004 18:01:54 -0500 [thread overview]
Message-ID: <20040121175954.A1343@animx.eu.org> (raw)
In-Reply-To: <20040121213027.GN23765@srv-lnx2600.matchmail.com>; from Mike Fedyk on Wed, Jan 21, 2004 at 01:30:27PM -0800
> What do you think about individual email (non-list) using a confirmation
> based spam blocking system.
Consider a spammer using your address and spams people. Say 25000 of those
use this method (Called challenge response authentication protocol). You'll
get bombarded with 25000 challenge message.
You put the burden on the sender, not the spammer which is pretty much
useless. There was a discussion about this on exim-users and someone posted
a web page. http://kmself.home.netcom.com/Rants/challenge-response.html
> I currently use spamassassin to filter my messages, but I saw recently a
> project that asks you to reply to a confirmation message if you're not
> already on the white-list.
>
> I'm not sure how acceptable it would be, and this is a little OT, but I'm
> wondering if I should spend the time testing that for my corp.
I for one refuse to answer those challenges unless I know it was due to a
spammer. Defeats the purpose.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2004-01-21 22:50 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ecartis-01212004203954.14209.1@mail.convergence2.de>
2004-01-21 19:43 ` List 'linux-dvb' closed to public posts Dave Jones
2004-01-21 19:54 ` Christoph Hellwig
2004-01-21 19:56 ` Linus Torvalds
2004-01-21 19:56 ` Dave Jones
2004-01-21 20:12 ` John Bradford
2004-01-21 21:44 ` Jes Sorensen
2004-01-22 5:11 ` Rik van Riel
2004-01-21 20:38 ` Zan Lynx
2004-01-21 20:57 ` Charles Cazabon
2004-01-21 21:57 ` Diego Calleja
2004-01-21 21:15 ` Dave Jones
2004-01-21 21:29 ` Randy.Dunlap
2004-01-21 21:30 ` [OT] Confirmation Spam Blocking was: " Mike Fedyk
2004-01-21 22:50 ` Adrian Bunk
2004-01-21 23:01 ` Wakko Warner [this message]
2004-01-22 6:51 ` Jan-Benedict Glaw
2004-01-22 14:31 ` Wakko Warner
2004-01-21 23:40 ` Andreas Jellinghaus
2004-01-22 0:26 ` Zan Lynx
2004-01-22 5:14 ` Rik van Riel
2004-01-22 13:24 ` Jes Sorensen
2004-01-22 16:56 ` David Ford
2004-01-22 17:01 ` Trond Myklebust
2004-01-22 17:10 ` David Ford
2004-01-22 17:35 ` Trond Myklebust
2004-01-22 18:18 ` Andreas Jellinghaus
2004-01-22 17:11 ` Andreas Jellinghaus
2004-01-22 17:30 ` viro
2004-01-22 17:34 ` Ralf Hildebrandt
2004-01-22 17:41 ` David Ford
2004-01-22 18:20 ` Brian Beattie
2004-01-23 7:41 ` Willy Tarreau
2004-01-23 9:24 ` Paul Jakma
2004-01-22 18:35 ` David Lang
2004-01-22 18:49 ` David Ford
2004-01-22 22:18 ` jw schultz
2004-01-22 22:58 ` Linus Torvalds
2004-01-22 23:16 ` Linus Torvalds
2004-01-23 6:49 ` David S. Miller
2004-01-23 15:38 ` Chris Ricker
2004-01-23 9:25 ` Paul Jakma
2004-01-23 19:38 ` Pavel Machek
2004-01-22 22:43 ` Scott Laird
2004-01-24 20:14 ` Kevin O'Connor
2004-01-24 21:12 ` Linus Torvalds
2004-01-24 23:25 ` Kevin O'Connor
[not found] ` <1hDmg-4AP-9@gated-at.bofh.it>
2004-01-24 23:59 ` Russ Allbery
2004-01-22 22:15 ` Krzysztof Halasa
2004-01-23 8:43 ` Jes Sorensen
2004-01-26 22:58 ` Max Valdez
2004-01-23 9:17 ` Paul Jakma
2004-01-22 5:13 ` Rik van Riel
2004-01-21 23:08 ` Russell King
2004-01-22 13:28 ` Theodore Ts'o
2004-01-21 22:13 ` Linus Torvalds
2004-01-21 23:01 ` Marcus Metzler
2004-01-22 14:14 ` Johannes Stezenbach
2004-01-22 15:14 ` Marcus Metzler
2004-01-22 15:31 ` Johannes Stezenbach
2004-01-21 23:21 ` Stephen Hemminger
2004-01-22 15:15 ` Michael Hunold
2004-01-22 15:18 ` Dave Jones
2004-01-21 20:08 ` Valdis.Kletnieks
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=20040121175954.A1343@animx.eu.org \
--to=wakko@animx.eu.org \
--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