From owner-freebsd-questions@FreeBSD.ORG Wed Feb 19 12:02:49 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E526280 for ; Wed, 19 Feb 2014 12:02:49 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D0D131DBE for ; Wed, 19 Feb 2014 12:02:48 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s1JC2gSu040408; Wed, 19 Feb 2014 12:02:44 GMT (envelope-from freebsd@qeng-ho.org) Message-ID: <53049D62.8030903@qeng-ho.org> Date: Wed, 19 Feb 2014 12:02:42 +0000 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Darren Pilgrim , freebsd-questions@freebsd.org Subject: Re: Reverse DNS question References: <20140218180620.0807880cf0dd661482e394b9@3dresearch.com> <5303F01C.3030205@bluerosetech.com> <53047301.4050201@qeng-ho.org> <201402191119.02667.mark.tinka@seacom.mu> <5304930A.6080004@bluerosetech.com> In-Reply-To: <5304930A.6080004@bluerosetech.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2014 12:02:49 -0000 On 19/02/2014 11:18, Darren Pilgrim wrote: > On 2/19/2014 1:19 AM, Mark Tinka wrote: >> On Wednesday, February 19, 2014 11:01:53 AM Arthur Chance >> wrote: >> >>> Slightly changing the topic, does anyone have any idea >>> how IPv6 is going to affect use of RDNS for spam >>> prevention? Given that machines will often have multiple >>> addresses, do we have to bolt down our MTAs to using >>> specific publicly visible addresses, or is RDNS just >>> going to get dropped. I don't have an IPv6 system to >>> play with yet. >> >> From a spam prevention perspective, nothing changes, >> operationally. >> >> My expectation is that mail server operators will require >> similar checks in IPv6. > > Google has made IPv6 RDNS effectively mandatory for communicating with > gmail servers. Thank you. That was the sort of information I was after. So we will have to tell our MTAs to use specific addresses as opposed to wildcard binding.