From owner-freebsd-questions@FreeBSD.ORG Wed Feb 19 11:18:34 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 56E6FBD4 for ; Wed, 19 Feb 2014 11:18:34 +0000 (UTC) Received: from luigi.brtsvcs.net (luigi.brtsvcs.net [IPv6:2607:fc50:1000:1f00::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 33242197F for ; Wed, 19 Feb 2014 11:18:34 +0000 (UTC) Received: from chombo.houseloki.net (c-76-115-19-22.hsd1.or.comcast.net [76.115.19.22]) by luigi.brtsvcs.net (Postfix) with ESMTPSA id B55F42D4FD4; Wed, 19 Feb 2014 03:18:32 -0800 (PST) Received: from [IPv6:2601:7:880:bd0:4dc6:fe9a:fceb:5eeb] (unknown [IPv6:2601:7:880:bd0:4dc6:fe9a:fceb:5eeb]) by chombo.houseloki.net (Postfix) with ESMTPSA id 16DC03CD; Wed, 19 Feb 2014 03:18:30 -0800 (PST) Message-ID: <5304930A.6080004@bluerosetech.com> Date: Wed, 19 Feb 2014 03:18:34 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: mark.tinka@seacom.mu, 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> In-Reply-To: <201402191119.02667.mark.tinka@seacom.mu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Arthur Chance 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 11:18:34 -0000 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.