IETF Logo Mail Archive

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

"John Levine" <johnl@taugh.com> Fri, 11 May 2018 21:51 UTC

Return-Path: <johnl@iecc.com>
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 A77A012D94B for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 14:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=KYlAM3To; dkim=pass (1536-bit key) header.d=taugh.com header.b=gumqLRDv
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 r5VaVpmz5Cio for <ietf@ietfa.amsl.com>; Fri, 11 May 2018 14:51:17 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 861C312D93F for <ietf@ietf.org>; Fri, 11 May 2018 14:51:17 -0700 (PDT)
Received: (qmail 80265 invoked from network); 11 May 2018 21:51:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=13987.5af61053.k1805; bh=nmF9NK4LNB8Et1+BpZDyka/qLseQDQtJJqny+Tn6/9E=; b=KYlAM3ToYilT4mHYlx86i7yv9P6VLGlL0ioDlYUnyLK3YyRqH5mHlaNw0AGRwFT8t7Ieoq12R54HL1YwRU9b3QKJDPlLIV/2H6VgdKBPPsIRoxzmPnZ8Azugoi91gV/j0krQ+PcqT/CVHuY3jDYtbkqW1mz+bfmGKwg+I+9rDXFlFoU7yWbO/JHwpr4npajodmJaei7Tb0obgprLZX8qYBbSjJ48e/Onz0xIh5UFOW9FllfrhmFCIVLtCQL7Wb7h
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=13987.5af61053.k1805; bh=nmF9NK4LNB8Et1+BpZDyka/qLseQDQtJJqny+Tn6/9E=; b=gumqLRDv8hR+NC3B1/bVjtUc5loUtqSlRCYQjXcSwPPnq7tIWEZDO3WhiC2kaE3KrDml/qaTz1k359XcOQ0+j7SdXK6GgTJ6MwYwI5+E+P8kzbC6nOtld5h/J0uBxZUpOQ5bEU2vEigYGwmA+dpwLJ6bHOLSaBdIOQS23gjf6jxC4uoOZkJA6T6VJneXRyozvsNdrAkAaBVwK5vMFlxd3oRoiGA11FK/qgRejkf0hBclN6XF2VhCTzs50oJHZdQj
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 11 May 2018 21:51:15 -0000
Received: by ary.qy (Postfix, from userid 501) id 37389266D3D1; Fri, 11 May 2018 17:51:14 -0400 (EDT)
Date: Fri, 11 May 2018 17:51:14 -0400
Message-Id: <20180511215115.37389266D3D1@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Enabling DMARC workaround code for all IETF/IRTF mailing lists
In-Reply-To: <9D950D21-7324-469E-A809-8946B77824F1@dukhovni.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9e-hP8Mu7i0aDcKRS46ws4uIkaw>
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:51:19 -0000

In article <9D950D21-7324-469E-A809-8946B77824F1@dukhovni.org> you write:
>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?

Probably not many.  It's a kludge, remember.

I can also report that if you don't need to allow bulk mail when you
forward, it's a lot easier to do reliable filtering.  You can, for example,
enforce DMARC policies with a near-zero error rate.

R's,
John

v2.23.0 | Report a Bug | By Email