On 27/04/2026 23:20, John Levine wrote:
It appears that Tero Kivinen  <[email protected]> said:
Which wrong. Forwarding does not happen without the recipient knowing
it, thus recipient will KNOW which email services are forwarding
emails to him ....

Sometimes. My wife and I have forwarding addresses at our universities, and I
have one at the IEEE ([email protected].) They all used to handle the forwarding
themselves, but over the years they outsourced it. Yale outsourced to Google,
Cornell to Microsoft. The IEEE has a strange system where the mail goes to
Google, is relayed to an IEEE server at AWS, and is then reinjected into Google
to send back out.

When a forwarder moves, frequently without telling the forward recipients, whose
job is it to update your users' configuration?


If the user’s configuration is tied to a stable identifier such as a List-ID, and the list signs its mail with a DKIM signing key for that identifier, then changes in the underlying forwarding path don’t require user updates. Any notion of authorization is necessarily local to the receiver and follows the list identity, not the infrastructure.


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.

Sure, and you don't need ARC for that, just whitelist the forwarding system.


Right, or have the forwarder sign with DKIM. But this brings out another point of the draft:

    Because the forwarding party is typically not in the author’s domain
    control and cannot easily be enumerated in the author’s SPF record,
    it becomes operationally infeasible for senders to cover every
    possible forwarder. As such, broken authentication at forwarders
    represents a structural gap in DMARC deployment.

Why should senders cover every possible forwarder? That seems more naturally a receiver-side concern.


Best
Ale
--




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

Reply via email to