From nobody Mon Sep 10 10:04:37 2018 Return-Path: X-Original-To: dmarc@ietf.org Delivered-To: dmarc@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63CDC130ED9; Mon, 10 Sep 2018 10:04:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: dmarc@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.83.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: dmarc@ietf.org Message-ID: <153659907435.16004.8029711338036070907@ietfa.amsl.com> Date: Mon, 10 Sep 2018 10:04:34 -0700 Archived-At: Subject: [dmarc-ietf] I-D Action: draft-ietf-dmarc-arc-multi-02.txt X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2018 17:04:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain-based Message Authentication, Reporting & Conformance WG of the IETF. Title : Using Multiple Signing Algorithms with the ARC (Authenticated Received Chain) Protocol Authors : Kurt Andersen Seth Blank John Levine Filename : draft-ietf-dmarc-arc-multi-02.txt Pages : 6 Date : 2018-09-10 Abstract: The Authenticated Received Chain (ARC) protocol creates a mechanism whereby a series of handlers of an email message can conduct authentication of the email message as it passes among them on the way to its destination. Initial development of ARC has been done with a single allowed signing algorithm, but RFC 8463 has expanded the supported algorithms. This specification defines how to extend ARC for multiple signing algorithms. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dmarc-arc-multi/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dmarc-arc-multi-02 https://datatracker.ietf.org/doc/html/draft-ietf-dmarc-arc-multi-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dmarc-arc-multi-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Sep 19 19:20:58 2018 Return-Path: X-Original-To: dmarc@ietfa.amsl.com Delivered-To: dmarc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7255A130DCA for ; Wed, 19 Sep 2018 19:20:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.102 X-Spam-Level: X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=CdDsYfKR; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=drIXpreq 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 Ljf4CE-UGUc4 for ; Wed, 19 Sep 2018 19:20:54 -0700 (PDT) Received: from pop3.winserver.com (ftp.catinthebox.net [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id 64856126CB6 for ; Wed, 19 Sep 2018 19:20:54 -0700 (PDT) DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=525; t=1537410042; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=6rny2Gkp4eUYAsGmRQSYK2uKRE0=; b=CdDsYfKRuhS5vP4biUcavqa46HiqSOjOwXxasWYng4A3xlMfTk/1W+eV8h5sDd 4eccqf6AT5kCk1udsbHGRcBH4DGwytnc1fD5sl6tRTuQJ6K+6kgabshW7ngUeSHn heKigIOL4TwpEcsS639cWx0O1vCE+jM/g0ajQuVQzXF9U= Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Wed, 19 Sep 2018 22:20:42 -0400 Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com; Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 1508675462.29173.9112; Wed, 19 Sep 2018 22:20:42 -0400 DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=525; t=1537409327; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=0gnoJsa d5BWHVMfR+1e09cab/hnv73cBrUMLSgjSeio=; b=drIXpreq9etdP43LfByQZZO v1x2Kz2fPSQE8lwxDfbC76qykFzd66PPPgbwqql9qjaGD+dw4IO98RGjMWhDjKGq 7uwSVVsqvVHT7wPbk7H834XBoWtIywe1i1PlfOj3eBzFrJsZYsnRIEvJ5mbUvte0 4UEwzn0ziWC8k7rUTGoU= Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Wed, 19 Sep 2018 22:08:46 -0400 Received: from [192.168.1.68] ([99.121.5.8]) by beta.winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 1250054875.9.56956; Wed, 19 Sep 2018 22:08:45 -0400 Message-ID: <5BA303DF.90505@isdg.net> Date: Wed, 19 Sep 2018 22:20:15 -0400 From: Hector Santos Organization: Santronics Software, Inc. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1 MIME-Version: 1.0 To: "dmarc@ietf.org" Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: [dmarc-ietf] List Server Rewrite From Logic X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2018 02:20:57 -0000 It is my understanding the IETF has begun to do a "rewrite" of the list poster/message RFC8322.From address of restricted DMARC domains to help resolve the IETF list subscribers distribution reject problem. If so, is there some written protocol, method or outline of what is actually being done? I am giving up trying to keep the RFC5822.From address persistent, i.e. avoid rewriting, while waiting for a better solution to materialize. I would like to finally consider it for our list server. Thanks -- HLS From nobody Wed Sep 19 20:21:27 2018 Return-Path: X-Original-To: dmarc@ietfa.amsl.com Delivered-To: dmarc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7792130DFC for ; Wed, 19 Sep 2018 20:21:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=I5tI991k; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=iCiQHhMs 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 jMfgv76PJr2J for ; Wed, 19 Sep 2018 20:21:24 -0700 (PDT) Received: from ftp.catinthebox.net (ftp.catinthebox.net [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8DF130DFB for ; Wed, 19 Sep 2018 20:21:23 -0700 (PDT) DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=887; t=1537413678; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=jM+dBlm29kUx233JtgO+oPQilc0=; b=I5tI991k7IZjrZYB9XeGK1pfzx2lp1p9hRH3HrycaY3CPFMk6D5NFra7hy9LDI J8154OuRqIocXYBfLYNXIBLM2eNCTFt1dlP8pQDSJsXtq04ZlSOigu1moQamEMJ5 UL4fDnYlQUyFZ7DPjz5NV3JjpB5W+wunjoKLs2ce083AI= Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Wed, 19 Sep 2018 23:21:18 -0400 Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com; Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 1512310503.29173.2580; Wed, 19 Sep 2018 23:21:17 -0400 DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=887; t=1537412964; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=zku+96h c1MtOEOftu9/fqbuz6xdS4sz7ZxeSEZA2A5k=; b=iCiQHhMs2zdgRnnxB/jvgrs lMFzlFHBylxMusLVTlbQEv4L/Mo4MyDReWaxrFWY7VGIsW08GJ+Fo9LYRzEZWP1a gQHwHkTPAIST+27dKhedBVq445o32pEIl/Ne95tINh33Own3EdpuT8+7l7hNxlI2 hI53SkIFX4EhEoVf35zk= Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Wed, 19 Sep 2018 23:09:24 -0400 Received: from [192.168.1.68] ([99.121.5.8]) by beta.winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 1253693218.9.59116; Wed, 19 Sep 2018 23:09:23 -0400 Message-ID: <5BA31215.7000108@isdg.net> Date: Wed, 19 Sep 2018 23:20:53 -0400 From: Hector Santos Organization: Santronics Software, Inc. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1 MIME-Version: 1.0 To: dmarc@ietf.org References: <5BA303DF.90505@isdg.net> In-Reply-To: <5BA303DF.90505@isdg.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [dmarc-ietf] List Server Rewrite From Logic X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2018 03:21:27 -0000 I found this February 2018 IETF-DISCUSS post describing its rewrite steps for subscribers who have DMARC p=reject policies. https://www.ietf.org/mail-archive/web/wgchairs/current/msg15439.html I just change my domain to p=reject. This will be a test of the rewrite. On 9/19/2018 10:20 PM, Hector Santos wrote: > It is my understanding the IETF has begun to do a "rewrite" of the > list poster/message RFC8322.From address of restricted DMARC domains > to help resolve the IETF list subscribers distribution reject problem. > > If so, is there some written protocol, method or outline of what is > actually being done? I am giving up trying to keep the RFC5822.From > address persistent, i.e. avoid rewriting, while waiting for a better > solution to materialize. I would like to finally consider it for our > list server. > > Thanks > -- HLS From nobody Wed Sep 19 20:46:27 2018 Return-Path: X-Original-To: dmarc@ietfa.amsl.com Delivered-To: dmarc@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC03D130DF3 for ; Wed, 19 Sep 2018 20:46:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=aW3ySU3N; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=1xflds3w 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 mIxXWJOGE3AZ for ; Wed, 19 Sep 2018 20:46:23 -0700 (PDT) Received: from ftp.catinthebox.net (ntbbs.winserver.com [76.245.57.69]) by ietfa.amsl.com (Postfix) with ESMTP id 0012E130E0E for ; Wed, 19 Sep 2018 20:46:22 -0700 (PDT) DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1138; t=1537415172; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=ulo+1rJaGvCg1YzKWNmtMNOvJhs=; b=aW3ySU3NICwHexStNvBvd8KJXsjzjMyKBMlHXjK/J6Ssrb8SlNanbOvNlXMCxh 1gW8rzjmXnF0bwW5nJlLatctKD1kH20pdgSiGw3hi4jMaRbnbTOOpL5VZdp/opqd dubKeSRf3FqEXoqoI6DuqpBVdT6mY5DM3bY0Jbl0Klzvc= Received: by winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Wed, 19 Sep 2018 23:46:12 -0400 Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com; Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 1513805633.29173.2292; Wed, 19 Sep 2018 23:46:12 -0400 DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1138; t=1537414458; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=sTsSjpd FLEltU9yxj6tiEZ5LqfHG3vgzn3QAzZOBPA4=; b=1xflds3wqLWEmaL9nCCblkt PyAqkQP8vhkL41Xz+L2r4O0vu1PF6QEXpreEaK3GaegieGA9o3FjPpI+DegsIbdP BRxPc7jieFgKR9oRUMpcc+LL29Z1zywhMgLY/zIcad6J80RqHXzT93qwuQZf7hKP Rk741q4Zc6IG7zIvIwSA= Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.6) for dmarc@ietf.org; Wed, 19 Sep 2018 23:34:18 -0400 Received: from [192.168.1.68] ([99.121.5.8]) by beta.winserver.com (Wildcat! SMTP v7.0.454.6) with ESMTP id 1255187500.9.57416; Wed, 19 Sep 2018 23:34:17 -0400 Message-ID: <5BA317EB.4000703@isdg.net> Date: Wed, 19 Sep 2018 23:45:47 -0400 From: Hector Santos Organization: Santronics Software, Inc. User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1 MIME-Version: 1.0 To: dmarc@ietf.org References: <5BA303DF.90505@isdg.net> <5BA31215.7000108@isdg.net> In-Reply-To: <5BA31215.7000108@isdg.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [dmarc-ietf] List Server Rewrite From Logic X-BeenThere: dmarc@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Sep 2018 03:46:26 -0000 This worked. I had to add the "Reply-Id" address in Thunderbird to better support direct mail (Reply to Sender), otherwise it used the rewritten from address. Thanks On 9/19/2018 11:20 PM, Hector Santos wrote: > I found this February 2018 IETF-DISCUSS post describing its rewrite > steps for subscribers who have DMARC p=reject policies. > > https://www.ietf.org/mail-archive/web/wgchairs/current/msg15439.html > > I just change my domain to p=reject. This will be a test of the rewrite. > > > > > On 9/19/2018 10:20 PM, Hector Santos wrote: >> It is my understanding the IETF has begun to do a "rewrite" of the >> list poster/message RFC8322.From address of restricted DMARC domains >> to help resolve the IETF list subscribers distribution reject problem. >> >> If so, is there some written protocol, method or outline of what is >> actually being done? I am giving up trying to keep the RFC5822.From >> address persistent, i.e. avoid rewriting, while waiting for a better >> solution to materialize. I would like to finally consider it for our >> list server. >> >> Thanks >> > -- HLS