Re: [Asrg] How will we manage IPv6 spam?
Michael Thomas <mike@mtcc.com> Fri, 17 August 2012 21:04 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 E013C11E80E1 for <asrg@ietfa.amsl.com>;
Fri, 17 Aug 2012 14:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level:
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[AWL=-0.075,
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 A1nTHzGEKJMc for
<asrg@ietfa.amsl.com>; Fri, 17 Aug 2012 14:04:34 -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 583E411E80D1 for <asrg@irtf.org>;
Fri, 17 Aug 2012 14:04:34 -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
q7HL4X4a026139 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256
verify=NO); Fri, 17 Aug 2012 14:04:33 -0700
Message-ID: <502EB1E1.6050807@mtcc.com>
Date: Fri, 17 Aug 2012 14:04:33 -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>
In-Reply-To: <Pine.GSO.4.64.1208171642250.8836@nber6>
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=1193; t=1345237473;
x=1346101473; 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=VM4i6ZQ74ZcQ6RrOauF3hkhKpx3HaissedKwe3+RhqE=;
b=qdtrmnWR2EuGDqGEEbCCY3A+xWwNlbXdWeFYByY6XMxhbDsNekZwa0fWdC
NuLquq5lQCG6Z3OsUFcfCwSzvWVCH4P5mq+ef6IT0Kb//+vF2KCi1Ktw9LuQ
KPW3tNKDBkL+iZ69tLEZOLX1S1y9/CQjBUZ0tfziiwTO4rU+imM1E=;
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
Cc: Daniel Feenberg <feenberg@nber.org>
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: Fri, 17 Aug 2012 21:04:35 -0000
On 08/17/2012 01:51 PM, Daniel Feenberg wrote: > > > On Fri, 17 Aug 2012, John R. Levine wrote: > >> Hi. Remember the ASRG? I was hoping it might do a little research. >> >> In talking to people about IPv6 mail, I'm still coming to the conclusion that anyone who thinks they know how they're going to handle it, beyond the current toy scale, doesn't understand the problem. Things we might address include: >> > > I would not expect to accept any IPv6 mail until users come forward to show me that they wish to correspond with MTAs that have no IPv4 connection ability. While this may happen in the fullness of time, I don't expect it soon. Now and for the foreseeable future such a system would have very little connectivity, far less than a blacklisted spam source. 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. 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