IETF Logo Mail Archive

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

Dotzero <dotzero@gmail.com> Tue, 28 March 2023 16:39 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 C83A5C14CE33 for <dmarc@ietfa.amsl.com>; Tue, 28 Mar 2023 09:39:09 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2iTBlfj27uvD for <dmarc@ietfa.amsl.com>; Tue, 28 Mar 2023 09:39:09 -0700 (PDT)
Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (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 4F5CCC14CF13 for <dmarc@ietf.org>; Tue, 28 Mar 2023 09:39:09 -0700 (PDT)
Received: by mail-yb1-xb2f.google.com with SMTP id e65so15831989ybh.10 for <dmarc@ietf.org>; Tue, 28 Mar 2023 09:39:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680021548; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=b5XfUzNpbj9150T/bnulMOVrj+GW8wEfokZLUQF5x+I=; b=QoZ09/llNqICHEE7n9b8patfiEsNIemHbUNVL5By/OWGwwqKL4iRRKYndyFomGA81E utHaJbqxdlOs7JvuodyAh7JwlzcU44uub8igV+Ww2FXcLx1fLn6hTJRBB5grflqOsMKu BTt3P4Jye+t/vWtmm8FnduftJDUahx1wFRAfuaN736XcLsfKHlRsVUajF232C9DQgWC+ BhHGT+UigV+goA6xd4mMkVLVY/GY1R0upbCANg+r6qDmOwYk6JELEci7pieBuYfK1XjC vABrXw8mU3E5SwHZ4skuI4ffWr/1vKn4xgfVMZZMPSoZP/3bF8wDCq1XUkiQT2TNiHVO /5dg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680021548; 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=b5XfUzNpbj9150T/bnulMOVrj+GW8wEfokZLUQF5x+I=; b=EiIwEel11yj2D8m2rTcQ+4pkg68runc20hNElU7MHFobXF0xpGnXI1IbwlCQGmHtQC g3/TQBMKuWTNtdEXg/2h24kOQXy6JsaQ3MG1hu9f+4EKe0RWWaSa2/0L//TnGSK53Zq5 +EaOMBZy7GaWoWjRxJU2oiufp0+Hapl7CVv6C1ntpg5um2W5l0zd087ZbZLhCLQ1MAC2 LNcH2MD2viJ5VCGP/Mq5gFaoHcsoOnXXFgof0C8wIkz4xFEpklwOw+LkXps8bLk/v5oH JeFv/9D90P0MCYqUTXkb5cCKNKanBXiVuJtMK+rYS0tUOzHw0kXhxl3jXJ4i6s0Lx91U eumw==
X-Gm-Message-State: AAQBX9es5agV4s1mbFeExqhwhddRbbjYLHO+aYYeMXVHiU4xDR5++mjt zdpHcOFGn9eEahqM0kt4Cn3fLLQJslzRh4ViNJ6dDUHGbCw=
X-Google-Smtp-Source: AKy350bA8TMNPgoxy6O6xDbZ6zEW6w9ux8llYV4qFA3SpIEBtgmG5ro030uUlXFA9/VBXmmNduIRV/zYKgboxgagYkQ=
X-Received: by 2002:a25:c750:0:b0:b45:e545:7c50 with SMTP id w77-20020a25c750000000b00b45e5457c50mr10556920ybe.0.1680021547885; Tue, 28 Mar 2023 09:39:07 -0700 (PDT)
MIME-Version: 1.0
References: <CALaySJ+NBg9vzqa0_t-sBf7EKXQ3A=DTyy-Vc7M-ZK9-vfJxmw@mail.gmail.com> <CAHej_8m7m29EiKUzarR1wBVyxfORfdcX_kgUz0-3uDiqoZ+i2A@mail.gmail.com> <CAHej_8nu8LZCEk2COCk6XUv9oPs2tP-SOZfUhKSqMxx8gBN8iA@mail.gmail.com> <3445610.T9FX6QkNB4@localhost>
In-Reply-To: <3445610.T9FX6QkNB4@localhost>
From: Dotzero <dotzero@gmail.com>
Date: Tue, 28 Mar 2023 12:38:56 -0400
Message-ID: <CAJ4XoYfS3X61VXbL8DLcE9gvVZLQ0U9FH3ruP-UK9r13iaNbyw@mail.gmail.com>
To: Scott Kitterman <sklist@kitterman.com>
Cc: dmarc@ietf.org
Content-Type: multipart/alternative; boundary="00000000000093a9ff05f7f87fa5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/rvv86Z3Z3pcqDJ_8iMkduR7XFIU>
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: Tue, 28 Mar 2023 16:39:09 -0000

On Tue, Mar 28, 2023 at 12:18 PM Scott Kitterman <sklist@kitterman.com>
wrote:

>
>
> I don't understand the connection between DMARC policies and open signup
> domains?  What makes them in any way special relative to DMARC?
>
> Scott K
>

I agree with Scott on this.  I don't believe that "open signup" domains
deserve this special call out in this manner. For example, a domain
providing accounts to the public ( "open signup domains") may choose to
specify in its TOS that account email addresses may not be used to send
email from servers other than the domain's own servers. This is a
contractual issue, not an interoperability issue. We should be very careful
before wading into these waters. I understand the concern but I think the
concern is best handled in a separate BCP.

Michael Hammer

v2.23.0 | Report a Bug | By Email