I believe I asked a straightforward question, which I have asked previously in other ways in other contexts. The silence confirms that, unfortunately, there is no good answer.
We have had much discussion which assumes that ARC will reduce From rewrite, because ARC will allow an evaluator to identify trustworthy changes made by mailing lists. When the mailing list operator is unaware that the recipient is using ARC to trust his messages, he must continue to rewrite From. This means that ARC must be combined with the reverse-encoding techniques described by Ale, so that the diminishing of >From rewrite is accomplished entirely by the evaluator before presenting the message to the user. List operators could diminish From rewrite by collecting data about which evaluators require it. There are two obvious ways to collect this data: asking subscribers and sending test messages. Yet I have been repeatedly told, most recently by Ale, that list operators are unwilling to collect evaluator-specific data. Perhaps this resistance exists because the supporting software does not exist, and that could be fixed if the concept was formalized by IETF. Without reverse-encoding or evaluator-specific rewrite decisions, ARC has failed at its original purpose. Doug Foster On Fri, Oct 8, 2021 at 1:02 AM Benny Pedersen <m...@junc.eu> wrote: > On 2021-10-08 02:47, Douglas Foster wrote: > > Assume the following: > > > > List "L" has implemented ARC and has subscribers from 10 domains, > > Domain through DomainJ. > > > > A user from DomainA, which publishes p=reject, submits a post to the > > list. > > > > What information does List "L" use to decide whether to rewrite > > "From", for each of the 10 domains? > > How is that information obtained? > > what info ? > > are you asking how to break dkim ? > > dkim have still adsp, and atleast this still stands in spamassassin, > since it uses metacpan Mail::DKIM perl module > > simple do not break dkim > > i think its endless debate on we want to fix it, but no one can see the > light in the jungle of solutions on problems never existed on servial > maillists that does not break dkim > > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc >
_______________________________________________ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
