Re: [spfbis] Clarity on location of SPF records

Dave Crocker <dhc@dcrocker.net> Tue, 16 September 2014 12:54 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: spfbis@ietfa.amsl.com
Delivered-To: spfbis@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4E481A06DE for <spfbis@ietfa.amsl.com>; Tue, 16 Sep 2014 05:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KqVhndQfMShE for <spfbis@ietfa.amsl.com>; Tue, 16 Sep 2014 05:54:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB6841A0455 for <spfbis@ietf.org>; Tue, 16 Sep 2014 05:54:19 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s8GCsGVi016823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 16 Sep 2014 05:54:19 -0700
Message-ID: <541832F6.7030005@dcrocker.net>
Date: Tue, 16 Sep 2014 05:54:14 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Scott Kitterman <spf2@kitterman.com>, spfbis@ietf.org
References: <CAC6Wms59cN0+v87dL69o10uZ7B5TnmbiX6WZf7J9C+vE11PgDw@mail.gmail.com> <54182EDD.7030508@dcrocker.net> <81eb5aa8-b6fc-471f-b25f-eb8e3cbd572f@email.android.com>
In-Reply-To: <81eb5aa8-b6fc-471f-b25f-eb8e3cbd572f@email.android.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 16 Sep 2014 05:54:19 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/spfbis/6HWoqilvc_8QlII_ldga6h8qgT8
Subject: Re: [spfbis] Clarity on location of SPF records
X-BeenThere: spfbis@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: SPFbis discussion list <spfbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spfbis>, <mailto:spfbis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spfbis/>
List-Post: <mailto:spfbis@ietf.org>
List-Help: <mailto:spfbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spfbis>, <mailto:spfbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2014 12:54:20 -0000

On 9/16/2014 5:50 AM, Scott Kitterman wrote:
> Additionally, you should publish records for any domain that show up in an rfc5321.ehelo command. This is, however, rather less commonly done.


yeah.  and that's why i made my summary 'simplistic'...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net