Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mention of ARC in DMARCbis
Emanuel Schorsch <emschorsch@google.com> Tue, 02 April 2024 17:49 UTC
Return-Path: <emschorsch@google.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 60068C14F6AD for <dmarc@ietfa.amsl.com>; Tue, 2 Apr 2024 10:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.596
X-Spam-Level:
X-Spam-Status: No, score=-17.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=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, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 sZb0l57zGsBq for <dmarc@ietfa.amsl.com>; Tue, 2 Apr 2024 10:49:31 -0700 (PDT)
Received: from mail-ej1-x634.google.com (mail-ej1-x634.google.com [IPv6:2a00:1450:4864:20::634]) (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 51CB2C14F5FB for <dmarc@ietf.org>; Tue, 2 Apr 2024 10:49:31 -0700 (PDT)
Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a46a7208eedso711916566b.0 for <dmarc@ietf.org>; Tue, 02 Apr 2024 10:49:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1712080169; x=1712684969; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=NcbljvJ8LbZrRscY3rhfBVM6j3kBc1ZYleolZVdzkbo=; b=Fuz90EsWcqT138IXVWoq0qgnTkyYPU8+fQPz/VEH3Z7WjlIV285PEMBLS8brwgQwrr rw0072v4zhJ2+2H1/8NO2XbfDc8GzsHFoDifC7fWYZILeaY0lO/nz8ji+iSPfh6JrCtn R7gUYdgJFkspHK/QlhraHbpHo3/0Z2xY51YpWerZRP8l5dCq00fY9aT+WOCPXpfMaSqp tKCmb1+GMQORufcq16wQIOhVKK9Ks8q204u2/Kmn7mvHHdt/zFgb237qyOvB7KICGlmX N3pvnkeNCGC6gn5nf7r3AV/B45D1LPv9kwK61yO8QGQIsJIAGrGiCoTSxQaAiuMgszgq 1jdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712080169; x=1712684969; 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=NcbljvJ8LbZrRscY3rhfBVM6j3kBc1ZYleolZVdzkbo=; b=X9rD2c7Eon+tJjCaxEKuSVT5oU/0Z8dmLF7+sLfD3t3xHnGDS9+fBkR5ORgpDaD+L/ 8s2Dg4mfuBr1/aqfBFzFvPLWyqHdK6f9F3o7N4CMVcZOsWFcWGyuDIwvSb0kbmyebR5U dSk55TT9QsOIfPNWsnRyw/3jteffR68xAB5VQJlzkpoDI2VXbmqcpfwlX/LFu79ZZHfy FC8PRkqKR73OV6pJTVLY96OHcs+bqyc1L16WZF5LKKfwAHCYmUT2GUxWS/0JdCMJGS4/ v0SHKAyD/9lv7s2kizK88QNUyty3Sgm4Up/b/n3XR9ML6Js/aW1zv1c5lyzuA7ryZo5q Iyow==
X-Gm-Message-State: AOJu0YzvkNlG56K2xqeT3BKxvzNkJSK7pkEWBDNt3OCM7zPlWms5iI4q WnAeGOgUYS2nOg4bcvAoauGFs82PknQwJTqJjAeJsRKr20Nj4D7k4c5JqrsLtJkFlvEfa7pMLPq iOw108AqkqMU2zojoaYfGNvaE0U4BPUeAIOUD
X-Google-Smtp-Source: AGHT+IH3powR4CyccQ3h3CaqTePeIMJF9QNQ2yYUxmwhQxB7wkQB2xrkvehVtAjIV1yJrSQEMhWnWOvdj7CsV2TmqFo=
X-Received: by 2002:a17:906:f6d1:b0:a4e:1b02:81d6 with SMTP id jo17-20020a170906f6d100b00a4e1b0281d6mr342055ejb.10.1712080169203; Tue, 02 Apr 2024 10:49:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAHej_8x7jGiMQmuJR8qnp5ET8i_Xqz1p4YSeM6RkeY3YiNfaxg@mail.gmail.com> <20240401230502.531CA86A7CC2@ary.qy> <CAL0qLwZakrXvDQPc851ggDuipbdv9+zApPYESkfYq12QB3_UAA@mail.gmail.com> <CAFcYR_WFXZv3z_RPavixYHMRy=kVxYrfUDiUjy18FbgYuXCk3w@mail.gmail.com> <CAL0qLwZKWNsV_CZ7C4ep88soaquhFG6FswoyNDWdfJ4HB7pamQ@mail.gmail.com>
In-Reply-To: <CAL0qLwZKWNsV_CZ7C4ep88soaquhFG6FswoyNDWdfJ4HB7pamQ@mail.gmail.com>
From: Emanuel Schorsch <emschorsch@google.com>
Date: Tue, 02 Apr 2024 10:48:50 -0700
Message-ID: <CAFcYR_UFs-KHZJ5mVKDT=6hrJx=17KAqLRoNF6p+UoP5FgDG9w@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Cc: dmarc@ietf.org
Content-Type: multipart/alternative; boundary="000000000000505399061520bac7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/RVxb9lFMcIml8WYMi56gSrLpp8g>
Subject: Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mention of ARC in DMARCbis
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, 02 Apr 2024 17:49:35 -0000
Three concrete use-cases where ARC is helpful: 1) SPF Downgrade <https://www.valimail.com/blog/how-an-spf-upgrade-attack-spoofed-googles-blue-checkmark/>. We didn't reach consensus for adding auth= tag to DMARC and so SPF Upgrade remains a significant vulnerability for achieving a DMARC pass. Having the ARC headers allows us to detect that this has occurred and respond appropriately (reject/spam-folder the message or just downgrade the authentication state in our system). 2) Excluding indirect mail flows from parts of Sender Requirements <https://blog.google/products/gmail/gmail-security-authentication-spam-protection/> / NoAuthNoEntry. Having the ARC headers and a safe way to consistently identify the indirect flow in a non-spoofable way allows us to not apply requirements that don't make sense for forwarded mail (e.g. requiring SPF or DMARC alignment) 3) Local policy for DMARC failures. For example, downgrading p=reject to p=quarantine if ARC headers indicating indirect mail and previous alignment are present. On Tue, Apr 2, 2024 at 6:37 AM Murray S. Kucherawy <superuser@gmail.com> wrote: > Hi Emanuel, > > On Tue, Apr 2, 2024 at 1:02 AM Emanuel Schorsch <emschorsch@google.com> > wrote: > >> Just to chime in, Gmail is using ARC and it has already provided a large >> amount of value for the indirect flow problem. Especially, since other >> major providers and a number of forwarders are adding ARC headers that >> provide us useful visibility into the previous hops and allow us to make >> more intelligent decisions. I can share that a number of escalations for >> problems that arose out of indirect flows have been resolved by use of ARC >> headers. >> > > Can you give an example, even if only a hypothetical one? > > I would love to hear more detail than "Yes, it provides value." How, > exactly? And have any other operators found the same? > > -MSK, p11g >
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… John Levine
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… Scott Kitterman
- [dmarc-ietf] DMARCbis WGLC - Issue 144 Mention of… Todd Herr
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… Murray S. Kucherawy
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… Emanuel Schorsch
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… Emanuel Schorsch
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… Alessandro Vesely
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… Murray S. Kucherawy
- Re: [dmarc-ietf] ARC, DMARCbis WGLC - Issue 144 M… John Levine
- Re: [dmarc-ietf] ARC, DMARCbis WGLC - Issue 144 M… Murray S. Kucherawy
- Re: [dmarc-ietf] ARC, DMARCbis WGLC - Issue 144 M… Seth Blank
- Re: [dmarc-ietf] ARC, DMARCbis WGLC - Issue 144 M… Murray S. Kucherawy
- Re: [dmarc-ietf] ARC, DMARCbis WGLC - Issue 144 M… Seth Blank
- Re: [dmarc-ietf] DMARCbis WGLC - Issue 144 Mentio… Emanuel Schorsch