Re: [dmarc-ietf] Signaling forwarders, not just MLMs

Barry Leiba <barryleiba@computer.org> Thu, 13 April 2023 16:19 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 515FDC14CF1F for <dmarc@ietfa.amsl.com>; Thu, 13 Apr 2023 09:19:24 -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_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 sDeQMCuHx9gt for <dmarc@ietfa.amsl.com>; Thu, 13 Apr 2023 09:19:22 -0700 (PDT)
Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (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 8EB6DC14CF0C for <dmarc@ietf.org>; Thu, 13 Apr 2023 09:19:22 -0700 (PDT)
Received: by mail-ej1-f51.google.com with SMTP id jg21so38461002ejc.2 for <dmarc@ietf.org>; Thu, 13 Apr 2023 09:19:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681402761; x=1683994761; h=cc: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=rpwaBqNRisNJ/AQrrnz/geV+Dlxsf1MYlyYKOnAK1OQ=; b=luNJRo7o++ZXUbH6z2IEtsno8pvIuCRBDRDHNOj/IHermBywMKjJYFHIVSGq8u3Fo8 l6pOQZESHQP0uRz7PpHjQrCNJ6lQVtmqINNNa5217OYzbE9bL7nq+bzSrdyriM6h5kwS WZqygkxFaVp8FHCrsEcVl2vzEkMP0Je+Cjdo9jkbYsAvTzBFvo+uIeCc/4gVW16R8WX0 +RFB1tBReqMSz6MdeVj2tTYE9PZwcHseEO0Pr+HEVKhqp+Gqp3H0OV+mjK3+Wl4Q88qg HWlWJgtq8OSCjDtoBbKK9ykaZwo6a7yyIVkhTXeVQVzs/U/ROjtoFTMTu4z8QkMAMzSP G3wA==
X-Gm-Message-State: AAQBX9c2fpcffrO9492wXrJLoemZkFCTt/iZOoFccmImPDXh5yxSoM5m lgtI+8ETbYBiq3EhpM6Rj5uuBbs2aWeK+hZoGCI=
X-Google-Smtp-Source: AKy350bXiDQRZJESUBljqm1vNMFVocZej8qtZXqz+BOzjbQHMdZL282Is0QG/EjT9MxeNavnaqIeE/Tf4S/APWovd04=
X-Received: by 2002:a17:907:6d23:b0:8b8:aef3:f2a9 with SMTP id sa35-20020a1709076d2300b008b8aef3f2a9mr1578458ejc.0.1681402760820; Thu, 13 Apr 2023 09:19:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAL0qLwYbbLLq-qLg_Wnp5aFw_2my4UTZz3U3LjwbCmpMNdudfA@mail.gmail.com> <20230413151342.B96D0BF17F1F@ary.qy> <CALaySJKM5Kct0u0ekuEBS=DVQTXG_CiewpzNwVyPiAaQ9zx3VA@mail.gmail.com> <CAHej_8nyYrCXPo8aYOb+cVSf=2NQDOBmUgo-FD=ohPBZ=yFuHw@mail.gmail.com>
In-Reply-To: <CAHej_8nyYrCXPo8aYOb+cVSf=2NQDOBmUgo-FD=ohPBZ=yFuHw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 13 Apr 2023 12:19:09 -0400
Message-ID: <CALaySJ+6JxGua90o8kgyoFH48swn6f0g8x+Jx4By4jQnC7ot8w@mail.gmail.com>
To: Todd Herr <todd.herr@valimail.com>
Cc: John Levine <johnl@taugh.com>, dmarc@ietf.org, superuser@gmail.com
Content-Type: multipart/alternative; boundary="00000000000048d0a005f93a1680"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/W3hNfp2NZjdLc-3Y_-8UDZi9x2M>
Subject: Re: [dmarc-ietf] Signaling forwarders, not just MLMs
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, 13 Apr 2023 16:19:24 -0000

Maybe just add a sentence to the end of the second paragraph:

   The use of SPF alone, without DKIM, is strongly NOT RECOMMENDED.

Barry


On Thu, Apr 13, 2023 at 12:04 PM Todd Herr <todd.herr@valimail.com> wrote:

> On Thu, Apr 13, 2023 at 11:21 AM Barry Leiba <barryleiba@computer.org>
> wrote:
>
>> > Anyone who does forwarding is damaged by DMARC because there are a lot
>> of
>> > people who do DMARC on the cheap with SPF only.
>>
>> This brings up another issue, I think: that there should also be
>> stronger advice that using DKIM is critical to DMARC reliability, and
>> using SPF only, without DKIM, is strongly NOT RECOMMENDED.
>>
>> I don't disagree.
>
> How do we make the following text stronger?
> 5.5.2.
> <https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-27.html#section-5.5.2>Configure
> Sending System for DKIM Signing Using an Aligned Domain
> <https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-27.html#name-configure-sending-system-fo>
>
> While it is possible to secure a DMARC pass verdict based on only one of
> SPF or DKIM, it is commonly accepted best practice to ensure that both
> authentication mechanisms are in place to guard against failure of just one
> of them.
>
> This is particularly important because SPF will always fail in situations
> where mail is sent to a forwarding address offered by a professional
> society, school or other institution, where the address simply relays the
> message to the recipient's current "real" address. Many recipients use such
> addresses and with SPF alone and not DKIM, messages sent to such users will
> always produce DMARC fail.
> <https://www.ietf.org/archive/id/draft-ietf-dmarc-dmarcbis-27.html#section-5.5.2-2>
>
> The Domain Owner SHOULD choose a DKIM-Signing domain (i.e., the d= domain
> in the DKIM-Signature header) that aligns with the Author Domain.
>
>
> --
>
> *Todd Herr * | Technical Director, Standards and Ecosystem
> *e:* todd.herr@valimail.com
> *m:* 703.220.4153
>
> This email and all data transmitted with it contains confidential and/or
> proprietary information intended solely for the use of individual(s)
> authorized to receive it. If you are not an intended and authorized
> recipient you are hereby notified of any use, disclosure, copying or
> distribution of the information included in this transmission is prohibited
> and may be unlawful. Please immediately notify the sender by replying to
> this email and then delete it from your system.
>