Re: [Asrg] How will we manage IPv6 spam?
Michael Thomas <mike@mtcc.com> Sat, 18 August 2012 00:21 UTC
Return-Path: <mike@mtcc.com>
X-Original-To: asrg@ietfa.amsl.com
Delivered-To: asrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 4F99321F846A for <asrg@ietfa.amsl.com>;
Fri, 17 Aug 2012 17:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.672
X-Spam-Level:
X-Spam-Status: No, score=-2.672 tagged_above=-999 required=5 tests=[AWL=-0.073,
BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id na5tBx99pdWx for
<asrg@ietfa.amsl.com>; Fri, 17 Aug 2012 17:21:32 -0700 (PDT)
Received: from mtcc.com (mtcc.com [IPv6:2001:5a8:4:9fe0:224:8cff:feaa:6d9b])
by ietfa.amsl.com (Postfix) with ESMTP id 5D77821F8468 for <asrg@irtf.org>;
Fri, 17 Aug 2012 17:21:32 -0700 (PDT)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224])
(authenticated bits=0) by mtcc.com (8.14.3/8.14.3) with ESMTP id
q7I0LUJC027941 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256
verify=NO); Fri, 17 Aug 2012 17:21:30 -0700
Message-ID: <502EE00A.6050501@mtcc.com>
Date: Fri, 17 Aug 2012 17:21:30 -0700
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US;
rv:1.8.1.22) Gecko/20090605 Thunderbird/2.0.0.22 Mnenhy/0.7.5.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <alpine.BSF.2.00.1208171554300.31068@joyce.lan>
<Pine.GSO.4.64.1208171642250.8836@nber6> <502EB1E1.6050807@mtcc.com>
<Pine.GSO.4.64.1208171702000.8836@nber6> <502EDB7F.1030506@pscs.co.uk>
In-Reply-To: <502EDB7F.1030506@pscs.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1420; t=1345249291;
x=1346113291; c=relaxed/simple; s=thundersaddle.kirkwood;
h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=mtcc.com;
i=mike@mtcc.com; z=From:=20Michael=20Thomas=20<mike@mtcc.com>
|Subject:=20Re=3A=20[Asrg]=20How=20will=20we=20manage=20IPv 6=20spam?
|Sender:=20 |To:=20Anti-Spam=20Research=20Group=20-=20IRTF=20<asrg@irtf .org>
|Content-Type:=20text/plain=3B=20charset=3DISO-8859-1=3B=20 format=3Dflowed
|Content-Transfer-Encoding:=207bit |MIME-Version:=201.0;
bh=IGCI+O6+B6TU1DqMgmLk6bOm9XYaOGUVsw3GP/JE+ok=;
b=D2j9j4yU7CKXI2Ks0BHwVLjQ9tKcQRU1nD6KW1bE80hGFMgwxeNFQFJfX6
v8yx40LyxT7pp7Hyw2r6Tk3zStuWk1EioSP8lw1MncL9BYLHOVOCJ4JWJrrU
tfpLDwGbwkb54rZqrSf0Hq+nNSTz13RBIPawVBb0f5vM3PJQUVTVk=;
Authentication-Results: ; v=0.1; dkim=pass header.i=mike@mtcc.com ( sig from
mtcc.com/thundersaddle.kirkwood verified; );
dkim-asp=pass header.From=mike@mtcc.com
Subject: Re: [Asrg] How will we manage IPv6 spam?
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/options/asrg>,
<mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>,
<mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Aug 2012 00:21:33 -0000
On 08/17/2012 05:02 PM, Paul Smith wrote: > On 17/08/2012 22:08, Daniel Feenberg wrote: >> >> >> On Fri, 17 Aug 2012, Michael Thomas wrote: >> >>> On 08/17/2012 01:51 PM, Daniel Feenberg wrote: >>> >>> Host operating systems -- all of them to my knowledge -- prefer v6 over v4 if you have a public v6 address. So the mere existence of a AAAA associated with the MX will cause the sender to pick the v6 destination. I have a v6 mail system and got bitten because I had forgot to put up the v6 reverse map. It will happen just as a natural consequence of people enabling v6 on their infrastructure. >> >> This sounds inconvenient. If I want to accept mail from one IPv6 host, then all the IPv6 hosts will want to use IPv6, and unless I accept mail from unknown IPv6 hosts, mail from hosts that would have been accepted over IPv4 will be rejected? > This is a fair point. Given that IPv6 is rare at the moment and is really an 'extension' to SMTP anyway, maybe we should be looking at a further extension which allows an SMTP receiver to say 'retry on my IPv4 address' Seriously, let's not go here. Any such extension would be DOA in the IETF anyway. If DNSBL's are the reason you would want to stay in v4 land, I'd suggest the problem is with the way DNSBL's are engineered, not v6. Thislist being an IETF research group should just accept that v6 will arrive and not try to roll back time. Mike
- [Asrg] How will we manage IPv6 spam? John R. Levine
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Michael Thomas
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Paul Smith
- Re: [Asrg] How will we manage IPv6 spam? Michael Thomas
- Re: [Asrg] How will we manage IPv6 spam? John Levine
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Daniel Feenberg
- Re: [Asrg] How will we manage IPv6 spam? Paul Smith
- Re: [Asrg] How will we manage IPv6 spam? Emanuele Balla (aka Skull)
- Re: [Asrg] How will we manage IPv6 spam? SM
- Re: [Asrg] rDNS and cache issues, was How will we… John Levine
- Re: [Asrg] rDNS and cache issues, was How will we… Emanuele Balla (aka Skull)
- Re: [Asrg] rDNS and cache issues, was How will we… Matthias Leisi
- Re: [Asrg] rDNS and cache issues, was How will we… John Levine