Hi,
On 08.05.2025 20:03, John Levine wrote:
Except that DKIM2 will let recipients reliably look back through the changes
that forwarders make.
Which was exactly the point I was trying to make.
a) If the changes are reversible (they're not "arbitrary
modifications"), validity is easy to verify, it doesn't require some
tacked-on trust process.
b) If they are not reversible, it likely requires a trust process like
ARC does. In that case ARC already exists and works, if that's a problem
that someone needs solved.
Burdening DKIMv2 with it might be an "easy way out" for some
implementers, I suspect many of us are familiar with vendors' tendency
to say "just allowlist us". Which will then result in "just allowlist
our arbitrary irreversible modifications", I fear.
On 08.05.2025 20:03, John Levine wrote:
If it were practical to set up shared lists of trusted forwarders. it would
have happened in the 10 years since the ARC draftwas published.
But it has happened, but only in the sense that everyone has their own
list for the forwarders they trust. From our experience it works really
well to solve certain problems.
Best,
Taavi
_______________________________________________
Ietf-dkim mailing list -- [email protected]
To unsubscribe send an email to [email protected]
