Re: [dmarc-ietf] Proposed text for p=reject and indirect mail flows

Barry Leiba <barryleiba@computer.org> Thu, 30 March 2023 02:01 UTC

Return-Path: <barryleiba@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 7E399C159A24 for <dmarc@ietfa.amsl.com>; Wed, 29 Mar 2023 19:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.547
X-Spam-Level:
X-Spam-Status: No, score=-1.547 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.096, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HYi92Pa49i0H for <dmarc@ietfa.amsl.com>; Wed, 29 Mar 2023 19:01:34 -0700 (PDT)
Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 765BFC1522D9 for <dmarc@ietf.org>; Wed, 29 Mar 2023 19:01:24 -0700 (PDT)
Received: by mail-ed1-f45.google.com with SMTP id ek18so70729936edb.6 for <dmarc@ietf.org>; Wed, 29 Mar 2023 19:01:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680141682; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=BOOUkvjndd5iifEhGdXK4Td7xZm+IBNFw4gCNc4jy14=; b=kI80g8GjgdwOqPhV3B+zosbRjzNwdvqOpuFgaiS57YUgqhj6WpjtT3/IjhoAQpZ6xd BEEHJI5ZjhctenRbb7305mwNuLkcEmzYFKvyXsTzLMRAZjANw6FTNM0z/isj3GECkG2i 0vWtlQzfm7ek3/mewkJ3nMQQU8NfrrfRSFtdt+VskoeZnr90lhA/cZwltj7TVAS64RLY lnYSOMcYGnR42nuafNuRuigDCaXwFiYjNieVYWwEAFbylr/SVCRLhbjd92gAU1kIBO0G FmVOQE33dyZBEV2kUO2JJiqs0JrHC6BQkI8dJawJZ4i8/rte3ozE9pL6gAfrz6Zcxd3C FJSA==
X-Gm-Message-State: AAQBX9cZZWiyqy5AmO1eZ9/QSnrOvMlapZIGfFYVlXSvPdHXaZ1iz+HN 2mpRzg5Efh5CGYvOMHPBDskhYfPDSldwiCFPTec8dDxYe24=
X-Google-Smtp-Source: AKy350aNkkfBoHelqpBmYphTW4H5xVUBTVoDFrK0MCzHEZ/K8UOTZHi+Gz5aqnfL42y8vSPddESHARNkqlXte7BD2Iw=
X-Received: by 2002:a17:906:5584:b0:93a:6e4d:e772 with SMTP id y4-20020a170906558400b0093a6e4de772mr2735316ejp.7.1680141682183; Wed, 29 Mar 2023 19:01:22 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+NBg9vzqa0_t-sBf7EKXQ3A=DTyy-Vc7M-ZK9-vfJxmw@mail.gmail.com> <6319292.vCqnBZbX7o@localhost> <CAHej_8nd1xyAgwASLJbuJHyXEAfHbjqxNH1XtJxKFyfyOneyug@mail.gmail.com> <13145172.pEV04Z3DvM@localhost> <CAHej_8msLJQ0vbZ2jzitjxrQ1wdim5bHJkiD-QrU5F0EJvQp0g@mail.gmail.com> <FCFEB95E-63F9-46C3-A5F4-FA6B02FA8EB5@episteme.net> <CAHej_8=GbmzyXaeEkyLkv6uKc0-owuMC6UspPNq9irT7nF8b7w@mail.gmail.com> <CALaySJLmRyyBLE7ZKy88XUS_hXr9M2uwc8jOCYBrBPeC+pCdCg@mail.gmail.com> <MN2PR11MB43519A6CD95E5C80AA1EC2CFF7899@MN2PR11MB4351.namprd11.prod.outlook.com> <13603D87-4FDE-4768-9712-E6DB0818C802@kitterman.com> <CAH48ZfztW4OFm+ZMV=et7+uczj49dfbYT7i0w4LgU7pswuiEnw@mail.gmail.com> <CAL0qLwayTG_M1-fSTXiaVM5TS1Vo7X+Ehov2Bov9vCak7gn=yg@mail.gmail.com> <CAH48ZfxejSxbsDpgBUcfMDhGcz0QLGZEH6yVRMC0xmEFLksw3w@mail.gmail.com>
In-Reply-To: <CAH48ZfxejSxbsDpgBUcfMDhGcz0QLGZEH6yVRMC0xmEFLksw3w@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 30 Mar 2023 11:01:10 +0900
Message-ID: <CALaySJL2nuM6jaQc5ExhRymtRR9mHRPwwEUci0c1VtBzF_+fmA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002392e705f81478f7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/FGl8L37kd4iZmPSs9CBsC80yFOY>
Subject: Re: [dmarc-ietf] Proposed text for p=reject and indirect mail flows
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 30 Mar 2023 02:01:38 -0000

> Our spec needs to fix the evaluators, and their products, not the sender
policy.

No: it should be doing both.

Let’s look at it this way:

Suppose a general-use email provider called “Hooya” promulgated a policy
that said receiving domains should bounce any message from a hooya.com
sender that was fanned out to mailing list recipients.

I think that, worded that way, we would all agree it’s a bad idea.

If we were writing a policy spec of some sort and we were addressing this,
I think we should say BOTH that such a policy is inappropriate in that
would damage mailing list operation AND that receiving domains should not
be accommodating that policy.

Hooya’s use of p=reject would amount to announcing that policy, given how
mailing list software works and has worked for decades.

Barry