Re: [Asrg] 0.General - News Article - NYT Reports Porn Spam Hijacking Network

"Jon Kyme" <jrk@merseymail.com> Wed, 16 July 2003 08:30 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20923 for <asrg-archive@odin.ietf.org>; Wed, 16 Jul 2003 04:30:42 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19chfz-0002I5-VB for asrg-archive@odin.ietf.org; Wed, 16 Jul 2003 04:30:16 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6G8UF54008801 for asrg-archive@odin.ietf.org; Wed, 16 Jul 2003 04:30:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19chfz-0002HK-2K for asrg-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 04:30:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20874; Wed, 16 Jul 2003 04:29:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19chfk-0004di-00; Wed, 16 Jul 2003 04:30:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19chfe-0004df-00; Wed, 16 Jul 2003 04:29:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19chem-00028Y-RY; Wed, 16 Jul 2003 04:29:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cheC-00027h-T3 for asrg@optimus.ietf.org; Wed, 16 Jul 2003 04:28:24 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20835 for <asrg@ietf.org>; Wed, 16 Jul 2003 04:28:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cheA-0004aW-00 for asrg@ietf.org; Wed, 16 Jul 2003 04:28:22 -0400
Received: from argon.connect.org.uk ([193.110.243.33]) by ietf-mx with esmtp (Exim 4.12) id 19chdz-0004aI-00 for asrg@ietf.org; Wed, 16 Jul 2003 04:28:11 -0400
Received: from mmail by argon.connect.org.uk with local (connectmail/exim) id 19chde-0005JR-00 for asrg@ietf.org; Wed, 16 Jul 2003 09:27:50 +0100
In-Reply-To: <C61148CA-B710-11D7-8867-00039380F1B6@pobox.com>
Subject: Re: [Asrg] 0.General - News Article - NYT Reports Porn Spam Hijacking Network
To: ASRG <asrg@ietf.org>
From: Jon Kyme <jrk@merseymail.com>
X-Mailer: [ConnectMail 3.5.10]
X-connectmail-Originating-IP: 172.25.243.3
Message-Id: <E19chde-0005JR-00@argon.connect.org.uk>
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Wed, 16 Jul 2003 09:27:50 +0100

> 
> So you're proposing that ISPs be required to run something like 
> SpamAssassin on all *outgoing* e-mail, and bounce e-mail back at the 
> user if it looks like spam?
> 

This is a real live issue for providers of (for instance) free webmail
services. I'm familiar with a situation where the admin overhead of
investigating and terminating accounts following abuse allegations is
making this kind of outbound filtering look very attractive. I realise that
free webmail is a special case, but it's clear that the volume limits
imposed by many such providers are a step along this road.


> I see a problem with that--will users accept it, or will they take 
> their money elsewhere? I know that when *I* send an e-mail, I expect it 
> to be sent--if my ISP bounces it back because they don't like the 
> content, it's time for me to find another ISP.
>

Most (if not all) ISP have AUP which prohibit the use of their systems for
sending spam. I suspect that if a customer had a lot of trouble with
outbound content filtering it would be because either;
(a) their ISP does filtering badly - in which case you're right, the
customer would walk, or (b) the customer *is* a spammer.

I believe that it is in the long-term interests of ISP to keep spammers off
their networks. The consequences of blacklisting on legitimate customers
can support arguments for outbound filtering.

I don't see how you'd "require" ISP to use this, perhaps you might choose
to whitelist ISP who assert that they do.
 






--

_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg