IETF Logo Mail Archive

Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 11 May 2018 19:30 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2756112D879 for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 12:30:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 eX6tL_32LF7v for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 12:30:17 -0700 (PDT)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73A1312D86A for <ietf@ietf.org>; Fri, 11 May 2018 12:30:15 -0700 (PDT)
Received: from [192.168.1.161] (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 304857A3309 for <ietf@ietf.org>; Fri, 11 May 2018 19:30:14 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <911C82676980A52DB95C7DEF@PSB>
Date: Fri, 11 May 2018 15:30:13 -0400
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-Id: <7906364A-91C7-4DC3-84BF-6AB538F66EB8@dukhovni.org>
References: <919855CA-9F77-420A-8B8F-79174CD2FC19@fastmail.fm> <61B1EDB45FC4FF33154B13B0@PSB> <739143A6-90EB-4F26-8F54-B281DA2FB0E4@fastmail.fm> <CAKKJt-cvxgW2=Od_hkF8+keDHfT_1RJtSLwXSiiR7_dhmqPJYQ@mail.gmail.com> <911C82676980A52DB95C7DEF@PSB>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1zn0nJoWC5TgmsJbnlCFFM3bJ8o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 19:30:19 -0000


> On May 11, 2018, at 3:05 PM, John C Klensin <john-ietf@jck.com> wrote:
> 
> I assume that dmarc.ietf.org will
> recognize its own convention, rewrite the message headers, and
> send it off to alexey@example.com.

This rather invites abuse, since now ietf.org becomes an open relay
for all the "DMARC-protected" contributors.  Other lists I'm on
do something that I find more useful:

	From: List Name <list.name@list.example.org>
	Reply-To: Author Name <author.name@example.com>, ...

This does not introduce any anomalous reverse routing.

-- 

	Viktor.

v2.23.0 | Report a Bug | By Email