IETF Logo Mail Archive

Re: [ietf-smtp] [Shutup] chained authorizationm, was Proposed Charter for the "SMTP Headers ...

Dave Crocker <dhc@dcrocker.net> Mon, 30 November 2015 16:46 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 913D11AD0A5; Mon, 30 Nov 2015 08:46:44 -0800 (PST)
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 g7mjKaJojGdS; Mon, 30 Nov 2015 08:46:42 -0800 (PST)
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 DAC131AD0A3; Mon, 30 Nov 2015 08:46:42 -0800 (PST)
Received: from [192.168.1.87] (76-218-10-206.lightspeed.sntcca.sbcglobal.net [76.218.10.206]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id tAUGkg32009367 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Mon, 30 Nov 2015 08:46:42 -0800
References: <20151130162124.13748.qmail@ary.lan>
To: ietf-smtp@ietf.org, shutup@ietf.org
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <565C7D72.4050100@dcrocker.net>
Date: Mon, 30 Nov 2015 08:46:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <20151130162124.13748.qmail@ary.lan>
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.17]); Mon, 30 Nov 2015 08:46:42 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-smtp/U4vFQZYddvT9hnMA_2yyHSbV6hQ>
Subject: Re: [ietf-smtp] [Shutup] chained authorizationm, was Proposed Charter for the "SMTP Headers ...
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2015 16:46:44 -0000

On 11/30/2015 8:21 AM, John Levine wrote:
>> If you're relaying the email on to somewhere else then you're assuming
>> that there's a mechanism by which your policy regarding SPF becomes
>> known to those other people.
>>
>> I'm unaware of such a mechanism existing at the moment --
> 
> That's more or less what Authentication-Results and the deprecated
> Received-SPF headers do, recording a snapshot of what the SPF results
...

Probably relevant, current work:

     Authenticated Received Chain (ARC)
     https://tools.ietf.org/html/draft-andersen-arc-00

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email