Murray S. Kucherawy writes: > On Thu, Apr 23, 2026 at 8:04 AM Alessandro Vesely <[email protected]> wrote: > > Section 3.1 states that "ARC required evaluators to run a reputation > system for ARC signers." This is not accurate. The only occurrence of > the term "reputation" in the ARC specification is in Section 7.1.2, where > it notes that a site /may/ apply reputation-based filtering. There is no > requirement for evaluators to operate such a system. > > I would assume what's meant here is that ARC is only truly valuable if you > develop some kind of reputation for "good" or "bad" actors in the ARC chain. > Without that, ARC's value is arguably limited. (The same argument applies to > DKIM.)
Which wrong. Forwarding does not happen without the recipient knowing it, thus recipient will KNOW which email serverices are forwarding emails to him (he has set those forwarding himself). If he has set up the forwardings himself, he clearly already trustes the service as he trusts that service to process his emails, thus he can trust the ARC headers generated by that service. There is no need for any kind of global trust, only per recipient trust and that is easy for him to configure to his recipient system. > More generally, the use of signatures should be considered within a > broader authentication and authorization framework. Internet email has > historically operated without mandatory authentication, and with an > implicit authorization model in which any sender can attempt delivery to > any recipient without prior arrangement. This openness is a core property > of the system. Forwarding, by contrast, introduces third-party assertions > of identity, where this implicit authorization model no longer applies > cleanly. > > If I configure this email address to forward elsewhere, does Gmail make any > assertions about any identity in the message (apart from, say, its own DKIM > signature)? I don't think that's ever true, much less generally true. But when you set up the forwarding that means you do trust google. So your final destination can be configure it to trust ARC headers generated by the google, as you know that you are going to be receiving forwarded emails from google, and as you clearly trust it, you can trust its ARC headers, and if they say that SPF/DKIM/DMARC passed when it came in, you know that was true at that point. -- [email protected] _______________________________________________ dmarc mailing list -- [email protected] To unsubscribe send an email to [email protected]
