Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field

Dotzero <dotzero@gmail.com> Fri, 14 August 2020 16:18 UTC

Return-Path: <dotzero@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC9B3A0D71 for <dmarc@ietfa.amsl.com>; Fri, 14 Aug 2020 09:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 W3XCQybTrnbs for <dmarc@ietfa.amsl.com>; Fri, 14 Aug 2020 09:18:27 -0700 (PDT)
Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (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 23C953A0CFB for <dmarc@ietf.org>; Fri, 14 Aug 2020 09:18:27 -0700 (PDT)
Received: by mail-wr1-x42c.google.com with SMTP id a14so8846175wra.5 for <dmarc@ietf.org>; Fri, 14 Aug 2020 09:18:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=I4XNwtJRb4+xW/R2qnJsCSEUx7OLmgwVxVKujz6HBlk=; b=JmSI4RI/YP2pecSA91Oy15uM8m9kYd8fg3wjbt+tkvYRRd2zJhw7zKcfE4wehZLSve laFi1T1kLEroWuM1b/DAU7vTiqS8US/CrLrEYmzCEWLVLvZEYWb1hq7ZnTMvjMaLa9th jUTdz6BHyMo9DfcLwbM091+DEP6UlHlkWLgh5H/DA4ntFbfhF2yPbNVt0AePnIcF0J8h Fn8GB8M8fgRFVipmFpGzCAxrjqmxCvIG7yqNlFXnGUq8DHagm100s2bAytyKV09z1wSB fbk4wshkftEhKyRHCbJDSmKq1ucxTaFwTbnH4bKEpfaFzdvLkLJBILyv/y58WivccHTG wYGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I4XNwtJRb4+xW/R2qnJsCSEUx7OLmgwVxVKujz6HBlk=; b=kaBQY7R/kv/IFxoNeORVHMg/9TsYHTEWTXoS5UL9jjlTpp0N3keatvyNj3vh1/DF31 hkvYUvSkt/urRJmMbsUJu/1hFtaWShFVypT+adjBG43OaPLY55cX/OxEHiax0BTXyI1G VS3hN8xFw8+mKpjjl3aZ4GD7yifIhd611R2U2DmxXiM6S8GmlMwhWAwg/Cq1BrxhVFTw FOAu70yQ0C50eL4tsvI4FayT9fiPaS67mZcmL5OgHaQokP/u7kcKm6yVI03ngv3Rt/da gG5TUfQtEs5Tl+hCiabkfmhXua0OFSZD9WK3AXA3TOf1IpTdI8VPqfLTpIrIThxF2iXL 6Mew==
X-Gm-Message-State: AOAM533x3+PFb0QjzyFJGaL9mF74ylwXDt89Kj1BY566vZgTBQgf6C3+ vzfmZkaFXjHWl3fFlsgL/wJohmTiEHG3o/O+nOttAdB0
X-Google-Smtp-Source: ABdhPJxNDLQTXNlMkPxxBEcFpsOoJABNhnkggL+AVtnxqgjQhEnqSHGBwMQlUb98Nqj+g9aefouKTraiAKukmTuZBIk=
X-Received: by 2002:adf:9526:: with SMTP id 35mr3554806wrs.326.1597421905513; Fri, 14 Aug 2020 09:18:25 -0700 (PDT)
MIME-Version: 1.0
References: <CAJ4XoYfpGMUmkDkQYN0qZeNFi_xZjfR=99yVu0dgLz-z19iwfA@mail.gmail.com> <20200814020806.7D8BF1E92E0C@ary.local> <CAJ4XoYcFbh8-nAxjxzzRgUahFfhcgcZQ2yMF2ewv_-DgUmhL=g@mail.gmail.com> <3253B303-7A8B-436A-BB14-3E59FA6C96B1@wordtothewise.com>
In-Reply-To: <3253B303-7A8B-436A-BB14-3E59FA6C96B1@wordtothewise.com>
From: Dotzero <dotzero@gmail.com>
Date: Fri, 14 Aug 2020 12:18:14 -0400
Message-ID: <CAJ4XoYc0nGARKvdW54hc7ERAVOr0c81_gM6rZjHh4PaMngOQ+A@mail.gmail.com>
To: Laura Atkins <laura@wordtothewise.com>
Cc: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003c110005acd8c5a3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/h5D898_rGPyWeJrzSXF_ZnVMnyk>
Subject: Re: [dmarc-ietf] Call for Adoption: DMARC Use of the RFC5322.Sender Header Field
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Aug 2020 16:18:29 -0000

On Fri, Aug 14, 2020 at 10:46 AM Laura Atkins <laura@wordtothewise.com>
wrote:

>
>
> On 14 Aug 2020, at 09:27, Dotzero <dotzero@gmail.com> wrote:
>
>  Now I have come to the conclusion that they should reject list
> submissions from accounts at domains which publish a DMARC policy of
> p=reject. Domains should not be able to externalize their internal problems
> to others.
>
>
> This effectively cuts off users at multiple ISPs from ever participating
> in mailing lists. Which is exactly what we’re trying to fix with this
> proposal.
>

Does the proposal actually fix the problem? Does the proposal actually fix
the problem without creating other problems? After reading an re-reading
Dave's draft, my conclusion is that the answer is no to both questions.



>
> Just because a user has an address at a consumer mailbox provider that
> publishes p=reject does not make them a second class citizen banned from
> participating in any mailing list.
>

You are conflating the provision of Internet connectivity  with the
provision of email services. That ship sailed a long time ago. There are a
number of ISPs which no longer provide email accounts/port 25 services. If
a user with an account at one of those domains wanted to use their login as
an email address are you suggesting that others should send responses to
that "email address" even though no MX is available for that account and
mail will never reach that user? It is clear to me that a domain
owner/admin has the right to determine how that domain will or will not be
used. The individual is not banned from ever participating in a mailing
list. They simply can't use an account from that particular domain. There
are plenty of other places they can get an email account from. They also
have the opportunity to tell their existing provider they are unhappy with
policy. Providers can and do change their policies. For the longest time,
the address block associated with Amazon Simple Mail Service was a swamp of
badness. Legitimate users and organizations started deciding to not use
other Amazon AWS services as a result of their mail being blocked. Amazon
got religion and started cleaning up their mess. So yes, even large players
can respond to market and community pressures.

I'm not the person who initially suggested MLMs reject users/email from
domains that publish p=reject. That was John Levine. Perhaps he was being
sarcastic, perhaps not. It is certainly a forcing mechanism. And that may
just be what is needed for domains to think carefully about how they
implement DMARC.

Michael Hammer

>
> laura
>
> --
> Having an Email Crisis?  We can help! 800 823-9674
>
> Laura Atkins
> Word to the Wise
> laura@wordtothewise.com
> (650) 437-0741
>
> Email Delivery Blog: https://wordtothewise.com/blog
>
>
>
>
>
>
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc
>