public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stuart MacDonald" <stuartm@connecttech.com>
To: "'Chase Venters'" <chase.venters@clientec.com>
Cc: "'Krzysztof Halasa'" <khc@pm.waw.pl>, <ellis@spinics.net>,
	"'Willy Tarreau'" <w@1wt.eu>, <linux-kernel@vger.kernel.org>
Subject: RE: [OT] RE: bogofilter ate 3/5
Date: Thu, 7 Sep 2006 18:21:06 -0400	[thread overview]
Message-ID: <08f301c6d2cb$ea2cdac0$294b82ce@stuartm> (raw)
In-Reply-To: <Pine.LNX.4.64.0609071604010.31500@turbotaz.ourhouse>

From: Chase Venters [mailto:chase.venters@clientec.com] 
> So what is the SpamCop RBL data used for then?

SpamCop uses it on their own mail service to flag messages as
potential spam and filter those out to a junk folder.

They also publish the list publicly.

So, SpamCop is blocking 0 emails.

As for third parties looking at their RBL, SpamCop specifically
recommends that the list *not* be used for blocking:
http://www.spamcop.net/fom-serve/cache/291.html

> (1) The mail _would_ be solicited because you asked for it on 
> my behalf;

So you'll be sending me your snail mail address then? Thanks.

> permission. Phony permission, perhaps, but permission nonetheless...

False permission is no permission at all. That's a widely recognised
concept; in law, life and the internet.

> On Thu, 7 Sep 2006, Stuart MacDonald wrote:
> > Things change.
> 
> Yes, and eventually Internet mail will grow up and forgery 

SMTP is growing up *right now*. The reconfig of servers to not send
unsolicted bounces/etc is part of the growing-up-ness.

The following fall into two categories:

> 1. No more bounce messages
> 4. No more deferral messages

Servers can be configed to not send these. To those whose systems are
set up in such a manner to require accepting the message before
delivery, to paraphrase Chase, "(2) Spammers would be responsible for
your misery, not the parties rejecting your bounces".

> 2. No more "Your message has been queued for moderator 
> approval" messages
> 3. No more "Thanks for contacting CrapCo, your support ticket 
> # is 238417" 
> messages
> 5. No more vacation mail
> 6. No more challenge/response systems
> 7. No more mailing lists that you can sign up to by sending mail to 
> subscribe@list.org or majordomo@list.org; all subscription and 
> unsubscription must be done through web interfaces

All of these should be sent by a human.

> can turn all auto-response systems off completely.

Yep. That's the growing up you were looking for earlier.

It looks like we disagree on the method of change required. That's
life.

..Stu


       reply	other threads:[~2006-09-07 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0609071604010.31500@turbotaz.ourhouse>
2006-09-07 22:21 ` Stuart MacDonald [this message]
2006-09-07 22:23   ` [OT] RE: bogofilter ate 3/5 Chase Venters
2006-09-08 14:25     ` Stuart MacDonald
2006-09-07 13:58 Stuart MacDonald
2006-09-07 14:01 ` [OT] " Chase Venters

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='08f301c6d2cb$ea2cdac0$294b82ce@stuartm' \
    --to=stuartm@connecttech.com \
    --cc=chase.venters@clientec.com \
    --cc=ellis@spinics.net \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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