IETF Logo Mail Archive

Re: DMARC and ietf.org

Dave Crocker <dhc@dcrocker.net> Wed, 20 July 2016 17:42 UTC

Return-Path: <dhc@dcrocker.net>
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 15BC912D956 for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2016 10:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.107
X-Spam-Level:
X-Spam-Status: No, score=-1.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793] autolearn=no 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 daXYV_UiG_cf for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2016 10:42:41 -0700 (PDT)
Received: from simon.songbird.com (unknown [72.52.113.5]) (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 1797512D954 for <ietf@ietf.org>; Wed, 20 Jul 2016 10:42:41 -0700 (PDT)
Received: from [192.168.100.164] (p578ab585.dip0.t-ipconnect.de [87.138.181.133]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id u6KHhI9w026511 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 20 Jul 2016 10:43:19 -0700
Subject: Re: DMARC and ietf.org
References: <CAL0qLwYZPO9L9e7MHA6zP5vcTbQEJmwCSonLdMeQiOw4CUoiFw@mail.gmail.com> <20140718174827.652621ADAF@ld9781.wdf.sap.corp> <6.2.5.6.2.20140719235353.0c50d260@resistor.net> <25621.1405862805@sandelman.ca> <56CDC083.7020001@sandelman.ca> <CAA=duU0HLdE0WRcM3o9SXGuZ2T6E5mha+GjRkyGfPEe+VO=pdg@mail.gmail.com> <87B045CE-2C2F-4528-937E-772B67E26F8C@vigilsec.com> <1301.1456329984@obiwan.sandelman.ca> <56CDFA68.4030506@gmail.com> <A2F94A7A-3984-4E01-9C66-C580BD8C92CA@me.com> <BE67956E-7299-41D1-B8D6-B66AD18081D7@vigilsec.com> <bf2540aa-eda2-8e56-d3f5-1bf862b395ce@dcrocker.net> <10004.1469036041@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <25ffe3be-cf32-6a25-1830-82650c1175d9@dcrocker.net>
Date: Wed, 20 Jul 2016 19:42:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <10004.1469036041@obiwan.sandelman.ca>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NVwoRJ1mUgQPWwcoi7r7IX-ruJs>
Cc: John Payne <jcapayne@me.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Wed, 20 Jul 2016 17:42:42 -0000

On 7/20/2016 7:34 PM, Michael Richardson wrote:
>
> Dave Crocker <dhc@dcrocker.net> wrote:
>     > There is an effort (ARC) to develop a capability that might let
>     > DMARC-related
>     > messages survive transit of a mailing list, but that effort is still
>     > nascent.
>
> It's been two years of "please wait" (or is it three?)

Indeed.  And it will be longer before a work-around is both developed 
and deployed.  You're welcome. No, really, it was a pleasure 
contributing to the effort...


> I think that it is time to reject email coming into mailing lists that
> has p=reject policy, and not forward it, as that is the policy of the mail
> system.

Go ahead.  I'm sure the relevant users will not pursue any remedies at 
losing connectivity, such as moving to a different list provider.

Which is to say, that I and almost all others are /very/ unhappy with 
this 'side effect' problem caused by DMARC, but that real-world 
pragmatics are making it unrealistic to take simple, purity-based 
actions in response.



d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

v2.23.0 | Report a Bug | By Email