A person referring to $DAYJOB$ (a larger MBP) has said on this list they find 
no value with ARC, and even harmful, a few months ago.  Google removed it from 
their documentation for “sender requirements”.  I have said we stopped 
evaluating its usefulness for a number of reasons.

I’ve said before that there may be some use for ARC (internal routing, etc), 
but as the document describes the goals/usages of ARC, I don’t believe it is 
the solution we are looking for.

--
Alex Brotman
Sr. Engineer, Anti-Abuse & Messaging Policy
Comcast

From: Murray S. Kucherawy <[email protected]>
Sent: Tuesday, July 7, 2026 1:47 PM
To: Taavi Eomäe <[email protected]>
Cc: [email protected]; Tero Kivinen <[email protected]>
Subject: [dmarc-ietf] Re: Review of draft-ietf-dmarc-arc-to-historic

On Tue, Jul 7, 2026 at 12:03 AM Taavi Eomäe 
<[email protected]<mailto:[email protected]>> wrote:
On 06.07.2026 22:07, Murray S. Kucherawy wrote:
> [...] to have the momentum needed to overcome that complexity, and
> deliver signal that operators find useful.  ARC doesn't appear to have
> developed that momentum.

This is a bold statement that ARC doesn't deliver an useful signal for
operators. Except for some unspecified "big players", for which it
hasn't, that have not been named.

Earlier in that same message, I did use the word "some" multiple times.  I'm 
not making a categorical claim here.  Maybe the issue is that the larger 
operators that find no value in it have simply been the most vocal, and (until 
now) nobody has really come to its defense.

And at least two of the "big players" are here and participating.  It's up to 
them if they want to re-state their affiliations.

-MSK
_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to