Re: [Asrg] DNSBL and IPv6

Paul Smith <paul@pscs.co.uk> Thu, 25 October 2012 11:12 UTC

Return-Path: <prvs=0645E458C4=paul@pscs.co.uk>
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 5ABAE21F8998 for <asrg@ietfa.amsl.com>; Thu, 25 Oct 2012 04:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 3NDUuHW420nr for <asrg@ietfa.amsl.com>; Thu, 25 Oct 2012 04:12:16 -0700 (PDT)
Received: from mail.pscs.co.uk (mail.pscs.co.uk [188.65.177.237]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE1B21F8997 for <asrg@irtf.org>; Thu, 25 Oct 2012 04:12:14 -0700 (PDT)
Received: from lmail.pscs.co.uk ([82.68.5.206]) by mail.pscs.co.uk ([188.65.177.237] running VPOP3) with ESMTP; Thu, 25 Oct 2012 12:12:21 +0100
Received: from [192.168.66.100] ([192.168.66.100]) by lmail.pscs.co.uk ([192.168.66.70] running VPOP3) with ESMTP; Thu, 25 Oct 2012 11:50:50 +0100
Message-ID: <50891887.50103@pscs.co.uk>
Date: Thu, 25 Oct 2012 11:46:31 +0100
From: Paul Smith <paul@pscs.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <20121025024859.3176.qmail@joyce.lan> <A6AF6224-421E-4483-834B-A1F658BEC7C6@blighty.com>
In-Reply-To: <A6AF6224-421E-4483-834B-A1F658BEC7C6@blighty.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Authenticated-Sender: paul
X-Server: VPOP3 Enterprise V6.0 - Registered
X-Organisation: Paul Smith Computer Services
Cc: Steve Atkins <steve@blighty.com>
Subject: Re: [Asrg] DNSBL and IPv6
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: Thu, 25 Oct 2012 11:12:17 -0000

On 25/10/2012 04:00, Steve Atkins wrote:
> On Oct 24, 2012, at 7:48 PM, "John Levine" <johnl@taugh.com> wrote:
>
>>>> Depends what your intentions are.  If you're trying to do listwashing, you
>>>> may wall see DNSBL listings rather than bounces.  I like VERP just fine and
>>>> my lists use it, but I do get back FBL reports that are munged to the point
>>>> where I can't tell who complained.  But they rarely munge the IP.
>>> People trying to avoid listwashing will learn to munge the bottom bits of any
>>> IPv6 address.
>> Well, maybe.  Personally, I think the threat of listwashing is overstated.
>> The really slimy senders have lists so dirty that no amount of washing will
>> clean them.
>>
>> But anyway, I'm seeing a lot of assertions about how IPv6 mail will work,
>> and precious little running core or simulations.  As always, anyone want
>> to do some, you know, research?
> It's mostly dependent on how IPv6 addresses for mailservers (legitimate and
> otherwise) will be allocated, and how much IPv6 will be used for inter-domain
> email delivery. Do we have any data, or researched speculation, about that
> to work from?
>
I actually think getting any *useful* data about this would be very 
tricky at the moment, if not impossible.

I know that we can't use IPv6 anywhere. We have 4 broadband connections 
with different suppliers, and none support IPv6 yet, and the data centre 
we use for our servers also doesn't support IPv6 yet. I guess lots of 
people are in the same situation, especially smaller companies. This 
probably means that spammers in general won't be using IPv6 yet - would 
it be worth their hassle, given that most of their 'customers' won't 
have it. So, anyone who does have IPv6 MX servers will probably just be 
getting IPv6 mail from people like Google, and no one else.

So, it might be interesting to get data to see how widely IPv6 is used 
for email currently, but it's unlikely to be useful data to give us 
realistic ideas how spam will affect the IPv6 infrastructure in the 
future. eg, there may be virtually no IPv6 spam now, but it won't stay 
that way.



(My personal view is that IPv6 for widespread email use is well in the 
future. There is no huge advantage over IPv4 given that the number of 
MTAs is vastly smaller than the number of other Internet connected 
devices. For interoperability, everyone with an MTA will NEED an IPv4 
address for now. There are complexity issues especially to do with 
security, hacking protection, spam filtering etc. So, I think most mail 
admins will be leaving IPv6 turned off until they need to turn it on - 
which may take a while, since it'll be a catch-22 situation. What may 
trigger it is if someone like Google decides to turn OFF all IPv4 
support in their mail infrastructure, but I think that's unlikely for 
the foreseeable future...

MSAs may support IPv6 a lot sooner to support their IPv6 MUAs, but those 
won't have the spam issues.

I know this isn't an 'IETF approved' viewpoint, but it's mine, based on 
our customers)



-

Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53