[dmarc-ietf] List Server Rewrite From Logic

Hector Santos <hsantos@isdg.net> Thu, 20 September 2018 02:20 UTC

Return-Path: <hsantos@isdg.net>
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 <dmarc@ietfa.amsl.com>; 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 <dmarc@ietfa.amsl.com>; 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 <dmarc@ietf.org>; 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 <hsantos@isdg.net>
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" <dmarc@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/VzfCfXjBayWHJXqglQEloh9JkgY>
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\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=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