CC: undisclosed-recipients: ;
MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-35155-1402013179-994.36210-3-0@isc.org>
Content-Disposition: inline
References: <RT-Ticket-36210@isc.org> <rt-3.8.6-35155-1402013179-994.36210-3-0@isc.org>
Message-ID: <20140606011413.GA82956@isc.org>
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) by bugs.isc.org (Postfix) with ESMTP id 647222D20051 for <bind9-review@bugs.isc.org>; Fri,  6 Jun 2014 01:14:13 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id 4BA33216C31; Fri,  6 Jun 2014 01:14:13 +0000 (UTC)
Delivered-To: bind9-review@bugs.isc.org
User-Agent: Mutt/1.4.2.3i
Subject: Re: [ISC-Bugs #36210] Warn for missing spf TXT record when type SPF exists
Return-Path: <each@isc.org>
X-Original-To: bind9-review@bugs.isc.org
Date: Fri, 6 Jun 2014 01:14:13 +0000
To: Mark Andrews via RT <bind9-review@isc.org>
From: Evan Hunt <each@isc.org>
RT-Message-ID: <rt-3.8.6-35155-1402017254-1717.36210-0-0@isc.org>
Content-Length: 77

Should we consider synthesizing a missing TXT as well as logging a warning?