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 21:44 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 94EB012D93F for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 14:44:45 -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 LWA5YTRDUkiW for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 14:44:44 -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 2294312D940 for <ietf@ietf.org>; Fri, 11 May 2018 14:44:40 -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 29BE47A3309 for <ietf@ietf.org>; Fri, 11 May 2018 21:44:39 +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: <20180511213138.D86C7266D234@ary.qy>
Date: Fri, 11 May 2018 17:44:37 -0400
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-Id: <9D950D21-7324-469E-A809-8946B77824F1@dukhovni.org>
References: <20180511213138.D86C7266D234@ary.qy>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ac7tYAQV-1lNOOKBJk30kGmKtKM>
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 21:44:46 -0000


> On May 11, 2018, at 5:31 PM, John Levine <johnl@taugh.com> wrote:
> 
> For whoever said it's an open relay,

I'm not ashamed of that post. :-)

> sheesh, we're not totally dim.

Of course.  And yet, I may want to reply to a saved message years
later.  How may years of reverse forwarding is the ietf.org mail
service signing up for?  If Gmail, Yahoo, ... are having trouble
filtering out all the outbound 419 scams they're sending me, should
I expect ietf.org to do better?

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email