Re: DMARC and ietf.org

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 21 July 2016 05:35 UTC

Return-Path: <brian.e.carpenter@gmail.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 84E1912DA0A for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2016 22:35:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 iAonQuBo2AUP for <ietf@ietfa.amsl.com>; Wed, 20 Jul 2016 22:35:24 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E09E812D901 for <ietf@ietf.org>; Wed, 20 Jul 2016 22:35:23 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id p74so64952973qka.0 for <ietf@ietf.org>; Wed, 20 Jul 2016 22:35:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=t+tOSQot6pVYlWw9ZL7u7QcuoFszavjySUSO52XPFLo=; b=sLWxjHBwtFR3kQwosLJ+FcpwJOB40DbJaWQSi2QqEvtNvlj1elsJ35V5cRjo92VHmT JNe0NUssIMXpbAIfD3lqV5CZz/OkInUqnaOq5XbvKB/VFIaRJwf1pxDuxtlMgixYJgub sD0zoPhD1QtvhfbihwwqkgTbOGsane23uP6E++mFPl8ATj5HoV7TM080RiFQF1uV5ldY ft4yxYepS8Gl1jlHCYg3W+cdhI5Rc5c9D6kG6zLWtmVVNUYGbIZ1S9nVcox/yEc0nM7c hMYWFpBEWehqeKQEzRenJc/6o/6LbMwn60qyB+uc8nXLTkmhVF0M5VxVNWVBJ7ytUzPS vUvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=t+tOSQot6pVYlWw9ZL7u7QcuoFszavjySUSO52XPFLo=; b=e8mhf2dDDMgGgtXGCk2U0QQOhuDOvCORCyjw7Qpih/UtYiPs5lWaVpweRfbvc6fjbX 8wPrMMhRs6sW4nCaAiyIbdP15njsF86DnoT69m16koRlTVXsqAcKk08Kio/aTP8eEUQx RxDc5teCyA68e1+otEdHmvJRdBhO1rfKeE1gglzEz5PyvCNyBbX5PuQBryZa56K8goWG byQ4FcozDrUEZIASchrPPTBEZXWsHm+s3XmfKkOPVrKZsboLqnPduSrE+2p4ZPFP5f7y JGav3NZwiC7Rfn75YIWqe7bV5xrbXn829ijbIom8L8MMcgUSexXSDMFW/mAzhOmTrfXK xbXw==
X-Gm-Message-State: ALyK8tI3OAXuSInwZ+o2nNkSjU517Zk1+8sfR5OqNutVlPc3rRlSqXzL2gBRIuqeOngElg==
X-Received: by 10.55.167.199 with SMTP id q190mr66695617qke.95.1469079322940; Wed, 20 Jul 2016 22:35:22 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:136:28cc:dc4c:9703:6781? ([2001:67c:370:136:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id z32sm3468126qtz.0.2016.07.20.22.35.21 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 22:35:22 -0700 (PDT)
Subject: Re: DMARC and ietf.org
To: ietf@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> <25ffe3be-cf32-6a25-1830-82650c1175d9@dcrocker.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <aa0e220a-e1a1-3c65-b426-01d1fbb09c5d@gmail.com>
Date: Thu, 21 Jul 2016 17:35:28 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <25ffe3be-cf32-6a25-1830-82650c1175d9@dcrocker.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X99uHUiSC-mnTOUVYALQg7UTQx8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 21 Jul 2016 05:35:25 -0000

On 21/07/2016 05:42, Dave Crocker wrote:
> 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.

Yes. So I repeat the question: Since the most pragmatic, non-purity-based
solution is to rewrite the sender field for mail from p=reject (or p=quarantine)
domains, when will we change the IETF and IRTF mailmen to do so?

I'm happy to help experiment for any lists for which I am an admin, but we need
the IETF's IT support to take this very seriously very soon. The day that gmail
changes its policy, I estimate that at least 20% of the IETF will be broken.

    Brian