[dmarc-ietf] Re: Evaluating consensus on the idea of making ARC "Historic"

Alessandro Vesely <vesely@tana.it> Fri, 31 July 2026 10:40 UTC

Return-Path: <vesely@tana.it>
X-Original-To: dmarc@mail2.ietf.org
Delivered-To: dmarc@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3971D12186B44 for <dmarc@mail2.ietf.org>; Fri, 31 Jul 2026 03:40:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1785494424; bh=KDNF2YKwwB5PxUbrWibRx7aF+2aJ3BxFA1fMHzjoCdk=; h=Date:Subject:To:References:From:In-Reply-To; b=g9jyXlHYUvbJSdgkYar1AQHL2ClL02+OX/RhwDgZJtnyJ1/ir8aO7sZKxi34vTMse hatgnYnhUjjGWFDd2zApUGB2CKlLG2hATwoBcatPK9lJ0C90f27NSX6C7L9RCyHVme LeCT2Pg/TOOKVHNW86Hc+s7EFHhiz2yIyx4+zOJ0=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GI32kDRHThu1 for <dmarc@mail2.ietf.org>; Fri, 31 Jul 2026 03:40:23 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [94.198.96.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 2DE1712186B3F for <dmarc@ietf.org>; Fri, 31 Jul 2026 03:40:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1785494421; bh=mbXSvvN+uQOof+5I1hdUlJLThaOjLSZe2IUhMkU+0k0=; h=Date:Subject:To:References:From:In-Reply-To; b=Ad2OWEtXwoeUssrUog88gl+EtjudW6RY472yuPDBH/Xs0a/ofvYkv8bcgRy0V9QBx VG8jd+dnGURJw6kY1H7d0ukwoBxZlLafPp/XtGOygy7Ma6B7CYlZGN8ikZM+uH0KEJ HPEM1o/y9XHEwmUclJFZ24D7rpI+yMUCumkl6ebM80Y4uFabmvraDYebV/O0y
Original-Subject: [dmarc-ietf] Re: Evaluating consensus on the idea of making ARC "Historic"
Author: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.87] (pcale.tana [::ffff:172.25.197.87]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3,128bits,ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC03D.000000006A6C7B95.000067B8; Fri, 31 Jul 2026 12:40:21 +0200
Message-ID: <98dface1-867e-4864-afc5-9e57fc363a69@tana.it>
Date: Fri, 31 Jul 2026 12:39:32 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Richard Clayton <richard@highwayman.com>, dmarc@ietf.org
References: <CALaySJJx_Q7ANbhooNSHY7XawW51Lt42hM771O6Kr-pKLrt5=g@mail.gmail.com> <CAD2i3WMhQhKZUGjG_y0DGDXJdgM9qPMpHUAmvH5pjicQG+5EkQ@mail.gmail.com> <CALaySJK-X0XtA8ODbA-9KbzTxDth_pKc5fqWU6tbq3h+tizJ=g@mail.gmail.com> <5$YN55AmL5aqFAGQ@highwayman.com>
Authentication-Results: tana.it; auth=pass (details omitted)
From: Alessandro Vesely <vesely@tana.it>
Content-Language: en-US, it-IT
In-Reply-To: <5$YN55AmL5aqFAGQ@highwayman.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: Q5HTS4YK5MWALXIXHO5HTIUOATWRIYQ2
X-Message-ID-Hash: Q5HTS4YK5MWALXIXHO5HTIUOATWRIYQ2
X-MailFrom: vesely@tana.it
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dmarc.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dmarc-ietf] Re: Evaluating consensus on the idea of making ARC "Historic"
List-Id: "Domain-based Message Authentication, Reporting, and Compliance (DMARC)" <dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gV-7-_QYkIb5UkxdZvsibQDIFuQ>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Owner: <mailto:dmarc-owner@ietf.org>
List-Post: <mailto:dmarc@ietf.org>
List-Subscribe: <mailto:dmarc-join@ietf.org>
List-Unsubscribe: <mailto:dmarc-leave@ietf.org>

Hi,

it is not easy to understand what happened at Yahoo.  The statement relayed by 
Richard (and quoted below) may shred some further light after John's summary:

     Y tells us that they had to ignore G's ARC chains because they signed
     messages that took insecure routes and were silently modified.
     https://mailarchive.ietf.org/arch/msg/dmarc/ZTIYuQG9oCOP7bmc7WoYAWIgicM

and Richard's quote of draft-adams-arc-experiment-conclusion-01:

    *  Abuse of trusted chains: Attackers have been leveraging situations
       where recipients trusted ARC chains by modifying email after an
       initial attestation and then passing it to another entity which
       trusted that attestation.  Assessing whether the email came
       directly from the entity at the head of the ARC chain is complex
       and assessing whether or not any changes to the email were made by
       a trusted signer or a malicious third party has proved to be
       impossible.
     https://mailarchive.ietf.org/arch/msg/dmarc/pfleAeQo_bacxA9a4yhs7gEuDWI

Messages apparently followed a path like:

     Originator -> G (adding an ARC set) -> bad guy (modifying the message) -> Y

However, it is not explained whether the bad guy added a second ARC set or how 
the message could have been modified without invalidating G's signature.


Best
Ale


On Thu 30/Jul/2026 20:07:34 +0200 Richard Clayton wrote:
> In message <CALaySJK-X0XtA8ODbA-9KbzTxDth_pKc5fqWU6tbq3h+tizJ=g@mail.gma
> il.com>, Barry Leiba <barryleiba@gmail.com> writes
> 
>>The next step is for those who still want to proceed with making ARC
>>Historic *now*... to respond to these objections and either accept the
>>suggestion to wait, or to address reasons we should not.
> 
> I would like to relay a statement (sorry for the delay, but these things
> need some approvals):
> 
> ----
> 
> At Yahoo we have read with interest the recent discussions about
> documenting the end of the ARC experiment.
> 
> We have not been applying ARC headers to any email and we will not be
> doing so in the future.
> 
> We have experimented with accepting ARC information from other senders.
> Our experience has been that this has DECREASED our ability to identify
> email that our users do not wish to receive. It has not improved our
> ability to identify valid email that has been forwarded by others,
> instead our trust in senders to report useful and valid information to
> us has been misplaced on several occasions. We have taken several large
> senders off our "trusted list" as a result, and we will not be spending
> any effort in adding any new senders to our (now extremely short) list.
> 
> Counting by domain we currently see about 12,000 users of ARC -- which
> may sound a lot but it is rather less than half of one percent of the
> domains sending us email each day. That is we conclude that, even after
> about 10 years, adoption has been very low indeed.
> 
> We would not encourage any other senders to bother with ARC, instead
> they should engage with the DKIM2 initiative which we believe will be of
> significant use in improving our ability to identify mail which our
> users want.
> 
> 
> _______________________________________________
> dmarc mailing list -- dmarc@ietf.org
> To unsubscribe send an email to dmarc-leave@ietf.org